From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jia Wang <wangjia@ultrarisc.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.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 v3 2/2] serial: 8250_dw: Use a fixed CPR value for UltraRISC DP1000 UART
Date: Wed, 22 Apr 2026 11:45:38 +0300 [thread overview]
Message-ID: <aeiKsv3bFPJ94InI@ashevche-desk.local> (raw)
In-Reply-To: <177681947637.2697678.10937675549830278979.b4-reply@b4>
On Wed, Apr 22, 2026 at 08:57:56AM +0800, Jia Wang wrote:
> On 2026-04-21 15:18 +0300, Ilpo Järvinen wrote:
> > On Tue, 21 Apr 2026, Jia Wang wrote:
...
> > > +static const struct dw8250_platform_data dw8250_ultrarisc_dp1000_data = {
> > > + .usr_reg = DW_UART_USR,
> > > + .cpr_value = 0x00022022,
> >
> > Please construct the cpr_value by ORing DW_UART_CPR_* defines together.
> > For fields, FIELD_PREP_CONST() may be useful.
> >
> > In order to be able to use the DW_UART_CPR_* defines, they need to be
> > moved into 8250_dwlib.h (I'd move all DW_UART register defines in a
> > preparatory patch).
> >
> > I know the existing Renesas' .cpr_value doesn't follow this convention but
> > that could be converted as well (in another patch, or leave the Renesas
> > entry conversion to me if you don't want to do that).
>
> Thanks for the review.
>
> Just to confirm: since you mentioned that the preparatory patch moving
> the DW_UART register defines is already in place, I don't need to move
> them again, correct?
>
> I will update my patch to use the DW_UART_CPR_* macros and
> FIELD_PREP_CONST() accordingly, and I’m happy to add a separate patch in
> the next revision to convert the Renesas .cpr_value as well.
My understanding that you want to send a patch series of 3 patches:
- moving DW_UART_CPR_* values from C-file to h-file
- modify existing Renesas case
- add support for your HW (this patch in updated form)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-04-22 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 5:58 [PATCH v3 0/2] serial: 8250_dw: Add support for UltraRISC DP1000 uart Jia Wang
2026-04-21 5:58 ` [PATCH v3 1/2] dt-bindings: serial: snps-dw-apb-uart: Add UltraRISC DP1000 UART Jia Wang
2026-04-21 17:06 ` Conor Dooley
2026-04-21 5:58 ` [PATCH v3 2/2] serial: 8250_dw: Use a fixed CPR value for " Jia Wang
2026-04-21 12:18 ` Ilpo Järvinen
2026-04-22 0:57 ` Jia Wang
2026-04-22 8:45 ` Andy Shevchenko [this message]
2026-04-22 8:46 ` Andy Shevchenko
2026-04-22 9:39 ` Jia Wang
2026-04-22 9:43 ` Andy Shevchenko
2026-04-22 9:51 ` Jia Wang
2026-04-22 9:01 ` Ilpo Järvinen
2026-04-22 9:45 ` Jia Wang
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=aeiKsv3bFPJ94InI@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--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