From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree-spec@vger.kernel.org
Subject: Re: [PATCH dt-schema 3/3] schemas: i2c: add generic interrupt name for I2C controllers
Date: Thu, 15 Aug 2024 20:42:58 +0200 [thread overview]
Message-ID: <Zr5MMrRAw8VhIJri@shikoro> (raw)
In-Reply-To: <CAL_Jsq+FggVdyJBJ_jA=wfiK87qtwYh42+49Lu2p_mi=_+n74A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Hi Rob,
thanks for the super-fast review!
> > "smbus_alert" is a generic interrupt name for controllers, so document
> > it. Introduce also "irq" for the primary interrupt.
>
> I wouldn't add "irq". It's kind of odd in that we have it for I2C
> devices in the first place and we don't try to do that anywhere else.
Yes, I am actually happy to remove "irq". I only added it for
consistency.
> > + interrupt-names:
> > + anyOf:
> > + - {} # Any name is allowed.
> > + - items:
> > + enum:
> > + - irq
> > + - smbus_alert
>
> It doesn't really matter with the {}, but the 2nd entry is only true
> if interrupt-names only contains these 2 names. I'd use 'contains'
> rather than 'items' here.
So, just replace "items:" with "contains:", right? Should I also change
this for I2C targets and add this chunk to patch 2?
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-08-15 18:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 12:09 [PATCH dt-schema 0/3] schemas: i2c: fix "smbus_alert" handling Wolfram Sang
2024-08-15 12:09 ` [PATCH dt-schema 1/3] schemas: i2c: reword descriptions for inclusive language Wolfram Sang
2024-08-15 12:09 ` [PATCH dt-schema 2/3] schemas: i2c: clean up interrupt descriptions for I2C targets Wolfram Sang
2024-08-15 12:09 ` [PATCH dt-schema 3/3] schemas: i2c: add generic interrupt name for I2C controllers Wolfram Sang
2024-08-15 14:54 ` Rob Herring
2024-08-15 18:42 ` Wolfram Sang [this message]
2024-08-15 20:39 ` Rob Herring
2024-08-15 14:46 ` [PATCH dt-schema 0/3] schemas: i2c: fix "smbus_alert" handling Rob Herring
2024-08-15 18:36 ` Wolfram Sang
2024-08-15 20:36 ` Rob Herring
2024-08-15 21:23 ` Wolfram Sang
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=Zr5MMrRAw8VhIJri@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree-spec@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@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