From: <Andrei.Simion@microchip.com>
To: <conor@kernel.org>
Cc: <Conor.Dooley@microchip.com>, <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 v3 3/3] dt-bindings: eeprom: at24: Add Microchip 24AA025E48/24AA025E64
Date: Mon, 1 Jul 2024 14:56:20 +0000 [thread overview]
Message-ID: <b025bd8f-ca7d-4639-87e2-f51e6dca96ea@microchip.com> (raw)
In-Reply-To: <20240701-majorette-briskness-696746f3fde1@spud>
On 01.07.2024 17:47, Conor Dooley wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
>
> ForwardedMessage.eml
>
> Subject:
> Re: [PATCH v3 3/3] dt-bindings: eeprom: at24: Add Microchip 24AA025E48/24AA025E64
> From:
> Conor Dooley <conor@kernel.org>
> Date:
> 01.07.2024, 17:47
>
> To:
> Andrei.Simion@microchip.com
> CC:
> Conor.Dooley@microchip.com, 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
>
>
>
> On Mon, Jul 01, 2024 at 02:37:57PM +0000, Andrei.Simion@microchip.com wrote:
>> On 28.06.2024 12:09, Conor Dooley wrote:
>>> Hey,
>>>
>>> On Fri, Jun 28, 2024 at 11:01:46AM +0300, Andrei Simion wrote:
>>>> Add compatible for Microchip 24AA025E48/24AA025E64 EEPROMs.
>>>>
>>>> Reviewed-by: Connor Dooley <conor.dooley@microchip.com>
>>> ^^ ^
>>> There's no way that I provided a tag with my name spelt incorrectly
>>> given I use a macro to insert them. Please copy-paste tags or use b4
>>> to pick them up, rather than type them out yourself.
>>>
>>>> Signed-off-by: Andrei Simion <andrei.simion@microchip.com>
>>>> ---
>>>> v2 -> v3:
>>>> - commit subject changed to reference Microchip 24AA025E48/24AA025E64
>>>> - drop the pattern: mac02e4$ and mac02e6$ and a-z from regex
>>>> - add these two devices down at the bottom
>>>> - added Reviewed-by
>>>>
>>>> v1 -> v2:
>>>> - change pattern into "^atmel,(24(c|cs|mac)[a-z0-9]+|spd)$" to keep simpler
>>>> ---
>>>> Documentation/devicetree/bindings/eeprom/at24.yaml | 4 ++++
>>>> 1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/eeprom/at24.yaml b/Documentation/devicetree/bindings/eeprom/at24.yaml
>>>> index 3c36cd0510de..699c2bbc16f5 100644
>>>> --- a/Documentation/devicetree/bindings/eeprom/at24.yaml
>>>> +++ b/Documentation/devicetree/bindings/eeprom/at24.yaml
>>>> @@ -132,6 +132,10 @@ properties:
>>>> - renesas,r1ex24128
>>>> - samsung,s524ad0xd1
>>>> - const: atmel,24c128
>>>> + - items:
>>>> + - const: microchip,24aa025e48
>>>> + - items:
>>>> + - const: microchip,24aa025e64
>>> I don't think this patch works, the schema has a select in it that only
>>> matches ^atmel,(24(c|cs|mac)[0-9]+|spd)$. You either need to have these
>>> fall back to an existing compatible (iff actually compatible) or else do
>>> something like:
>>> diff --git a/Documentation/devicetree/bindings/eeprom/at24.yaml b/Documentation/devicetree/bindings/eeprom/at24.yaml
>>> index 699c2bbc16f5..4d46b8c5439d 100644
>>> --- a/Documentation/devicetree/bindings/eeprom/at24.yaml
>>> +++ b/Documentation/devicetree/bindings/eeprom/at24.yaml
>>> @@ -18,7 +18,9 @@ select:
>>> properties:
>>> compatible:
>>> contains:
>>> - pattern: "^atmel,(24(c|cs|mac)[0-9]+|spd)$"
>>> + anyOf:
>>> + - pattern: "^atmel,(24(c|cs|mac)[0-9]+|spd)$"
>>> + - enum: ["microchip,24aa025e48", "microchip,24aa025e64"]
>> If I use your solution (and drop both items: const) -> it is selected the compatible but does not match anything.
> My intention was that you added my diff to your existing patch.
>
I also tested this scenario, it is OK.
Thank you for your clarifications.
Andrei
> Thanks,
> Conor.
next prev parent reply other threads:[~2024-07-01 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 8:01 [PATCH v3 0/3] Read MAC address through NVMEM for sama7g5ek Andrei Simion
2024-06-28 8:01 ` [PATCH v3 1/3] eeprom: at24: avoid adjusting offset for 24AA025E{48, 64} Andrei Simion
2024-06-28 8:30 ` Bartosz Golaszewski
2024-06-28 14:17 ` Andrei.Simion
2024-06-28 14:46 ` Bartosz Golaszewski
2024-07-01 7:23 ` Andrei.Simion
2024-07-01 8:46 ` Bartosz Golaszewski
2024-07-01 10:20 ` Andrei.Simion
2024-07-01 11:16 ` Bartosz Golaszewski
2024-07-01 12:17 ` Andrei.Simion
2024-06-28 8:01 ` [PATCH v3 2/3] ARM: dts: at91: at91-sama7g5ek: add EEPROMs Andrei Simion
2024-06-28 8:01 ` [PATCH v3 3/3] dt-bindings: eeprom: at24: Add Microchip 24AA025E48/24AA025E64 Andrei Simion
2024-06-28 9:09 ` Conor Dooley
2024-07-01 14:37 ` Andrei.Simion
2024-07-01 14:47 ` Conor Dooley
2024-07-01 14:56 ` Andrei.Simion [this message]
2024-06-28 8:29 ` [PATCH v3 0/3] Read MAC address through NVMEM for sama7g5ek Arnd Bergmann
2024-06-28 14:06 ` Andrei.Simion
2024-06-28 14:25 ` Arnd Bergmann
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=b025bd8f-ca7d-4639-87e2-f51e6dca96ea@microchip.com \
--to=andrei.simion@microchip.com \
--cc=Conor.Dooley@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=conor@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;
as well as URLs for NNTP newsgroup(s).