From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: serial: snps-dw-apb-uart: Simplify DMA-less RZ/N1 rule
Date: Thu, 10 Apr 2025 10:33:27 +0200 [thread overview]
Message-ID: <Z_eCV8aTmr4t1_xZ@shikoro> (raw)
In-Reply-To: <90c7aa143beb6a28255b24e8ef8c96180d869cbb.1744271974.git.geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
> - - enum:
> - - renesas,r9a06g032-uart
> - - renesas,r9a06g033-uart
> + - {}
What about simply dropping r9a06g033 which cannot run Linux (no RAM
controller, only 6MB internal RAM) and there hasn't been any upstreaming
effort for other OS in the last 7 years? And making the remaining
r9a06g032 just const? Why should we allow everything there? Do we want
to support that?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-04-10 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 8:00 [PATCH] dt-bindings: serial: snps-dw-apb-uart: Simplify DMA-less RZ/N1 rule Geert Uytterhoeven
2025-04-10 8:33 ` Wolfram Sang [this message]
2025-04-10 8:36 ` Geert Uytterhoeven
2025-04-10 9:37 ` Wolfram Sang
2025-04-10 10:56 ` Geert Uytterhoeven
2025-04-10 20:29 ` Wolfram Sang
2025-04-11 13:38 ` Rob Herring
2025-04-11 15:37 ` Wolfram Sang
2025-04-11 16:16 ` Rob Herring
2025-04-11 19:12 ` Wolfram Sang
2025-04-23 12:10 ` Geert Uytterhoeven
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=Z_eCV8aTmr4t1_xZ@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.