devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Varshini Rajendran <varshini.rajendran@microchip.com>
Cc: lee@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
	ychuang3@nuvoton.com, schung@nuvoton.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v6 02/27] dt-bindings: mfd: syscon: add microchip's sam9x7 sfr
Date: Tue, 30 Jul 2024 10:50:02 -0600	[thread overview]
Message-ID: <20240730165002.GA1508552-robh@kernel.org> (raw)
In-Reply-To: <20240729070603.1990265-1-varshini.rajendran@microchip.com>

On Mon, Jul 29, 2024 at 12:36:03PM +0530, Varshini Rajendran wrote:
> Add compatible for sam9x7 SoC's SFR.

That's (kind of) obvious from the diff. How is the block on the new SoC 
the same or different from the prior chip? It's kind of strange that one 
of these blocks which tend to be register bit soup of left over controls 
would be the same or a superset of another SoC.

> 
> Signed-off-by: Varshini Rajendran <varshini.rajendran@microchip.com>
> ---
> Changes in v6:
> 
>  - New patch in v6 as the syscon devices are moved to a new file
>    upstream.
> ---
>  .../devicetree/bindings/mfd/syscon.yaml       | 188 +++++++++---------
>  1 file changed, 97 insertions(+), 91 deletions(-)

Put this in your own schema file. I don't think we want get into more 
complicated cases here.

Rob

  reply	other threads:[~2024-07-30 16:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29  6:56 [PATCH v6 00/27] Add support for sam9x7 SoC family Varshini Rajendran
2024-07-29  7:05 ` [PATCH v6 01/27] dt-bindings: atmel-sysreg: add sam9x7 Varshini Rajendran
2024-07-29  7:06 ` [PATCH v6 02/27] dt-bindings: mfd: syscon: add microchip's sam9x7 sfr Varshini Rajendran
2024-07-30 16:50   ` Rob Herring [this message]
2024-07-29  7:06 ` [PATCH v6 03/27] dt-bindings: atmel-ssc: add microchip,sam9x7-ssc Varshini Rajendran
2024-07-29  7:06 ` [PATCH v6 04/27] dt-bindings: serial: atmel,at91-usart: add compatible for sam9x7 Varshini Rajendran
2024-07-29  7:06 ` [PATCH v6 05/27] dt-bindings: microchip: atmel,at91rm9200-tcb: add sam9x7 compatible Varshini Rajendran
2024-07-30 19:04   ` Rob Herring
2024-07-29  7:07 ` [PATCH v6 09/27] dt-bindings: clocks: atmel,at91sam9x5-sckc: add sam9x7 Varshini Rajendran
2024-07-29  7:07 ` [PATCH v6 10/27] dt-bindings: clocks: atmel,at91rm9200-pmc: add sam9x7 clock controller Varshini Rajendran
2024-07-29  7:08 ` [PATCH v6 14/27] dt-bindings: clock: at91: Allow PLLs to be exported and referenced in DT Varshini Rajendran
2024-07-29  7:08 ` [PATCH v6 16/27] dt-bindings: interrupt-controller: Add support for sam9x7 aic Varshini Rajendran
2024-07-29 16:24   ` Rob Herring
2024-07-29  7:09 ` [PATCH v6 21/27] dt-bindings: reset: atmel,at91sam9260-reset: add sam9x7 Varshini Rajendran
2024-07-29  7:09 ` [PATCH v6 22/27] dt-bindings: power: reset: atmel,sama5d2-shdwc: " Varshini Rajendran
2024-07-29  7:09 ` [PATCH v6 25/27] ARM: dts: at91: sam9x7: add device tree for SoC Varshini Rajendran
2024-07-31  8:30   ` Krzysztof Kozlowski
2024-08-27  9:50     ` Varshini.Rajendran
2024-08-27 12:48       ` Krzysztof Kozlowski
2024-08-28  8:25         ` Varshini.Rajendran
2024-08-28 11:49           ` Krzysztof Kozlowski
2024-09-02  6:34             ` Varshini.Rajendran
2024-07-29  7:09 ` [PATCH v6 26/27] dt-bindings: arm: add sam9x75 curiosity board Varshini Rajendran
2024-07-29  7:10 ` [PATCH v6 27/27] ARM: dts: microchip: sam9x75_curiosity: " Varshini Rajendran
2024-07-29  8:17 ` [PATCH v6 00/27] Add support for sam9x7 SoC family Andrei.Simion
2024-07-29  8:57   ` Varshini.Rajendran
2024-07-29 18:52 ` Rob Herring (Arm)
2024-08-09  6:24 ` claudiu beznea

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=20240730165002.GA1508552-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=schung@nuvoton.com \
    --cc=varshini.rajendran@microchip.com \
    --cc=ychuang3@nuvoton.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;
as well as URLs for NNTP newsgroup(s).