From: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [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-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
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
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [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: 38+ 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 ` Lee Jones
2014-11-27 11:43 ` Lee Jones
2014-11-27 11:43 ` [PATCH 1/4] spi: Add new driver for STMicroelectronics' " Lee Jones
2014-11-27 11:43 ` Lee Jones
2014-11-27 12:33 ` [STLinux Kernel] " Peter Griffin
2014-11-27 12:33 ` Peter Griffin
2014-11-27 12:33 ` Peter Griffin
[not found] ` <1417088636-11994-2-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-11-27 12:59 ` Mark Brown
2014-11-27 12:59 ` Mark Brown
2014-11-27 12:59 ` Mark Brown
[not found] ` <20141127125904.GV7712-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-11-27 15:05 ` Lee Jones
2014-11-27 15:05 ` Lee Jones
2014-11-27 15:05 ` Lee Jones
2014-11-27 16:24 ` Mark Brown
2014-11-27 16:24 ` Mark Brown
2014-11-27 16:24 ` Mark Brown
2014-11-27 13:24 ` Maxime Coquelin
2014-11-27 13:24 ` Maxime Coquelin
2014-11-27 13:24 ` Maxime Coquelin
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 11:43 ` Lee Jones
[not found] ` <1417088636-11994-3-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-11-27 13:00 ` Mark Brown
2014-11-27 13:00 ` Mark Brown
2014-11-27 13:00 ` Mark Brown
[not found] ` <20141127130053.GW7712-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-11-27 14:55 ` Lee Jones [this message]
2014-11-27 14:55 ` Lee Jones
2014-11-27 14:55 ` Lee Jones
2014-11-27 16:30 ` Mark Brown
2014-11-27 16:30 ` Mark Brown
2014-11-27 16:30 ` Mark Brown
[not found] ` <1417088636-11994-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-11-27 11:43 ` [PATCH 3/4] ARM: sti: Provide DT nodes for SSC[0..4] Lee Jones
2014-11-27 11:43 ` Lee Jones
2014-11-27 11:43 ` Lee Jones
2014-11-27 11:43 ` [PATCH 4/4] ARM: sti: Provide DT nodes for SBC SSC[0..2] Lee Jones
2014-11-27 11:43 ` Lee Jones
2014-11-27 11:43 ` 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-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.