From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 09/10 RESEND] spi: Add SSP/SPI device tree documentation
Date: Tue, 24 Jul 2012 21:43:48 +0200 [thread overview]
Message-ID: <201207242143.49038.marex@denx.de> (raw)
In-Reply-To: <500EE64B.8080103@mvista.com>
Dear Sergei Shtylyov,
> Hello.
>
> On 07/24/2012 12:40 AM, Marek Vasut wrote:
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Attila Kinali <attila@kinali.ch>
> > Cc: Chris Ball <cjb@laptop.org>
> > CC: Dong Aisheng <b29396@freescale.com>
> > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > Cc: Grant Likely <grant.likely@secretlab.ca>
> > Cc: Linux ARM kernel <linux-arm-kernel@lists.infradead.org>
> > Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > CC: Shawn Guo <shawn.guo@linaro.org>
> > ---
> >
> > Documentation/devicetree/bindings/spi/mxs-spi.txt | 18
> > ++++++++++++++++++ 1 file changed, 18 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/spi/mxs-spi.txt
> >
> > diff --git a/Documentation/devicetree/bindings/spi/mxs-spi.txt
> > b/Documentation/devicetree/bindings/spi/mxs-spi.txt new file mode 100644
> > index 0000000..f1263a9
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/spi/mxs-spi.txt
> > @@ -0,0 +1,18 @@
> > +* Freescale MX233/MX28 SSP/SPI
> > +
> > +Required properties:
> > +- compatible: Should be "fsl,<soc>-spi", where soc is "imx23" or "imx28"
> > +- reg: Offset and length of the register set for the device
> > +- interrupts: Should contain SSP interrupts (error irq first, dma irq
> > second) +- fsl,ssp-dma-channel: APBX DMA channel for the SSP
> > +
> > +Example:
> > +
> > +ssp0: ssp at 80010000 {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + compatible = "fsl,imx28-spi";
> > + reg = <0x80010000 2000>;
>
> Not 0x2000?
This is actually not the first place I was curious about in the imx28 DTS ...
yes, the size is 0x2000, but "2000" as is is used in multiple places across
imx28. Shawn?
> WBR, Sergei
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-24 19:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 20:40 [PATCH 00/10 V2] MXS SPI driver Marek Vasut
2012-07-23 20:40 ` [PATCH 01/10 RESEND] mmc: spi: Move SSP register definitions into separate file Marek Vasut
2012-07-23 20:40 ` [PATCH 02/10 RESEND] mmc: spi: Rename IMX2[38]_MMC to IMX2[38]_SSP Marek Vasut
2012-07-23 20:40 ` [PATCH 03/10 V2] mmc: spi: Add necessary bits into mxs-spi.h Marek Vasut
2012-07-23 20:40 ` [PATCH 04/10 RESEND] mmc: spi: Pull out parts shared between MMC and SPI Marek Vasut
2012-07-23 20:40 ` [PATCH 05/10 V2] mmc: spi: Pull out the SSP clock configuration function Marek Vasut
2012-07-23 20:40 ` [PATCH 06/10 V2] spi: Add SPI driver for mx233/mx28 Marek Vasut
2012-08-01 20:31 ` Mark Brown
2012-08-02 14:58 ` Marek Vasut
2012-08-02 16:00 ` Mark Brown
2012-08-02 16:03 ` Marek Vasut
2012-08-03 1:29 ` Shawn Guo
2012-08-03 13:38 ` Thomas Petazzoni
2012-08-03 13:46 ` Fabio Estevam
2012-08-03 13:49 ` Marek Vasut
2012-08-03 14:00 ` Marek Vasut
2012-07-23 20:40 ` [PATCH 07/10 RESEND] mmc: spi: Pull out common DMA parts from MXS MMC Marek Vasut
2012-07-23 20:40 ` [PATCH 08/10 RESEND] spi: Add DMA support into SPI driver Marek Vasut
2012-08-01 20:34 ` Mark Brown
2012-08-02 15:00 ` Marek Vasut
2012-07-23 20:40 ` [PATCH 09/10 RESEND] spi: Add SSP/SPI device tree documentation Marek Vasut
2012-07-24 18:15 ` Sergei Shtylyov
2012-07-24 19:43 ` Marek Vasut [this message]
2012-07-28 11:40 ` Shawn Guo
2012-07-28 11:42 ` Marek Vasut
2012-07-23 20:40 ` [PATCH 10/10 RESEND] ARM: mx28: Add SPI pinmux into imx28.dtsi Marek Vasut
2012-07-24 9:25 ` [PATCH 00/10 V2] MXS SPI driver Attila Kinali
2012-08-03 14:30 ` [PATCH] SPI: MXS: Allow to pass the SPI master bus number from the device tree Maxime Ripard
2012-08-03 14:43 ` Shawn Guo
2012-08-03 16:27 ` Maxime Ripard
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=201207242143.49038.marex@denx.de \
--to=marex@denx.de \
--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).