From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Ladislav Michl <oss-lists@triops.cz>
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH] MIPS: OCTEON: octeon-usb: Consolidate error messages
Date: Fri, 27 Jan 2023 17:27:13 +0100 [thread overview]
Message-ID: <20230127162713.GA6090@alpha.franken.de> (raw)
In-Reply-To: <Y6MW9Z4uhrqO4ocn@lenoch>
On Wed, Dec 21, 2022 at 03:23:49PM +0100, Ladislav Michl wrote:
> From: Ladislav Michl <ladis@linux-mips.org>
>
> Console output currently looks like USB clocks initialized succesfully
> even in case of error. Fix that and use consistently dev_err for fatal
> errors otherwise dev_warn.
>
> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> ---
> Hi there,
>
> this is just cleanup before real work. Just note that even
> warning says "Invalid UCTL clock rate ..., using 100000000 instead"
> clock_rate is not set to 100000000. There's also some indentation
> fixes to be done.
>
> However my main concern is unimplemented errata 29206 as noted in
> OCTEON III CN70XX/CN71XX Known Issues Revision 1.9, released under
> NDA. You can see its implementation in coreboot here (line 196):
> https://fossies.org/linux/coreboot/src/vendorcode/cavium/bdk/libbdk-hal/bdk-usb.c
>
> Above looks like BSD license. I'll reimplement said errata
> from scratch, unless someone sees as a problem "Marvell Proprietary
> and Confidential" documentation is used as source.
>
> arch/mips/cavium-octeon/octeon-usb.c | 42 +++++++++++++---------------
> 1 file changed, 20 insertions(+), 22 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-01-27 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 14:23 [PATCH] MIPS: OCTEON: octeon-usb: Consolidate error messages Ladislav Michl
2023-01-27 16:27 ` Thomas Bogendoerfer [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=20230127162713.GA6090@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@vger.kernel.org \
--cc=oss-lists@triops.cz \
/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).