From: michael@walle.cc (Michael Walle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] spi-orion: add device tree binding
Date: Sun, 3 Jun 2012 23:48:49 +0200 [thread overview]
Message-ID: <201206032348.49208.michael@walle.cc> (raw)
In-Reply-To: <20120603210123.GL14756@titan.lakedaemon.net>
Hi Jason,
Am Sonntag 03 Juni 2012, 23:01:23 schrieb Jason Cooper:
> On Sun, Jun 03, 2012 at 10:17:56PM +0200, Michael Walle wrote:
> > Signed-off-by: Michael Walle <michael@walle.cc>
> > ---
> >
> > .../devicetree/bindings/spi/spi-orion.txt | 5 +++++
> > drivers/spi/spi-orion.c | 11 +++++++++++
> > 2 files changed, 16 insertions(+), 0 deletions(-)
> > create mode 100644 Documentation/devicetree/bindings/spi/spi-orion.txt
> >
> > diff --git a/Documentation/devicetree/bindings/spi/spi-orion.txt
> > b/Documentation/devicetree/bindings/spi/spi-orion.txt new file mode
> > 100644
> > index 0000000..e68597a
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/spi/spi-orion.txt
> > @@ -0,0 +1,5 @@
> > +Marvell Orion SPI device
> > +
> > +Required properties:
> > +- compatible : should be "marvell,orion-spi".
>
> The above is correct, and a change in policy from when dreamplug DT
> support was first added.
>
> > +- reg : offset and length of the register set for the device
> > diff --git a/drivers/spi/spi-orion.c b/drivers/spi/spi-orion.c
> > index 2760450..2de58bb 100644
> > --- a/drivers/spi/spi-orion.c
> > +++ b/drivers/spi/spi-orion.c
> > @@ -17,6 +17,7 @@
> >
> > #include <linux/io.h>
> > #include <linux/spi/spi.h>
> > #include <linux/module.h>
> >
> > +#include <linux/of.h>
> >
> > #include <linux/clk.h>
> > #include <asm/unaligned.h>
> >
> > @@ -506,6 +507,7 @@ static int __init orion_spi_probe(struct
> > platform_device *pdev)
> >
> > if (orion_spi_reset(spi) < 0)
> >
> > goto out_rel_mem;
> >
> > + master->dev.of_node = pdev->dev.of_node;
> >
> > status = spi_register_master(master);
> > if (status < 0)
> >
> > goto out_rel_mem;
> >
> > @@ -547,10 +549,19 @@ static int __exit orion_spi_remove(struct
> > platform_device *pdev)
> >
> > MODULE_ALIAS("platform:" DRIVER_NAME);
> >
> > +#ifdef CONFIG_OF
> > +static const struct of_device_id orion_spi_of_match_table[]
> > __devinitdata = { + { .compatible = "mrvl,orion-spi", },
>
> Please make this consistent with the documentation, "marvell,orion-spi",
> thanks. That'll be one less to convert over later.
oh, actually i forgot to change the documentation. wasnt the convention to use
the name used in the stock exchange?
eg. the nand driver uses mrvl,orion-nand, or kirkwood itself is named
"mrvl,kirkwood".
Or did i miss sth, because you wrote "one less to convert over later"?
--
michael
next prev parent reply other threads:[~2012-06-03 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 20:17 [PATCH 1/3] spi-orion: add device tree binding Michael Walle
2012-06-03 20:17 ` [PATCH 2/3] ARM: kirkwood: use devicetree for orion-spi Michael Walle
2012-06-03 20:17 ` [PATCH 3/3] ARM: kirkwood: use devicetree for SPI on dreamplug Michael Walle
2012-06-03 21:01 ` [PATCH 1/3] spi-orion: add device tree binding Jason Cooper
2012-06-03 21:48 ` Michael Walle [this message]
2012-06-07 20:27 ` Jason Cooper
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=201206032348.49208.michael@walle.cc \
--to=michael@walle.cc \
--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).