All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	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>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-serial@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: serial: snps-dw-apb-uart: document RZ/N1 binding without DMA
Date: Tue, 18 Mar 2025 10:11:06 +0100	[thread overview]
Message-ID: <Z9k4qrFXCRf23MDo@shikoro> (raw)
In-Reply-To: <CAMuHMdWP8a5eR_1sk2oUe02KdiDaibHnqAHbn2mSyBHzP1FNJA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]


> > +            - enum:
> > +                - renesas,r9a06g032-uart
> > +                - renesas,r9a06g033-uart
> 
> I think you can simplify by replacing the enum by
> 
>     - pattern: "^renesas,.*$"

I still plan to remove r9a06g033 bindings from the kernel because that
SoC cannot run Linux with only 4MB of internal SRAM. So, all this will
become "const: renesas,r9a06g032-uart" in the future anyhow. But one
step after the other...


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-03-18  9:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  8:53 [PATCH] dt-bindings: serial: snps-dw-apb-uart: document RZ/N1 binding without DMA Wolfram Sang
2025-03-18  9:05 ` Geert Uytterhoeven
2025-03-18  9:11   ` Wolfram Sang [this message]
2025-03-18  9:22     ` Geert Uytterhoeven
2025-03-18  9:26       ` Wolfram Sang
2025-03-18  9:32 ` Miquel Raynal
2025-03-21 16:06 ` Rob Herring (Arm)
  -- strict thread matches above, loose matches on Subject: below --
2025-03-17 12:04 Wolfram Sang
2025-03-17 13:13 ` Geert Uytterhoeven
2025-03-17 16:01   ` Wolfram Sang

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=Z9k4qrFXCRf23MDo@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --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=magnus.damm@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --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.