From: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org,
Michael Walle <michael-QKn5cuLxLXY@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
machael-QKn5cuLxLXY@public.gmane.org,
Michael Walle <micheal-QKn5cuLxLXY@public.gmane.org>
Subject: Re: [PATCH 5/9] ARM: kirkwood: use devicetree for orion-spi
Date: Thu, 14 Jun 2012 11:31:35 +0200 [thread overview]
Message-ID: <20120614093135.GE4799@lunn.ch> (raw)
In-Reply-To: <201206132110.31011.arnd-r2nGTMty4D4@public.gmane.org>
On Wed, Jun 13, 2012 at 09:10:30PM +0000, Arnd Bergmann wrote:
> On Sunday 10 June 2012, Andrew Lunn wrote:
> > @@ -26,6 +26,11 @@ static struct of_device_id kirkwood_dt_match_table[] __initdata = {
> > { }
> > };
> >
> > +struct of_dev_auxdata kirkwood_auxdata_lookup[] __initdata = {
> > + OF_DEV_AUXDATA("marvell,orion-spi", 0xf1010600, "orion_spi.0", NULL),
> > + {},
> > +};
> > +
> > static void __init kirkwood_dt_init(void)
> > {
>
> How about instead adding the clkdev for "f1010600.spi" so you don't need the auxdata?
We either have auxdata and clean clock code, or no auxdata and messy
clock code with lots of aliases.
The auxdata is also not limited to the name of the clocks. It allows
me to diff the kernel log for a DT boot and a none DT boot of the same
box and see they are identical. I've found a few typo's that way, and
not been hindered by noise of the devices changing name is useful.
Once we have the clock tree described in DT, then i think it makes
sense to remove these auxdata entries.
Andrew
next prev parent reply other threads:[~2012-06-14 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 10:31 [PATCH 5/9] ARM: kirkwood: use devicetree for orion-spi Andrew Lunn
[not found] ` <1339324322-29388-6-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2012-06-10 17:06 ` Jason Cooper
[not found] ` <20120610170620.GW14756-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2012-06-12 12:04 ` Andrew Lunn
[not found] ` <20120612120433.GA17893-g2DYL2Zd6BY@public.gmane.org>
2012-06-12 18:13 ` Jason Cooper
2012-06-13 21:10 ` Arnd Bergmann
[not found] ` <201206132110.31011.arnd-r2nGTMty4D4@public.gmane.org>
2012-06-14 9:31 ` Andrew Lunn [this message]
[not found] ` <20120614093135.GE4799-g2DYL2Zd6BY@public.gmane.org>
2012-06-14 10:54 ` Arnd Bergmann
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=20120614093135.GE4799@lunn.ch \
--to=andrew-g2dyl2zd6by@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=machael-QKn5cuLxLXY@public.gmane.org \
--cc=michael-QKn5cuLxLXY@public.gmane.org \
--cc=micheal-QKn5cuLxLXY@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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).