From: <Nicolas.Ferre@microchip.com>
To: <conor@kernel.org>, <Claudiu.Beznea@microchip.com>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<Conor.Dooley@microchip.com>, <alexandre.belloni@bootlin.com>,
<sre@kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 2/4] dt-bindings: power: reset: atmel,at91sam9260-shdwc: convert to yaml
Date: Wed, 24 May 2023 08:12:41 +0000 [thread overview]
Message-ID: <e0c5cb71-af1e-e11d-7b8f-46a47a813d25@microchip.com> (raw)
In-Reply-To: <20230523-depletion-petty-978775d05b22@spud>
Conor,
On 23/05/2023 at 20:27, Conor Dooley wrote:
[..]
>> + - atmel,at91sam9x5-shdwc
> For my own curiosity, is this x a wildcard or part of the product name?
> Quick google was slightly confusing.
In this special case, the x is indeed a wildcard, but as the underlying
silicon is the same, we choose (a long time ago) to anyway go with this
naming for the "5 series" (which does not contain the sam9g45 BTW, to
make things easier ;-)).
Regards,
Nicolas
--
Nicolas Ferre
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-24 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 6:15 [PATCH 0/4] dt-bindings: power: reset: at91: convert to YAML Claudiu Beznea
2023-05-23 6:15 ` [PATCH 1/4] ARM: dts: at91: use generic name for shutdown controller Claudiu Beznea
2023-05-23 6:15 ` [PATCH 2/4] dt-bindings: power: reset: atmel,at91sam9260-shdwc: convert to yaml Claudiu Beznea
2023-05-23 18:27 ` Conor Dooley
2023-05-24 8:12 ` Nicolas.Ferre [this message]
2023-05-23 6:15 ` [PATCH 3/4] dt-bindings: power: reset: atmel,sama5d2-shdwc: " Claudiu Beznea
2023-05-23 18:49 ` Conor Dooley
2023-05-23 6:15 ` [PATCH 4/4] MAINTAINERS: add documentation file for Microchip SAMA5D2 shutdown controller 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=e0c5cb71-af1e-e11d-7b8f-46a47a813d25@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox