Linux SPI subsystem development
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Mark Brown <broonie@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Yang Yingliang <yangyingliang@huawei.com>,
	linux-spi@vger.kernel.org
Subject: Re: [PATCH -next 1/2] spi: introduce devm_spi_alloc_controller()
Date: Wed, 28 Sep 2022 17:11:16 +0200	[thread overview]
Message-ID: <20220928151116.GA13418@wunner.de> (raw)
In-Reply-To: <YzQsw8hiMTxdqZuu@sirena.org.uk>

On Wed, Sep 28, 2022 at 12:15:15PM +0100, Mark Brown wrote:
> On Tue, Sep 27, 2022 at 10:43:08PM +0200, Geert Uytterhoeven wrote:
> > On Tue, Sep 27, 2022 at 10:24 PM Mark Brown <broonie@kernel.org> wrote:
> 
> > > Sure, but since the current wrappers use the legacy names this means
> > > that we need new wrappers with more modern names hence there is
> > > something to improve here.
> 
> > So what are the more modern names?
> 
> It's unfortunately not 100% clear, and our use of controller for the
> generic thing gets in the way a bit.  There was some stuff from one of
> the open source hardware groups recently that tried to propose new names
> but I'm not immediately finding it.  "host" and "target" would probably
> do the trick?

Perhaps you mean that one?

https://www.oshwa.org/a-resolution-to-redefine-spi-signal-names/

Looks like they're replacing master with controller and
slave with peripheral.  Pity, we're using controller as
an umbrella term for either one of them.

Renaming that will lead to an awful lot of churn. :(

Thanks,

Lukas

  parent reply	other threads:[~2022-09-28 15:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 14:29 [PATCH -next 1/2] spi: introduce devm_spi_alloc_controller() Yang Yingliang
2022-09-26 14:29 ` [PATCH -next 2/2] spi: xilinx: switch to use spi_controller_*() functions Yang Yingliang
2022-09-27  3:45 ` [PATCH -next 1/2] spi: introduce devm_spi_alloc_controller() Lukas Wunner
2022-09-27  7:11   ` Geert Uytterhoeven
2022-09-27 11:21   ` Mark Brown
2022-09-27 11:57     ` Yang Yingliang
2022-09-27 13:31       ` Lukas Wunner
2022-09-27 17:01         ` Mark Brown
2022-09-27 20:19           ` Lukas Wunner
2022-09-27 20:22             ` Mark Brown
2022-09-27 20:43               ` Geert Uytterhoeven
2022-09-28 11:15                 ` Mark Brown
2022-09-28 15:01                   ` Yang Yingliang
2022-09-28 16:08                     ` Mark Brown
2022-09-28 15:11                   ` Lukas Wunner [this message]
2022-09-28 15:58                     ` Mark Brown
2022-09-28 17:14                     ` Geert Uytterhoeven
2022-09-28  6:34               ` Yang Yingliang
2022-09-28 11:10                 ` Mark Brown

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=20220928151116.GA13418@wunner.de \
    --to=lukas@wunner.de \
    --cc=broonie@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=yangyingliang@huawei.com \
    /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