From: Conor Dooley <conor@kernel.org>
To: Andrei Simion <andrei.simion@microchip.com>
Cc: brgl@bgdev.pl, robh@kernel.org, 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 3/3] dt-bindings: eeprom: at24: Add at24,mac02e4 and at24,mac02e6
Date: Wed, 19 Jun 2024 18:53:47 +0100 [thread overview]
Message-ID: <20240619-thee-herald-82725e1526e2@spud> (raw)
In-Reply-To: <20240619072231.6876-4-andrei.simion@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
On Wed, Jun 19, 2024 at 10:22:31AM +0300, Andrei Simion wrote:
> Update regex check and add pattern to match both EEPROMs.
>
> Signed-off-by: Andrei Simion <andrei.simion@microchip.com>
> ---
> 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..46daa662f6e7 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)[0-9]+[a-z0-9]*|spd)$"
Could we relax the pattern instead to make this bloat less? Would it be
problematic to just allow "^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)[0-9]+[a-z0-9]*|spd)$"
> + - pattern: "^atmel,(24(c|cs|mac)[0-9]+[a-z0-9]*|spd)$"
> - oneOf:
> - items:
> pattern: c00$
> @@ -54,6 +54,10 @@ properties:
> pattern: mac402$
> - items:
> pattern: mac602$
> + - items:
> + pattern: mac02e4$
> + - items:
> + pattern: mac02e6$
> - items:
> pattern: c04$
> - items:
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-19 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 7:22 [PATCH 0/3] Read MAC address through NVMEM for sama7g5ek Andrei Simion
2024-06-19 7:22 ` [PATCH 1/3] eeprom: at24: avoid adjusting offset for 24AA025E{48, 64} Andrei Simion
2024-06-19 7:22 ` [PATCH 2/3] ARM: dts: at91: at91-sama7g5ek: add EEPROMs Andrei Simion
2024-06-20 6:28 ` kernel test robot
2024-06-19 7:22 ` [PATCH 3/3] dt-bindings: eeprom: at24: Add at24,mac02e4 and at24,mac02e6 Andrei Simion
2024-06-19 17:53 ` Conor Dooley [this message]
2024-06-20 10:45 ` Andrei.Simion
2024-06-20 11:10 ` Conor Dooley
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=20240619-thee-herald-82725e1526e2@spud \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andrei.simion@microchip.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=nicolas.ferre@microchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox