[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJM55Z_o7Z8HhaUjrSqjxy1cPjud9Q3GrdqjgFThToxxOCrkgw@mail.gmail.com>
Date: Fri, 22 Sep 2023 03:40:49 -0700
From: Emil Renner Berthing <emil.renner.berthing@...onical.com>
To: Ben Dooks <ben.dooks@...ethink.co.uk>,
Chen Wang <unicornxw@...il.com>, aou@...s.berkeley.edu,
chao.wei@...hgo.com, conor@...nel.org, devicetree@...r.kernel.org,
emil.renner.berthing@...onical.com, guoren@...nel.org,
jszhang@...nel.org, krzysztof.kozlowski+dt@...aro.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
palmer@...belt.com, paul.walmsley@...ive.com, robh+dt@...nel.org,
xiaoguang.xing@...hgo.com
Cc: Chen Wang <wangchen20@...as.ac.cn>
Subject: Re: [PATCH v2 08/11] serial: 8250_dw: Add Sophgo SG2042 support
Ben Dooks wrote:
> On 20/09/2023 07:40, Chen Wang wrote:
> > From: Emil Renner Berthing <emil.renner.berthing@...onical.com>
> >
> > Add quirk to skip setting the input clock rate for the uarts on the
> > Sophgo SG2042 SoC similar to the StarFive JH7100.
>
> I'd love an actual explanation of why this is necessary here.
Makes sense. For the JH7100 the commit message is:
On the StarFive JH7100 RISC-V SoC the UART core clocks can't be set to
exactly 16 * 115200Hz and many other common bitrates. Trying this will
only result in a higher input clock, but low enough that the UART's
internal divisor can't come close enough to the baud rate target.
So rather than try to set the input clock it's better to skip the
clk_set_rate call and rely solely on the UART's internal divisor.
@Chen Wang is this also true for the SG2042?
/Emil
Powered by blists - more mailing lists