From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] I2C: BCM2835: Linking platform nodes to adapter nodes
Date: Mon, 25 Nov 2013 20:31:29 -0700 [thread overview]
Message-ID: <52941611.8070509@wwwdotorg.org> (raw)
In-Reply-To: <527D1870.8080302@wwwdotorg.org>
On 11/08/2013 09:59 AM, Stephen Warren wrote:
> On 11/08/2013 02:49 AM, Florian Meier wrote:
>> In order to find I2C devices in the device tree, the platform nodes
>> have to be known by the I2C core. Analogous to the i2c-omap driver
>> this requires setting the dev.of_node parameter of the adapter.
>
> (CCing the I2C maintainers...)
>
>> diff --git a/drivers/i2c/busses/i2c-bcm2835.c b/drivers/i2c/busses/i2c-bcm2835.c
>
>> @@ -299,6 +299,7 @@ static int bcm2835_i2c_probe(struct platform_device *pdev)
>> strlcpy(adap->name, "bcm2835 I2C adapter", sizeof(adap->name));
>> adap->algo = &bcm2835_i2c_algo;
>> adap->dev.parent = &pdev->dev;
>> + adap->dev.of_node = pdev->dev.of_node;
>
> Ah, that makes sense. Thinking about it now, I'd only ever used i2cget
> etc. to access I2C devices, rather than instantiating drivers from DT.
>
> That all said, I wonder if the I2C core shouldn't do something like the
> following inside i2c_add_adapter():
>
> if (!adap->dev.of_node && adap->dev.parent)
> adap->dev.of_node = adap->dev.parent->of_node;
>
> That would save every single I2C driver from having to set up this field
> manually.
BTW, this should probably be:
Cc: stable at vger.kernel.org
next prev parent reply other threads:[~2013-11-26 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 9:49 [PATCH] I2C: BCM2835: Linking platform nodes to adapter nodes Florian Meier
2013-11-08 16:59 ` Stephen Warren
2013-11-26 3:31 ` Stephen Warren [this message]
2013-11-26 13:05 ` Charles Keepax
2013-11-28 17:13 ` Mark Brown
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=52941611.8070509@wwwdotorg.org \
--to=swarren@wwwdotorg.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).