linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] ARM: dts: imx27-phytec-phycore-rdk: Add spidev node
Date: Sat, 8 Jun 2013 19:57:54 +0200	[thread overview]
Message-ID: <20130608175754.GM32299@pengutronix.de> (raw)
In-Reply-To: <1370712019.891315204@f13.mail.ru>

On Sat, Jun 08, 2013 at 09:20:19PM +0400, Alexander Shiyan wrote:
> > On Sat, Jun 08, 2013 at 06:39:39PM +0400, Alexander Shiyan wrote:
> > > This patch adds spidev device for spi0.1 which is used on ZigBee
> > > PCM970 connector.  This change will help to use this connector in
> > > userspace.
> > > 
> > > Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> > > ---
> > >  arch/arm/boot/dts/imx27-phytec-phycore-rdk.dts | 6 ++++++
> > >  1 file changed, 6 insertions(+)
> > > 
> > > diff --git a/arch/arm/boot/dts/imx27-phytec-phycore-rdk.dts b/arch/arm/boot/dts/imx27-phytec-phycore-rdk.dts
> > > index e7ed978..b2dbcdd 100644
> > > --- a/arch/arm/boot/dts/imx27-phytec-phycore-rdk.dts
> > > +++ b/arch/arm/boot/dts/imx27-phytec-phycore-rdk.dts
> > > @@ -17,6 +17,12 @@
> > >  &cspi1 {
> > >  	fsl,spi-num-chipselects = <2>;
> > >  	cs-gpios = <&gpio4 28 0>, <&gpio4 27 0>;
> > > +
> > > +	zigbee: spidev at 1 {
> > > +		compatible = "rohm,dh2228fv";
> > > +		reg = <1>;
> > > +		spi-max-frequency = <0>;
> > 
> > Why specify a speed of 0 here? Also, is there really a dh2228fv
> > connected or is this just a hack to let the Linux spidev driver match?
> 
> Zero in this case is indicates using SPI-controller maximum speed.
> This can be overriden by using SPI_IOC_RD_MAX_SPEED_HZ IOCTL
> for spidev device.
> About using dh2228fv, of course no. Currently this is only one dt entry
> for spidev exist, so yes, this a trick.

Then you should convince the spidev maintainers that whatever really is
connected there should be added to the spidev compatible list. Just
using an arbitrary binding only because the kernel happens to do the
right thing at the moment is not an option.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2013-06-08 17:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08 14:39 [PATCH 1/5] ARM: dts: i.MX27: Add DMA devicetree node Alexander Shiyan
2013-06-08 14:39 ` [PATCH 2/5] ARM: dts: i.MX27: Add SDHC devicetree nodes Alexander Shiyan
2013-06-08 14:39 ` [PATCH 3/5] ARM: dts: imx27-phytec-phycore-rdk: Add SDHC support Alexander Shiyan
2013-06-08 14:39 ` [PATCH 4/5] ARM: dts: imx27-phytec-phycore-rdk: Add spidev node Alexander Shiyan
2013-06-08 17:08   ` Sascha Hauer
2013-06-08 17:20     ` Re[2]: " Alexander Shiyan
2013-06-08 17:57       ` Sascha Hauer [this message]
2013-06-08 14:39 ` [PATCH 5/5] ARM: dts: imx27-phytec-phycore-rdk: Add MTD name for NOR flash Alexander Shiyan
2013-06-08 17:09 ` [PATCH 1/5] ARM: dts: i.MX27: Add DMA devicetree node Sascha Hauer
2013-06-09  3:07   ` Shawn Guo

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=20130608175754.GM32299@pengutronix.de \
    --to=s.hauer@pengutronix.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).