From: dianders@chromium.org (Doug Anderson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] drm: bridge/dw_hdmi: add dw hdmi i2c bus adapter support
Date: Thu, 3 Sep 2015 09:08:06 -0700 [thread overview]
Message-ID: <CAD=FV=UOSFeKPHSQE1Mrc_d4yCu54LOTj+TRZc_+kPs1mofLxg@mail.gmail.com> (raw)
In-Reply-To: <20150903093910.GA4151@ulmo.nvidia.com>
Thierry,
On Thu, Sep 3, 2015 at 2:39 AM, Thierry Reding <treding@nvidia.com> wrote:
> Perhaps the I2C core needs to be taught to look at the adapter's
> ->dev.parent->of_node in of_find_i2c_adapter_by_node(). As I understand
> it the purpose for registering a separate struct device for each I2C
> controller is so that there's an I2C parent for all slaves. At the same
> time every controller sets up ->dev.parent, and that parent's OF node is
> what we really want when we look up an I2C adapter by OF node. In other
> words, the OF node by which I2C adapters are referenced is always that
> of its parent device, as far as I can tell.
>
> Wolfram, do you know of any cases where adapter->dev.of_node would not
> be the same as adapter->dev.parent->of_node?
This sounds pretty reasonable to me. Certainly it would be a pretty
reasonable fallback if adapter->dev.of_node was NULL.
-Doug
next prev parent reply other threads:[~2015-09-03 16:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 21:34 [PATCH v3 2/2] drm: bridge/dw_hdmi: add dw hdmi i2c bus adapter support Vladimir Zapolskiy
2015-08-31 9:22 ` Philipp Zabel
2015-09-02 22:07 ` Doug Anderson
2015-09-02 22:50 ` Russell King - ARM Linux
2015-09-02 23:00 ` Doug Anderson
2015-09-02 23:04 ` Russell King - ARM Linux
2015-09-02 23:19 ` Doug Anderson
2015-09-16 21:16 ` Vladimir Zapolskiy
2015-09-16 22:02 ` Doug Anderson
2015-09-02 23:43 ` Doug Anderson
2015-09-03 9:19 ` Russell King - ARM Linux
2015-09-03 9:39 ` Thierry Reding
2015-09-03 16:08 ` Doug Anderson [this message]
2015-09-08 22:08 ` Wolfram Sang
2015-09-16 20:04 ` Doug Anderson
2015-09-16 20:58 ` Vladimir Zapolskiy
2015-09-16 21:56 ` Doug Anderson
2015-09-16 22:18 ` Russell King - ARM Linux
2015-09-21 14:00 ` Vladimir Zapolskiy
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='CAD=FV=UOSFeKPHSQE1Mrc_d4yCu54LOTj+TRZc_+kPs1mofLxg@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.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).