All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.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 16:30:59 +0000	[thread overview]
Message-ID: <20141127163059.GZ7712@sirena.org.uk> (raw)
In-Reply-To: <20141127145542.GH4628@x1>

[-- Attachment #1: Type: text/plain, Size: 625 bytes --]

On Thu, Nov 27, 2014 at 02:55:42PM +0000, Lee Jones wrote:
> On Thu, 27 Nov 2014, Mark Brown wrote:

> > 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.

Probably best to say something or retire one then.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Lee Jones <lee.jones-QSEj5FYQhm4dnm+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 16:30:59 +0000	[thread overview]
Message-ID: <20141127163059.GZ7712@sirena.org.uk> (raw)
In-Reply-To: <20141127145542.GH4628@x1>

[-- Attachment #1: Type: text/plain, Size: 625 bytes --]

On Thu, Nov 27, 2014 at 02:55:42PM +0000, Lee Jones wrote:
> On Thu, 27 Nov 2014, Mark Brown wrote:

> > 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.

Probably best to say something or retire one then.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] spi: st: Provide Device Tree binding documentation
Date: Thu, 27 Nov 2014 16:30:59 +0000	[thread overview]
Message-ID: <20141127163059.GZ7712@sirena.org.uk> (raw)
In-Reply-To: <20141127145542.GH4628@x1>

On Thu, Nov 27, 2014 at 02:55:42PM +0000, Lee Jones wrote:
> On Thu, 27 Nov 2014, Mark Brown wrote:

> > 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.

Probably best to say something or retire one then.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141127/eb94ebc5/attachment.sig>

  reply	other threads:[~2014-11-27 16:33 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
2014-11-27 12:59   ` Mark Brown
2014-11-27 12:59     ` Mark Brown
2014-11-27 12:59     ` Mark Brown
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
2014-11-27 13:00   ` Mark Brown
2014-11-27 13:00     ` Mark Brown
2014-11-27 13:00     ` Mark Brown
2014-11-27 14:55     ` Lee Jones
2014-11-27 14:55       ` Lee Jones
2014-11-27 14:55       ` Lee Jones
2014-11-27 16:30       ` Mark Brown [this message]
2014-11-27 16:30         ` Mark Brown
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   ` 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=20141127163059.GZ7712@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@stlinux.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.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.