linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: broonie@kernel.org, devicetree@vger.kernel.org,
	jerry.huang@nxp.com, krzysztof.kozlowski+dt@linaro.org,
	leoyang.li@nxp.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	robh+dt@kernel.org, shawnguo@kernel.org,
	Vladimir Oltean <olteanv@gmail.com>
Subject: Re: [EXT] Re: [PATCH 1/2 v4] dt-bindings: dspi: added for semtech sx1301
Date: Thu, 21 Apr 2022 13:56:53 +0200	[thread overview]
Message-ID: <20ef94a4ae0928deaadb52eccfd6e882@walle.cc> (raw)
In-Reply-To: <663d9e81-9036-6986-f52a-3846b4b5c673@linaro.org>

Am 2022-04-21 13:08, schrieb Krzysztof Kozlowski:
>> But there *could* be a sane default which then could be replaced in
>> an DT overlay. Like "mirkobus-socket" or similar, which might expose
>> spidev. Actually it is more than just SPI, there is GPIO and resets 
>> and
>> I2C. Maybe it should be an MFD? I don't know. But that is something 
>> for
>> the DT maintainers to decide if they'll allow such "generic" devices.
> 
> I think if you have DT overlay, you can add device node and there is no
> need for placeholder, right?

Yes, that is certainly correct. I was thinking of the user
experience. Sometimes you have eval board with that connector
to tinker around with different modules. Therefore I thought it
would be nice to have an userspace spi device by default for
first steps and tinkering.

There is UART which you can use by just opening the tty. There is
I2C which you can use by the i2ctools. There are GPIOs and PWM
which can also be used either by sysfs or the gpio-utils. But there
is no SPI device which can be used by the spi-tools.

But as I said, that is something up to you to decide :)

-michael

  reply	other threads:[~2022-04-21 11:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  7:31 [PATCH 1/2 v4] dt-bindings: dspi: added for semtech sx1301 Changming Huang
2022-04-20  7:31 ` [PATCH 2/2 v4] arm64: dts: fsl-ls1028a: add dspi2 support Changming Huang
2022-04-20 12:06 ` [PATCH 1/2 v4] dt-bindings: dspi: added for semtech sx1301 Krzysztof Kozlowski
2022-04-21  9:11   ` [EXT] " Jerry Huang
2022-04-21  9:18     ` Krzysztof Kozlowski
2022-04-21  9:35       ` Jerry Huang
2022-04-21  9:44       ` Michael Walle
2022-04-21 10:06         ` Jerry Huang
2022-04-21 11:08         ` Krzysztof Kozlowski
2022-04-21 11:56           ` Michael Walle [this message]
2022-04-21 14:23         ` Rob Herring
2022-04-21 15:16           ` Michael Walle
2022-04-21 19:08             ` Rob Herring
2022-04-22  2:19               ` Jerry Huang
2022-04-21 14:27     ` Rob Herring
2022-04-20 13:29 ` Rob Herring
2022-04-21  9:12   ` [EXT] " Jerry Huang

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=20ef94a4ae0928deaadb52eccfd6e882@walle.cc \
    --to=michael@walle.cc \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jerry.huang@nxp.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@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).