From: Jamie Iles <jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
To: Artem Bityutskiy <dedekind1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [PATCHv4] mtd: gpio-nand: add device tree bindings
Date: Mon, 15 Aug 2011 15:38:16 +0100 [thread overview]
Message-ID: <20110815143816.GH2636@pulham.picochip.com> (raw)
In-Reply-To: <1313418543.2600.2.camel@sauron>
On Mon, Aug 15, 2011 at 05:28:57PM +0300, Artem Bityutskiy wrote:
> On Tue, 2011-08-09 at 16:12 +0100, Jamie Iles wrote:
> > - res1 = platform_get_resource(dev, IORESOURCE_MEM, 1);
> > + if (!dev->dev.of_node)
> > + res1 = platform_get_resource(dev, IORESOURCE_MEM, 1);
> > + else
> > + res1 = gpio_nand_of_get_io_sync(&dev->dev);
> > +
> > if (res1) {
> > gpiomtd->io_sync = request_and_remap(res1, 4, "NAND sync", &ret);
> > if (!gpiomtd->io_sync) {
> > @@ -257,7 +362,16 @@ static int __devinit gpio_nand_probe(struct platform_device *dev)
> > }
> > }
> >
> > - memcpy(&gpiomtd->plat, dev->dev.platform_data, sizeof(gpiomtd->plat));
> > + if (dev->dev.of_node)
> > + kfree(res1);
> > +
> > + if (dev->dev.platform_data)
> > + memcpy(&gpiomtd->plat, dev->dev.platform_data,
> > + sizeof(gpiomtd->plat));
> > + else
> > + ret = gpio_nand_of_get_config(&dev->dev, &gpiomtd->plat);
> > + if (ret)
> > + goto err_nce;
> >
>
> So with this code you can mix platform data and DT? Say, io_sync may
> come from platform data and the rest from the DT? Is this normal
> practice?
Well you can use platform_data with DT - it's the only way to pass
function pointers for example, but I'm not convinced it's required in
this case (there is the adjust_parts callback, but I can't see a user of
it) so I'd be inclined to change the conditionals to:
if (!dev->dev.of_node)
memcpy(&gpiomtd->plat, dev->dev.platform_data, ...);
else
gpio_nand_of_get_config(...);
so that we don't use platform_data for the DT case.
Jamie
next prev parent reply other threads:[~2011-08-15 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 15:12 [PATCHv4] mtd: gpio-nand: add device tree bindings Jamie Iles
[not found] ` <1312902747-21372-1-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
2011-08-10 15:13 ` Scott Wood
[not found] ` <4E42A017.7040608-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-08-11 9:00 ` Jamie Iles
2011-08-15 13:57 ` Artem Bityutskiy
2011-08-15 13:58 ` Jamie Iles
2011-08-15 14:28 ` Artem Bityutskiy
2011-08-15 14:38 ` Jamie Iles [this message]
2011-08-15 14:45 ` Artem Bityutskiy
2011-08-15 15:24 ` Jamie Iles
[not found] ` <20110815152447.GI2636-apL1N+EY0C9YtYNIL7UdTEEOCMrvLtNR@public.gmane.org>
2011-08-19 19:51 ` Artem Bityutskiy
2011-08-19 21:18 ` Jamie Iles
2011-08-20 3:39 ` Artem Bityutskiy
2011-08-20 6:38 ` Jamie Iles
2011-08-20 12:09 ` Artem Bityutskiy
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=20110815143816.GH2636@pulham.picochip.com \
--to=jamie-wmlquqddiekakbo8gow8eq@public.gmane.org \
--cc=dedekind1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.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).