From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jia Wang <wangjia@ultrarisc.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/4] serial: 8250_dw: build Renesas RZN1 CPR value from DW_UART_CPR_* definitions
Date: Fri, 24 Apr 2026 17:09:46 +0300 (EEST) [thread overview]
Message-ID: <363a636d-f014-cc29-6be4-ec3041f43855@linux.intel.com> (raw)
In-Reply-To: <aetv2ljDOpH_Hs4s@ashevche-desk.local>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
On Fri, 24 Apr 2026, Andy Shevchenko wrote:
> On Fri, Apr 24, 2026 at 02:38:56PM +0300, Ilpo Järvinen wrote:
> > On Fri, 24 Apr 2026, Jia Wang wrote:
>
> ...
>
> > Hmm, maybe there should also be macro also for this one which takes the
> > fifosize as input and converts it to CPR field vlaue (effectively, the
> > macro is an inverse of DW_UART_CPR_FIFO_SIZE()). It would be more readable
> > than the literal.
>
> But this can be done separately, right?
It's logically part of the cpr_value literal to defines conversion (of
course one could introduce it in own patch without users but I don't see
much benefit from that).
> > Also include BUILD_BUG_ON(!IS_ALIGNED(fifosize, 16) + bounds checks)
> > inside that macro to catch invalid fifo sizes (+ don't forget the
> > necessary headers for those two new things).
>
> Hmm... Some devices may have FIFO = 8 or 4 bytes (Intel Quark IIRC has less
> than 16 and it's DW IP).
Perhaps but according the DW databook I've at hand, there are no values in
FIFO_MODE field for such FIFO sizes. So what would CPR contain in those
cases for FIFO_MODE field?
--
i.
next prev parent reply other threads:[~2026-04-24 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 5:39 [PATCH v4 0/4] serial: 8250_dw: Add support for UltraRISC DP1000 UART Jia Wang
2026-04-24 5:39 ` [PATCH v4 1/4] serial: 8250_dwlib: move DesignWare register definitions to header Jia Wang
2026-04-24 10:02 ` Andy Shevchenko
2026-04-27 2:31 ` Jia Wang
2026-04-24 5:39 ` [PATCH v4 2/4] serial: 8250_dw: build Renesas RZN1 CPR value from DW_UART_CPR_* definitions Jia Wang
2026-04-24 11:38 ` Ilpo Järvinen
2026-04-24 13:27 ` Andy Shevchenko
2026-04-24 14:09 ` Ilpo Järvinen [this message]
2026-04-24 15:16 ` Andy Shevchenko
2026-04-27 7:32 ` Jia Wang
2026-04-24 5:39 ` [PATCH v4 3/4] dt-bindings: serial: snps-dw-apb-uart: Add UltraRISC DP1000 UART Jia Wang
2026-04-24 5:39 ` [PATCH v4 4/4] serial: 8250_dw: Use a fixed CPR value for " Jia Wang
2026-04-24 9:58 ` [PATCH v4 0/4] serial: 8250_dw: Add support " Andy Shevchenko
2026-04-27 7:34 ` Jia Wang
2026-04-27 7:39 ` Andy Shevchenko
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=363a636d-f014-cc29-6be4-ec3041f43855@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=alex@ghiti.fr \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=wangjia@ultrarisc.com \
/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