From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] spi: st: Provide Device Tree binding documentation
Date: Thu, 27 Nov 2014 14:55:42 +0000 [thread overview]
Message-ID: <20141127145542.GH4628@x1> (raw)
In-Reply-To: <20141127130053.GW7712@sirena.org.uk>
On Thu, 27 Nov 2014, Mark Brown wrote:
> On Thu, Nov 27, 2014 at 11:43:54AM +0000, Lee Jones wrote:
>
> > +Required properties:
> > +- compatible : "st,comms-ssc-spi" or "st,comms-ssc4-spi"
>
> What do the two different compatible strings mean (for example, should
> ssc4 be used for version 4 and higher or is it just a quirk for that
> version)?
This appears to be historical. There aren't any functional
differences i.e. we don't match on them. I believe the former is a
more informal, generic name and the latter is the official name of the
IP block. The I2C component already upstreamed has the same naming
conventions by the looks of it.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-11-27 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 11:43 [PATCH 0/4] spi: st: New driver for ST's SPI Controller Lee Jones
2014-11-27 11:43 ` [PATCH 1/4] spi: Add new driver for STMicroelectronics' " Lee Jones
2014-11-27 12:33 ` [STLinux Kernel] " Peter Griffin
2014-11-27 12:59 ` Mark Brown
2014-11-27 15:05 ` Lee Jones
2014-11-27 16:24 ` Mark Brown
2014-11-27 13:24 ` Maxime Coquelin
2014-11-27 11:43 ` [PATCH 2/4] spi: st: Provide Device Tree binding documentation Lee Jones
2014-11-27 13:00 ` Mark Brown
2014-11-27 14:55 ` Lee Jones [this message]
2014-11-27 16:30 ` Mark Brown
2014-11-27 11:43 ` [PATCH 3/4] ARM: sti: Provide DT nodes for SSC[0..4] Lee Jones
2014-11-27 11:43 ` [PATCH 4/4] ARM: sti: Provide DT nodes for SBC SSC[0..2] Lee Jones
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=20141127145542.GH4628@x1 \
--to=lee.jones@linaro.org \
--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).