From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: linux-sunxi@lists.linux.dev, Roman Stratiienko <r.stratiienko@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
wens@csie.org, mripard@kernel.org, b-liu@ti.com,
megous@megous.com, Roman Stratiienko <r.stratiienko@gmail.com>
Subject: Re: [PATCH] usb: musb: sunxi: Don't print error on MUSB_ULPI_BUSCONTROL access
Date: Wed, 10 Nov 2021 21:27:23 +0100 [thread overview]
Message-ID: <7984413.T7Z3S40VBb@kista> (raw)
In-Reply-To: <20211019131244.1568560-1-r.stratiienko@gmail.com>
Hi Roman,
sorry for late reply.
Dne torek, 19. oktober 2021 ob 15:12:44 CET je Roman Stratiienko napisal(a):
> Error message appears during suspend, where musb driver is storing
> the register state in musb_save_context():
> ```
> musb-sunxi 1c19000.usb: Error unknown readb offset 112
> ```
>
> Print warning instead to avoid confusion.
>
> Signed-off-by: Roman Stratiienko <r.stratiienko@gmail.com>
> ---
> drivers/usb/musb/sunxi.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/usb/musb/sunxi.c b/drivers/usb/musb/sunxi.c
> index f3f76f2ac63f9b..961c858fb349e1 100644
> --- a/drivers/usb/musb/sunxi.c
> +++ b/drivers/usb/musb/sunxi.c
> @@ -440,6 +440,10 @@ static u8 sunxi_musb_readb(void __iomem *addr, u32
offset)
> return 0xde;
>
> return readb(addr + SUNXI_MUSB_CONFIGDATA);
> + case MUSB_ULPI_BUSCONTROL:
> + dev_warn(sunxi_musb->controller->parent,
> + "sunxi-musb does not have ULPI bus
control register\n");
Since this register doesn't exist, wouldn't be better to print only debug
message? Warning would imply something that's out of the ordinary, but in this
case it's benign.
> + return 0;
> /* Offset for these is fixed by sunxi_musb_busctl_offset()
*/
> case SUNXI_MUSB_TXFUNCADDR:
> case SUNXI_MUSB_TXHUBADDR:
> @@ -494,6 +498,10 @@ static void sunxi_musb_writeb(void __iomem *addr,
unsigned offset, u8 data)
> return writeb(data, addr +
SUNXI_MUSB_TXFIFOSZ);
> case MUSB_RXFIFOSZ:
> return writeb(data, addr +
SUNXI_MUSB_RXFIFOSZ);
> + case MUSB_ULPI_BUSCONTROL:
> + dev_warn(sunxi_musb->controller->parent,
> + "sunxi-musb does not have ULPI bus
control register\n");
> + return;
> /* Offset for these is fixed by sunxi_musb_busctl_offset()
*/
Same here.
Best regards,
Jernej
> case SUNXI_MUSB_TXFUNCADDR:
> case SUNXI_MUSB_TXHUBADDR:
> --
> 2.30.2
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-11-10 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 13:12 [PATCH] usb: musb: sunxi: Don't print error on MUSB_ULPI_BUSCONTROL access Roman Stratiienko
2021-11-10 20:27 ` Jernej Škrabec [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=7984413.T7Z3S40VBb@kista \
--to=jernej.skrabec@gmail.com \
--cc=b-liu@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-usb@vger.kernel.org \
--cc=megous@megous.com \
--cc=mripard@kernel.org \
--cc=r.stratiienko@gmail.com \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).