All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anurag Kumar Vulisha <anuragku@xilinx.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] usb: host: xhci-plat: Iterate over parent nodes for finding quirks
Date: Tue, 12 Jun 2018 07:03:39 +0000	[thread overview]
Message-ID: <MWHPR02MB2816ACB30A1142BD1B83F25CA77F0@MWHPR02MB2816.namprd02.prod.outlook.com> (raw)
In-Reply-To: <MWHPR02MB2816106466BD2AF8F7FB7BF8A7660@MWHPR02MB2816.namprd02.prod.outlook.com>

Hi Greg,

Please let me know if you have any comments on this patch. 

Thanks,
Anurag Kumar Vulisha

>-----Original Message-----
>From: Anurag Kumar Vulisha
>Sent: Wednesday, June 06, 2018 12:11 AM
>To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>Cc: Mathias Nyman <mathias.nyman@intel.com>; linux-usb@vger.kernel.org; linux-
>kernel@vger.kernel.org
>Subject: RE: [PATCH] usb: host: xhci-plat: Iterate over parent nodes for finding quirks
>
>Hi Greg,
>
>>-----Original Message-----
>>From: Greg Kroah-Hartman [mailto:gregkh@linuxfoundation.org]
>>Sent: Tuesday, June 05, 2018 8:55 PM
>>To: Anurag Kumar Vulisha <anuragku@xilinx.com>
>>Cc: Mathias Nyman <mathias.nyman@intel.com>; linux-usb@vger.kernel.org;
>>linux- kernel@vger.kernel.org
>>Subject: Re: [PATCH] usb: host: xhci-plat: Iterate over parent nodes
>>for finding quirks
>>
>>On Tue, Jun 05, 2018 at 08:50:56PM +0530, Anurag Kumar Vulisha wrote:
>>> In xhci_plat_probe() both sysdev and pdev->dev are being used for
>>> finding quirks. There are some drivers(like dwc3 host.c) which adds
>>> quirks(like usb3-lpm-capable) into pdev and the logic present in
>>> xhci_plat_probe() checks for quirks in either sysdev or pdev for
>>> finding the quirks. Because of this logic, some of the quirks are
>>> getting missed(usb3-lpm-capable quirk added by dwc3 host.c driver is
>>> getting missed).This patch fixes this by iterating over all the
>>> available parents for finding the quirks. In this way all the quirks
>>> which are present in child or parent are correctly updated.
>>>
>>> Signed-off-by: Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>
>>
>>So this is a bugfix?  If so, how far back in the kernel releases should it go to?
>>
>I feel this is as a bugfix. This problem started with this patch
>"usb: xhci: use bus->sysdev for DMA configuration (4c39d4b949d36faf)"
>where pdev->dev is replaced with sysdev. If I am not wrong this bug is present since
>4.12 kernel release.
>
>Thanks,
>Anurag kumar Vulisha
>
>>thanks,
>>
>>greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Anurag Kumar Vulisha <anuragku@xilinx.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: usb: host: xhci-plat: Iterate over parent nodes for finding quirks
Date: Tue, 12 Jun 2018 07:03:39 +0000	[thread overview]
Message-ID: <MWHPR02MB2816ACB30A1142BD1B83F25CA77F0@MWHPR02MB2816.namprd02.prod.outlook.com> (raw)

Hi Greg,

Please let me know if you have any comments on this patch. 

Thanks,
Anurag Kumar Vulisha

>-----Original Message-----
>From: Anurag Kumar Vulisha
>Sent: Wednesday, June 06, 2018 12:11 AM
>To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>Cc: Mathias Nyman <mathias.nyman@intel.com>; linux-usb@vger.kernel.org; linux-
>kernel@vger.kernel.org
>Subject: RE: [PATCH] usb: host: xhci-plat: Iterate over parent nodes for finding quirks
>
>Hi Greg,
>
>>-----Original Message-----
>>From: Greg Kroah-Hartman [mailto:gregkh@linuxfoundation.org]
>>Sent: Tuesday, June 05, 2018 8:55 PM
>>To: Anurag Kumar Vulisha <anuragku@xilinx.com>
>>Cc: Mathias Nyman <mathias.nyman@intel.com>; linux-usb@vger.kernel.org;
>>linux- kernel@vger.kernel.org
>>Subject: Re: [PATCH] usb: host: xhci-plat: Iterate over parent nodes
>>for finding quirks
>>
>>On Tue, Jun 05, 2018 at 08:50:56PM +0530, Anurag Kumar Vulisha wrote:
>>> In xhci_plat_probe() both sysdev and pdev->dev are being used for
>>> finding quirks. There are some drivers(like dwc3 host.c) which adds
>>> quirks(like usb3-lpm-capable) into pdev and the logic present in
>>> xhci_plat_probe() checks for quirks in either sysdev or pdev for
>>> finding the quirks. Because of this logic, some of the quirks are
>>> getting missed(usb3-lpm-capable quirk added by dwc3 host.c driver is
>>> getting missed).This patch fixes this by iterating over all the
>>> available parents for finding the quirks. In this way all the quirks
>>> which are present in child or parent are correctly updated.
>>>
>>> Signed-off-by: Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>
>>
>>So this is a bugfix?  If so, how far back in the kernel releases should it go to?
>>
>I feel this is as a bugfix. This problem started with this patch
>"usb: xhci: use bus->sysdev for DMA configuration (4c39d4b949d36faf)"
>where pdev->dev is replaced with sysdev. If I am not wrong this bug is present since
>4.12 kernel release.
>
>Thanks,
>Anurag kumar Vulisha
>
>>thanks,
>>
>>greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-06-12  7:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 15:20 [PATCH] usb: host: xhci-plat: Iterate over parent nodes for finding quirks Anurag Kumar Vulisha
2018-06-05 15:20 ` Anurag Kumar Vulisha
2018-06-05 15:25 ` [PATCH] " Greg Kroah-Hartman
2018-06-05 15:25   ` Greg Kroah-Hartman
2018-06-05 18:41   ` [PATCH] " Anurag Kumar Vulisha
2018-06-05 18:41     ` Anurag Kumar Vulisha
2018-06-12  7:03     ` Anurag Kumar Vulisha [this message]
2018-06-12  7:03       ` Anurag Kumar Vulisha
2018-06-12  8:02       ` [PATCH] " Greg Kroah-Hartman
2018-06-12  8:02         ` Greg Kroah-Hartman
2018-07-14 15:37         ` [PATCH] " Anurag Kumar Vulisha
2018-07-14 15:37           ` Anurag Kumar Vulisha
2018-07-15  8:02           ` [PATCH] " Greg Kroah-Hartman
2018-07-15  8:02             ` Greg Kroah-Hartman
2018-07-15  8:11             ` [PATCH] " Greg Kroah-Hartman
2018-07-15  8:11               ` Greg Kroah-Hartman
2018-07-20 14:53               ` [PATCH] " Mathias Nyman
2018-07-20 14:53                 ` Mathias Nyman
2018-08-06  7:58                 ` [PATCH] " Anurag Kumar Vulisha
2018-08-06  7:58                   ` Anurag Kumar Vulisha
2018-08-06 11:11                   ` [PATCH] " Mathias Nyman
2018-08-06 11:11                     ` Mathias Nyman
2018-08-06 11:41                     ` [PATCH] " Anurag Kumar Vulisha
2018-08-06 11:41                       ` Anurag Kumar Vulisha
2018-07-20 14:42 ` [PATCH] " Mathias Nyman
2018-07-20 14:42   ` Mathias Nyman
2018-07-20 15:39   ` [PATCH] " Anurag Kumar Vulisha
2018-07-20 15:39     ` Anurag Kumar Vulisha
2018-08-06 10:50     ` [PATCH] " Mathias Nyman
2018-08-06 10:50       ` Mathias Nyman
2018-08-06 11:14       ` [PATCH] " Anurag Kumar Vulisha
2018-08-06 11:14         ` Anurag Kumar Vulisha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MWHPR02MB2816ACB30A1142BD1B83F25CA77F0@MWHPR02MB2816.namprd02.prod.outlook.com \
    --to=anuragku@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.