devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Jagath Jog J <jagathjog1996@gmail.com>,
	<andriy.shevchenko@linux.intel.com>, <lars@metafoo.de>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [RFC 1/2] dt-bindings: iio: imu: Add DT binding doc for BMI323
Date: Fri, 13 Oct 2023 09:16:15 +0100	[thread overview]
Message-ID: <20231013091615.00007399@Huawei.com> (raw)
In-Reply-To: <CACRpkdY4yJKmc_Sbr=4sJ0WseCEEBOQ7wKj4fBUMG2_cx-Xxbw@mail.gmail.com>

On Tue, 10 Oct 2023 21:51:17 +0200
Linus Walleij <linus.walleij@linaro.org> wrote:

> On Tue, Oct 10, 2023 at 4:42 PM Jonathan Cameron <jic23@kernel.org> wrote:
> 
> > We kind of lost the question along the way.  Wasn't so much about whether
> > there was a generic binding but more about whether it is worth providing
> > separate controls for the two IRQ pins?  Or just assume no one is crazy
> > enough to play that level of mix and match.  
> 
> Ugh no, that's upfront design for a nonexistent use case.
> 
> - First, to even consider open drain the designer need to be really
>   short of IRQ lines/rails, and, despite knowing it's a bad idea, decide
>   to share this line between several peripherals, even though it will
>   require I2C traffic to just determine which one even fired the IRQ.
> 
> - Second, be interested in using two IRQs to distinguish between
>   different events? When we just faced the situation that we had
>   too few IRQ lines so we need to start sharing them with open
>   drain...?
> 
> It's not gonna happen.
> 
> Stay with just drive-open-drain; and configure them all as that if
> that property is set.

Good insights, I'd not really thought about the wider reasons for using
this :)  Not done any circuit design or embedded board bring up in a
long while.

Thanks!

> 
> Yours,
> Linus Walleij
> 


  reply	other threads:[~2023-10-13  8:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  8:03 [RFC 0/2] iio: imu: Add driver and dt-bindings for BMI323 Jagath Jog J
2023-09-18  8:03 ` [RFC 1/2] dt-bindings: iio: imu: Add DT binding doc " Jagath Jog J
2023-09-18 12:25   ` Krzysztof Kozlowski
2023-09-19 16:44     ` Jagath Jog J
2023-09-24 13:31       ` Jonathan Cameron
2023-09-27 21:37         ` Jagath Jog J
2023-09-24 13:37   ` Jonathan Cameron
2023-09-27 21:37     ` Jagath Jog J
2023-09-30 16:05       ` Jonathan Cameron
2023-10-08  6:24         ` Jagath Jog J
2023-10-10  9:00           ` Jonathan Cameron
2023-10-10  9:06             ` Linus Walleij
2023-10-10 14:42               ` Jonathan Cameron
2023-10-10 19:51                 ` Linus Walleij
2023-10-13  8:16                   ` Jonathan Cameron [this message]
2023-10-13 16:23                     ` Jagath Jog J
2023-09-18  8:03 ` [RFC 2/2] iio: imu: Add driver for BMI323 IMU Jagath Jog J
2023-09-18 10:03   ` Andy Shevchenko
2023-09-19 22:43     ` Jagath Jog J
2023-09-20 13:24       ` Andy Shevchenko
2023-10-08  6:25       ` Jagath Jog J
2023-10-10  9:02         ` Jonathan Cameron
2023-09-24 14:30   ` Jonathan Cameron
2023-09-27 19:59     ` Jagath Jog J
2023-09-27 21:25       ` Denis Benato
2023-09-29  7:59         ` Jagath Jog J
2023-09-30 16:17           ` Jonathan Cameron
2023-10-01 13:53           ` Denis Benato
2023-10-03 20:35             ` Jagath Jog J
2023-09-30 16:13       ` Jonathan Cameron
2023-09-27  9:57   ` Uwe Kleine-König
2023-09-27 12:35     ` Andy Shevchenko
2023-09-27 14:34       ` Uwe Kleine-König
2023-10-01  8:20         ` Andy Shevchenko
2023-09-28 18:19     ` Jagath Jog J
2023-09-28 20:48       ` Uwe Kleine-König

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=20231013091615.00007399@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jagathjog1996@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).