From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Pawel Laszczak <pawell@cadence.com>
Cc: "peter.chen@kernel.org" <peter.chen@kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] usb: cdnsp: Fix issue with resuming from L1
Date: Thu, 10 Apr 2025 11:26:38 +0200 [thread overview]
Message-ID: <2025041050-condition-stout-8168@gregkh> (raw)
In-Reply-To: <PH7PR07MB9538959C61B32EBCA33D1909DDB72@PH7PR07MB9538.namprd07.prod.outlook.com>
On Thu, Apr 10, 2025 at 07:34:16AM +0000, Pawel Laszczak wrote:
> Subject: [PATCH] usb: cdnsp: Fix issue with resuming from L1
Why is the subject line duplicated here? Can you fix up your git
send-email process to not do that?
> In very rare cases after resuming controller from L1 to L0 it reads
> registers before the clock has been enabled and as the result driver
> reads incorrect value.
> To fix this issue driver increases APB timeout value.
>
> Probably this issue occurs only on Cadence platform but fix
> should have no impact for other existing platforms.
If this is the case, shouldn't you just handle this for Cadence-specific
hardware and add the check for that to this change?
>
> Fixes: 3d82904559f4 ("usb: cdnsp: cdns3 Add main part of Cadence USBSSP DRD Driver")
> cc: stable@vger.kernel.org
> Signed-off-by: Pawel Laszczak <pawell@cadence.com>
> ---
> drivers/usb/cdns3/cdnsp-gadget.c | 22 ++++++++++++++++++++++
> drivers/usb/cdns3/cdnsp-gadget.h | 4 ++++
> 2 files changed, 26 insertions(+)
>
> diff --git a/drivers/usb/cdns3/cdnsp-gadget.c b/drivers/usb/cdns3/cdnsp-gadget.c
> index 87f310841735..b12581b94567 100644
> --- a/drivers/usb/cdns3/cdnsp-gadget.c
> +++ b/drivers/usb/cdns3/cdnsp-gadget.c
> @@ -139,6 +139,21 @@ static void cdnsp_clear_port_change_bit(struct cdnsp_device *pdev,
> (portsc & PORT_CHANGE_BITS), port_regs);
> }
>
> +static void cdnsp_set_apb_timeout_value(struct cdnsp_device *pdev)
> +{
> + __le32 __iomem *reg;
> + void __iomem *base;
> + u32 offset = 0;
> + u32 val;
> +
> + base = &pdev->cap_regs->hc_capbase;
> + offset = cdnsp_find_next_ext_cap(base, offset, D_XEC_PRE_REGS_CAP);
> + reg = base + offset + REG_CHICKEN_BITS_3_OFFSET;
> +
> + val = le32_to_cpu(readl(reg));
> + writel(cpu_to_le32(CHICKEN_APB_TIMEOUT_SET(val)), reg);
Do you need to do a read to ensure that the write is flushed to the
device before continuing?
> +}
> +
> static void cdnsp_set_chicken_bits_2(struct cdnsp_device *pdev, u32 bit)
> {
> __le32 __iomem *reg;
> @@ -1798,6 +1813,13 @@ static int cdnsp_gen_setup(struct cdnsp_device *pdev)
> pdev->hci_version = HC_VERSION(pdev->hcc_params);
> pdev->hcc_params = readl(&pdev->cap_regs->hcc_params);
>
> + /* In very rare cases after resuming controller from L1 to L0 it reads
> + * registers before the clock has been enabled and as the result driver
> + * reads incorrect value.
> + * To fix this issue driver increases APB timeout value.
> + */
Nit, please use the "normal" kernel comment style.
thanks,
greg k-h
next prev parent reply other threads:[~2025-04-10 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250410072333.2100511-1-pawell@cadence.com>
2025-04-10 7:34 ` [PATCH] usb: cdnsp: Fix issue with resuming from L1 Pawel Laszczak
2025-04-10 9:26 ` gregkh [this message]
2025-04-11 9:39 ` Pawel Laszczak
2025-04-11 9:48 ` Pawel Laszczak
2025-04-11 1:41 ` Peter Chen (CIX)
2025-04-11 10:00 ` Pawel Laszczak
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=2025041050-condition-stout-8168@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pawell@cadence.com \
--cc=peter.chen@kernel.org \
--cc=stable@vger.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