From: Phil Elwell <phil@raspberrypi.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Minas Harutyunyan <hminas@synopsys.com>,
Sasha Levin <sashal@kernel.org>,
Artur Petrosyan <Arthur.Petrosyan@synopsys.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] usb: dwc2: Fix build in periphal-only mode
Date: Fri, 28 May 2021 11:04:08 +0100 [thread overview]
Message-ID: <d577970e-7b86-1b1b-b31a-e432f1dc1c64@raspberrypi.com> (raw)
In-Reply-To: <YLC9I6vKh9z7LTke@kroah.com>
On 28/05/2021 10:51, Greg Kroah-Hartman wrote:
> On Fri, May 28, 2021 at 10:37:48AM +0100, Phil Elwell wrote:
>> Hi Greg,
>>
>> On 28/05/2021 10:23, Greg Kroah-Hartman wrote:
>>> On Fri, May 28, 2021 at 10:13:50AM +0100, Phil Elwell wrote:
>>>> The bus_suspended member of struct dwc2_hsotg is only present in builds
>>>> that support host-mode.
>>>>
>>>> Fixes: 24d209dba5a3 ("usb: dwc2: Fix hibernation between host and device modes.")
>>>> Signed-off-by: Phil Elwell <phil@raspberrypi.com>
>>>> ---
>>>> drivers/usb/dwc2/core_intr.c | 4 ++++
>>>> 1 file changed, 4 insertions(+)
>>>>
>>>> v2: Correct commit hash used in the Fixes line.
>>>>
>>>> diff --git a/drivers/usb/dwc2/core_intr.c b/drivers/usb/dwc2/core_intr.c
>>>> index a5ab03808da6..03d0c034cf57 100644
>>>> --- a/drivers/usb/dwc2/core_intr.c
>>>> +++ b/drivers/usb/dwc2/core_intr.c
>>>> @@ -725,7 +725,11 @@ static inline void dwc_handle_gpwrdn_disc_det(struct dwc2_hsotg *hsotg,
>>>> dwc2_writel(hsotg, gpwrdn_tmp, GPWRDN);
>>>> hsotg->hibernated = 0;
>>>> +
>>>> +#if IS_ENABLED(CONFIG_USB_DWC2_HOST) || \
>>>> + IS_ENABLED(CONFIG_USB_DWC2_DUAL_ROLE)
>>>> hsotg->bus_suspended = 0;
>>>> +#endif
>>>> if (gpwrdn & GPWRDN_IDSTS) {
>>>> hsotg->op_state = OTG_STATE_B_PERIPHERAL;
>>>> --
>>>> 2.25.1
>>>>
>>> I do not understand, the field in the structure is present for all, why
>>> is this crazy #if needed here?
>>>
>>> I see that the commit you reference here did add the new line to set
>>> bus_suspended, which seemed to be the point here. Why will the #if
>>> values matter here?
>> Sorry to waste your brain cycles on this. There is a problem, but it only
>> exists in branches where the blamed commit (24d209dba5a3) has been
>> back-ported as a Fix, because it depends on commit 012466fc8ccc which isn't
>> a Fix and therefore
>> hasn't been back-ported. Sadly 012466fc8ccc doesn't back-port cleanly on its
>> own - either more cherry-picks or a temporary patch like mine will be
>> needed.
> So should we revert this commit from the stable releases where it showed
> up? Which ones specifically?
>
> If so, please let me and stable@vger.kernel.org know and we can take
> care of it there.
Reverting back-ports of 24d209dba5a3 would be sufficient, although you are then
left with the problem that 24d209dba5a3 was intended to address.
I'll email the stable list.
Phil
prev parent reply other threads:[~2021-05-28 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 9:13 [PATCH v2] usb: dwc2: Fix build in periphal-only mode Phil Elwell
2021-05-28 9:23 ` Greg Kroah-Hartman
2021-05-28 9:37 ` Phil Elwell
2021-05-28 9:51 ` Greg Kroah-Hartman
2021-05-28 10:04 ` Phil Elwell [this message]
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=d577970e-7b86-1b1b-b31a-e432f1dc1c64@raspberrypi.com \
--to=phil@raspberrypi.com \
--cc=Arthur.Petrosyan@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sashal@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox