Hi,
On 09/20/2016 09:54 PM, Mathias Nyman wrote:
> On 29.08.2016 08:26, Lu Baolu wrote:
>> xHCI debug capability (DbC) is an optional but standalone
>> functionality provided by an xHCI host controller. Software
>> learns this capability by walking through the extended
>> capability list of the
On 29.08.2016 08:26, Lu Baolu wrote:
xHCI debug capability (DbC) is an optional but standalone
functionality provided by an xHCI host controller. Software
learns this capability by walking through the extended
capability list of the host. xHCI specification describes
DbC in section 7.6.
This
On Thu, 2016-09-01 at 10:21 +0800, Lu Baolu wrote:
> Hi Oliver,
>
> Thanks for review.
>
> On 08/31/2016 05:53 PM, Oliver Neukum wrote:
> > On Mon, 2016-08-29 at 13:26 +0800, Lu Baolu wrote:
> >> + /*
> >> +* Memory barrier to ensure hardware sees the trbs
> >> +* enqueued
Hi Oliver,
Thanks for review.
On 08/31/2016 05:53 PM, Oliver Neukum wrote:
> On Mon, 2016-08-29 at 13:26 +0800, Lu Baolu wrote:
>> + /*
>> +* Memory barrier to ensure hardware sees the trbs
>> +* enqueued above.
>> +*/
>> + wmb();
>> + if (cycle)
>> +
On Mon, 2016-08-29 at 13:26 +0800, Lu Baolu wrote:
> + /*
> +* Memory barrier to ensure hardware sees the trbs
> +* enqueued above.
> +*/
> + wmb();
> + if (cycle)
> + trb->field[3] |= cpu_to_le32(cycle);
> + else
> +
xHCI debug capability (DbC) is an optional but standalone
functionality provided by an xHCI host controller. Software
learns this capability by walking through the extended
capability list of the host. xHCI specification describes
DbC in section 7.6.
This patch introduces the code to probe and
