From: Conor Dooley <conor@kernel.org>
To: Andrei.Simion@microchip.com
Cc: robh@kernel.org, brgl@bgdev.pl, krzk+dt@kernel.org,
conor+dt@kernel.org, Nicolas.Ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
arnd@arndb.de, gregkh@linuxfoundation.org,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] dt-bindings: eeprom: at24: Add at24,mac02e4 and at24,mac02e6
Date: Tue, 25 Jun 2024 17:15:01 +0100 [thread overview]
Message-ID: <20240625-satisfy-froth-decbe11ba388@spud> (raw)
In-Reply-To: <53820e28-f512-4129-9a17-a549ef664755@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 2749 bytes --]
On Tue, Jun 25, 2024 at 07:33:18AM +0000, Andrei.Simion@microchip.com wrote:
> On 24.06.2024 22:49, Rob Herring wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Fri, Jun 21, 2024 at 03:13:40PM +0300, Andrei Simion wrote:
> >> Update regex check and add pattern to match both EEPROMs.
> >
> > The subject is wrong as 'at24' is not the vendor.
> >
>
> My mistake. It needs to be atmel,24mac02e4 and atmel,24mac02e6.
>
> >>
> >> Signed-off-by: Andrei Simion <andrei.simion@microchip.com>
> >> ---
> >> v1 -> v2:
> >> - change patter into "^atmel,(24(c|cs|mac)[a-z0-9]+|spd)$" to keep simpler
> >> ---
> >> Documentation/devicetree/bindings/eeprom/at24.yaml | 10 +++++++---
> >> 1 file changed, 7 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/Documentation/devicetree/bindings/eeprom/at24.yaml b/Documentation/devicetree/bindings/eeprom/at24.yaml
> >> index 3c36cd0510de..f914ca37ceea 100644
> >> --- a/Documentation/devicetree/bindings/eeprom/at24.yaml
> >> +++ b/Documentation/devicetree/bindings/eeprom/at24.yaml
> >> @@ -18,7 +18,7 @@ select:
> >> properties:
> >> compatible:
> >> contains:
> >> - pattern: "^atmel,(24(c|cs|mac)[0-9]+|spd)$"
> >> + pattern: "^atmel,(24(c|cs|mac)[a-z0-9]+|spd)$"
> >> required:
> >> - compatible
> >>
> >> @@ -37,8 +37,8 @@ properties:
> >> - allOf:
> >> - minItems: 1
> >> items:
> >> - - pattern: "^(atmel|catalyst|microchip|nxp|ramtron|renesas|rohm|st),(24(c|cs|lc|mac)[0-9]+|spd)$"
> >> - - pattern: "^atmel,(24(c|cs|mac)[0-9]+|spd)$"
> >> + - pattern: "^(atmel|catalyst|microchip|nxp|ramtron|renesas|rohm|st),(24(c|cs|lc|mac)[a-z0-9]+|spd)$"
> >> + - pattern: "^atmel,(24(c|cs|mac)[a-z0-9]+|spd)$"
> >
> > Are these devices available from multiple vendors? If not, I think I'd
> > add specific compatible strings with the right vendor rather than adding
> > to this pattern. It's rather loosely defined because that's what was in
> > use already.
> >
>
> So, would you like me to keep how it was before: "^atmel,(24(c|cs|mac)[0-9]+|spd)$" and "^(atmel|catalyst|microchip|nxp|ramtron|renesas|rohm|st),(24(c|cs|lc|mac)[0-9]+|spd)$"
> and to add only:
> - items:
> pattern: mac02e4$
> - items:
> pattern: mac02e6$
> ?
>
> Or would you like me to add to "the special cases that don't conform to the above pattern. Each requires a standard at24 model as fallback." area?
I think the suggestion is to explicitly add these two devices down at the
bottom instead of adding to the regex. The first hunk I think in this
patch needs to remain a regex.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-06-25 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 12:13 [PATCH v2 0/3] Read MAC address through NVMEM for sama7g5ek Andrei Simion
2024-06-21 12:13 ` [PATCH v2 1/3] eeprom: at24: avoid adjusting offset for 24AA025E{48, 64} Andrei Simion
2024-06-26 8:16 ` Bartosz Golaszewski
2024-06-21 12:13 ` [PATCH v2 2/3] ARM: dts: at91: at91-sama7g5ek: add EEPROMs Andrei Simion
2024-06-21 12:13 ` [PATCH v2 3/3] dt-bindings: eeprom: at24: Add at24,mac02e4 and at24,mac02e6 Andrei Simion
2024-06-21 14:14 ` Conor Dooley
2024-06-24 19:49 ` Rob Herring
2024-06-25 7:33 ` Andrei.Simion
2024-06-25 16:15 ` Conor Dooley [this message]
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=20240625-satisfy-froth-decbe11ba388@spud \
--to=conor@kernel.org \
--cc=Andrei.Simion@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox