> This patch should be backported to kernels as old as 3.2, that
> contain the commit 71c731a296f1b08a3724bd1b514b64f1bda87a23 "usb: host:
> xhci: Fix Compliance Mode on SN65LVPE502CP Hardware"
>
> Signed-off-by: Sarah Sharp
> Cc: Huang Ying
> Cc: sta...@vger.kernel.o
, is there a way to permanently disable D3cold, so that userspace
> can't re-enable it?
Yes. You can set
pci_dev->no_d3cold = true
in runtime_suspend callback of device driver. Then the device will
never be put into D3COLD state.
Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Dec 12, 2012 at 10:34 AM, Andrew Lutomirski wrote:
> On Tue, Dec 11, 2012 at 6:32 PM, Huang Ying wrote:
>> On Fri, 2012-12-07 at 22:00 +0100, Rafael J. Wysocki wrote:
>>> On Thursday, December 06, 2012 04:28:08 PM Sarah Sharp wrote:
>>> > On Thu, Dec 06, 20
hat patch after the bisect finished didn't seem to help.
> > However, it does make sense that this would be the culprit patch, if
> > Huang Ying's theory about the PME polling is correct.
>
> Well, we surely don't handle this particular case correctly, and it shouldn
se D3hot instead?
> > >
> > > Yes, you have /sys/bus/pci/devices/.../d3cold_allowed
> > > See Documentation/ABI/testing/sysfs-bus-pci
> > >
> > > If this really is a problem with the D3cold support that went into 3.6
> > > then I guess you shoul
On Mon, 2012-07-30 at 10:19 -0400, Alan Stern wrote:
> On Mon, 30 Jul 2012, Huang Ying wrote:
>
> > > Yup, that worked in the quick test I just did.
> > >
> > > lspci reading the device config will still not wake the bridge, but I
> > > assume that is i
On Mon, 2012-07-30 at 10:19 -0400, Alan Stern wrote:
> On Mon, 30 Jul 2012, Huang Ying wrote:
>
> > > Yup, that worked in the quick test I just did.
> > >
> > > lspci reading the device config will still not wake the bridge, but I
> > > assume that is i
On Mon, 2012-07-30 at 18:57 +0200, Bjørn Mork wrote:
> huang ying writes:
>
> > On Mon, Jul 30, 2012 at 4:08 PM, Bjørn Mork wrote:
> >> Huang Ying writes:
> >>
> >>> Do you have time to test the following patch to fix the lspci issue?
> >>&
On Mon, Jul 30, 2012 at 4:08 PM, Bjørn Mork wrote:
> Huang Ying writes:
>
>> Do you have time to test the following patch to fix the lspci issue?
>>
>> Subject: [BUGFIX] PCI/PM: Keep parent bridge active when read/write config
>> reg
>
>
> Sure. But ke
On Fri, 2012-07-27 at 11:11 +0200, Bjørn Mork wrote:
> Huang Ying writes:
>
> > Do you have time to try the following patch?
> >
> > Best Regards,
> > Huang Ying
> >
> > ---
> > drivers/pci/pci-driver.c |6 ++
> > 1 file changed,
On Thu, 2012-07-26 at 12:35 +0200, Bjørn Mork wrote:
> Huang Ying writes:
>
> > Do you have time to try the below patch?
>
> Sure. Looks OK wrt the USB problems, but may cause problems with the
> PCIe WiFi card. Unless those are related to other changes in -next.
>
On Wed, 2012-07-25 at 15:58 +0200, Bjørn Mork wrote:
> huang ying writes:
>
> > Hi, Bjorn,
> >
> > Thank you very much for your detailed information.
> >
> > On Wed, Jul 25, 2012 at 5:58 PM, Bjørn Mork wrote:
> >> Huang Ying writes:
> >>
If not, then
> why add it in the first place?
Yes. I should have added the ABI document. Will write a patch for
that.
Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi, Rafael,
On Wed, 2012-07-25 at 22:02 +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 25, 2012, Bjørn Mork wrote:
> > huang ying writes:
> >
> > > Hi, Bjorn,
> > >
> > > Thank you very much for your detailed information.
> > >
>
Hi, Bjorn,
Thank you very much for your detailed information.
On Wed, Jul 25, 2012 at 5:58 PM, Bjørn Mork wrote:
> Huang Ying writes:
>> On Wed, 2012-07-25 at 06:08 +0200, Bjørn Mork wrote:
>>> Enabling autosuspend for USB causes hotplug failure in the current
>>>
ollers to suspend
> 3) plugin a new USB device
After plugin the new USB device, is there anything in dmesg?
>
> I've bisected the regression down to this commit:
>
>
> commit 448bd857d48e69b33ef323739dc6d8ca20d4cda7
> Author: Huang Ying
> Date: Sat Jun 23 10
16 matches
Mail list logo