From: Peter Rosin <peda@axentia.se>
To: Wolfram Sang <wsa@kernel.org>,
Vincent Whitchurch <vincent.whitchurch@axis.com>,
kernel@axis.com, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, krzk+dt@kernel.org,
robh+dt@kernel.org, linux-kernel@vger.kernel.org,
luca@lucaceresoli.net
Subject: Re: [PATCH v2 1/2] dt-bindings: i2c: add property to avoid device detection
Date: Mon, 16 May 2022 10:07:20 +0200 [thread overview]
Message-ID: <758ebcab-b0a2-29bd-d79c-1fbdc95212ae@axentia.se> (raw)
In-Reply-To: <7ab1f387-3670-4b49-211d-3ff9a7c3d40b@axentia.se>
[Now with the proper email to Luca, sorry about that...]
2022-05-16 at 09:57, Peter Rosin wrote:
> 2022-05-14 at 16:26, Wolfram Sang wrote:
>> On Tue, Apr 12, 2022 at 10:50:45AM +0200, Vincent Whitchurch wrote:
>>> When drivers with ->detect callbacks are loaded, the I2C core does a
>>> bunch of transactions to try to probe for these devices, regardless of
>>> whether they are specified in the devicetree or not. (This only happens
>>> on I2C controllers whose drivers enable the I2C_CLASS* flags, but this
>>> is the case for generic drivers like i2c-gpio.)
>>>
>>> These kinds of transactions are unnecessary on systems where the
>>> devicetree specifies all the devices on the I2C bus, so add a property
>>> to indicate that the devicetree description of the hardware is complete
>>> and thus allow this discovery to be disabled.
>> Hmm, I don't think the name is fitting. "no-detect" is the desired
>> behaviour but a proper description is more like "bus-complete" or
>> something?
>>
>> That aside, I am not sure we should handle this at DT level. Maybe we
>> should better change the GPIO driver to not populate a class if we have
>> a firmware node?
> We also have the somewhat related address translation case (which I
> still need to look at). [Adding Luca to Cc]
>
> https://lore.kernel.org/lkml/20220206115939.3091265-1-luca@lucaceresoli.net/
>
> If a bus is "bus-complete", then address translation could use
> any unused address instead of from an explicit list of addresses.
> I.e. the "i2c-alias-pool" in the binding in patch 4/6 of that
> series could be made optional if the bus is "bus-complete".
>
> Not sure how much value there is in that?
>
> Cheers,
> Peter
next prev parent reply other threads:[~2022-05-16 8:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 8:50 [PATCH v2 0/2] i2c: Allow disabling auto detection via devicetree Vincent Whitchurch
2022-04-12 8:50 ` [PATCH v2 1/2] dt-bindings: i2c: add property to avoid device detection Vincent Whitchurch
2022-04-12 8:52 ` Krzysztof Kozlowski
2022-04-12 21:22 ` Rob Herring
2022-04-14 8:55 ` Vincent Whitchurch
2022-04-14 19:40 ` Rob Herring
2022-05-14 14:26 ` Wolfram Sang
2022-05-16 6:43 ` Vincent Whitchurch
2022-05-16 7:12 ` Wolfram Sang
2022-05-16 7:57 ` Peter Rosin
2022-05-16 8:07 ` Peter Rosin [this message]
2022-05-18 16:09 ` Luca Ceresoli
2022-04-12 8:50 ` [PATCH v2 2/2] i2c: core: support no-detect property Vincent Whitchurch
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=758ebcab-b0a2-29bd-d79c-1fbdc95212ae@axentia.se \
--to=peda@axentia.se \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@lucaceresoli.net \
--cc=robh+dt@kernel.org \
--cc=vincent.whitchurch@axis.com \
--cc=wsa@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).