From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: imx6q: add Novena board
Date: Wed, 18 Nov 2015 12:36:16 +0100 [thread overview]
Message-ID: <1447846576.3144.63.camel@pengutronix.de> (raw)
In-Reply-To: <201511181232.42446.marex@denx.de>
Am Mittwoch, den 18.11.2015, 12:32 +0100 schrieb Marek Vasut:
> On Wednesday, November 18, 2015 at 12:25:58 PM, Lucas Stach wrote:
> > Am Mittwoch, den 18.11.2015, 11:35 +0100 schrieb Marek Vasut:
> > > On Wednesday, November 18, 2015 at 11:10:12 AM, Lucas Stach wrote:
> > > > Hi Marek,
[...]
> > > [...]
> > >
> > > > > +&ecspi3 {
> > > > > + pinctrl-names = "default";
> > > > > + pinctrl-0 = <&pinctrl_ecspi3_novena>;
> > > > > + fsl,spi-num-chipselects = <3>;
> > > > > + status = "okay";
> > > > > +
> > > > > + spidev at 0 {
> > > > > + compatible = "spidev";
> > > >
> > > > This will explode on a new kernel. Specifying spidev without using a
> > > > more specific compatible will trigger a WARN_ON(), as it's considered
> > > > bad style.
> > >
> > > Oh, looks like imx_v6_v7_defconfig didn't have SPIDEV active, which is
> > > why I didn't catch it during my last test, dang.
> > >
> > > This SPI interface is routed into the FPGA, so what do you suggest I put
> > > in the compatible string? There is no other sensible driver for the
> > > peripheral, since the peripheral can be anything.
> >
> > I'm not really the right person to ask for that, but I would guess that
> > inventing a "novena,fpga-spi" compatible or something like that and
> > adding it to the spidev driver would be the right thing to do.
>
> So what's the rationale behind generic "spidev" being bad ? In my mind, it
> is much better to use generic driver and generic compatible prop "spidev"
> than to generate many one-off compatible props and have a driver with a list
> of all of those.
>
>From the commit log:
"Since spidev is a detail of how Linux controls a device rather than a
description of the hardware in the system we should never have a node
described as "spidev" in DT, any SPI device could be a spidev so this is
just not a useful description."
If you want to know about the details you would have to discuss this
with Mark Brown.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2015-11-18 11:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 9:48 [PATCH 1/2] devicetree: bindings: Add vendor prefix for Kosagi Marek Vasut
2015-11-18 9:48 ` [PATCH 2/2] ARM: dts: imx6q: add Novena board Marek Vasut
2015-11-18 10:10 ` Lucas Stach
2015-11-18 10:35 ` Marek Vasut
2015-11-18 11:25 ` Lucas Stach
2015-11-18 11:32 ` Marek Vasut
2015-11-18 11:36 ` Lucas Stach [this message]
2015-11-19 16:03 ` Marek Vasut
2015-11-18 12:14 ` Fabio Estevam
2015-11-18 12:00 ` Fabio Estevam
2015-11-19 16:11 ` Marek Vasut
2015-11-20 2:49 ` Sean Cross
2015-11-20 9:07 ` Marek Vasut
2015-11-20 20:46 ` [PATCH V2 " Marek Vasut
2015-11-20 20:58 ` Fabio Estevam
2015-11-20 21:05 ` Marek Vasut
2015-11-23 9:15 ` Lucas Stach
2015-11-24 11:04 ` Marek Vasut
2015-11-20 21:19 ` [PATCH 1/2] devicetree: bindings: Add vendor prefix for Kosagi Arnd Bergmann
2015-11-20 22:30 ` Marek Vasut
2015-11-20 22:46 ` Arnd Bergmann
2015-11-21 0:08 ` Marek Vasut
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=1447846576.3144.63.camel@pengutronix.de \
--to=l.stach@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).