linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	devicetree@vger.kernel.org, linux-spi@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v1 1/1] spi: pxa2xx: Move PXA SSP bindings to the correct folder
Date: Fri, 17 May 2024 18:24:37 +0100	[thread overview]
Message-ID: <e81d43f8-a3ba-41b4-a86f-af2d6943e917@sirena.org.uk> (raw)
In-Reply-To: <20240517171103.221856-1-andriy.shevchenko@linux.intel.com>

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

On Fri, May 17, 2024 at 08:11:03PM +0300, Andy Shevchenko wrote:
> SSP stands for Serial Synchronous Protocol and has nothing to do with
> UART, also known as USART, where 'A' stands for Asynchronous.
> 
> Move the SSP bindings to where it belongs.

It's a serial device which is also used for other applications (the
other one upstream being audio) so I can see where the current binding
comes from and it's not super obvious that spi is especially better
here.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-05-17 17:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 17:11 [PATCH v1 1/1] spi: pxa2xx: Move PXA SSP bindings to the correct folder Andy Shevchenko
2024-05-17 17:24 ` Mark Brown [this message]
2024-05-17 19:58   ` Andy Shevchenko
2024-05-17 20:19     ` Rob Herring
2024-05-20 10:47       ` Andy Shevchenko
2024-05-20 20:36         ` Rob Herring
2024-05-21 14:02           ` Andy Shevchenko

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=e81d43f8-a3ba-41b4-a86f-af2d6943e917@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=robh@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 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).