[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131126130553.GF25130@opensource.wolfsonmicro.com>
Date: Tue, 26 Nov 2013 13:05:53 +0000
From: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To: Stephen Warren <swarren@...dotorg.org>
Cc: Florian Meier <florian.meier@...lo.de>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
Wolfram Sang <wsa@...-dreams.de>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rpi-kernel@...ts.infradead.org
Subject: Re: [PATCH] I2C: BCM2835: Linking platform nodes to adapter nodes
On Fri, Nov 08, 2013 at 09:59:28AM -0700, 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;
Should this not also have an of_node_get to increment the ref
count on the node?
Thanks,
Charles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists