From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Wolfram Sang <wsa@kernel.org>, <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>
Subject: Re: [PATCH v2 1/2] dt-bindings: i2c: add property to avoid device detection
Date: Mon, 16 May 2022 08:43:38 +0200 [thread overview]
Message-ID: <20220516064338.GA28916@axis.com> (raw)
In-Reply-To: <Yn+8CJ3j2SY2+Mq+@shikoro>
On Sat, May 14, 2022 at 04:26:16PM +0200, Wolfram Sang wrote:
> 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?
Is it always safe to not do this detection if we have a firmware node?
Then maybe the core could just always skip it in that case without
looking for a special property or requiring individual drivers to choose
what to do?
next prev parent reply other threads:[~2022-05-16 6:43 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 [this message]
2022-05-16 7:12 ` Wolfram Sang
2022-05-16 7:57 ` Peter Rosin
2022-05-16 8:07 ` Peter Rosin
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=20220516064338.GA28916@axis.com \
--to=vincent.whitchurch@axis.com \
--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=robh+dt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.