From: Michael Walle <michael@walle.cc>
To: Alexandre Mergnat <amergnat@baylibre.com>
Cc: broonie@kernel.org, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-spi@vger.kernel.org, matthias.bgg@gmail.com,
robh+dt@kernel.org
Subject: Re: [PATCH 2/2] spi: spidev: add new mediatek support
Date: Mon, 23 Jan 2023 11:44:30 +0100 [thread overview]
Message-ID: <2aa2ff64cfd3b5ccd1342873fffa6cb4@walle.cc> (raw)
In-Reply-To: <CAFGrd9qXL-u4XzG9MLK2zbKoDudhTYpr-gJaZPjbysJ9Fo2gnQ@mail.gmail.com>
Hi,
Am 2023-01-23 10:37, schrieb Alexandre Mergnat:
> Le ven. 20 janv. 2023 à 09:20, Michael Walle <michael@walle.cc> a écrit
> :
>>
>> From: Alexandre Mergnat <amergnat@baylibre.com>
>>
>> > Add the "mediatek,genio" compatible string to support Mediatek
>> > SPI controller on the genio boards.
>>
>> What is the use case of having the spidev? What if I want to
>> connect a device with a linux driver to it? It seems like you
>> just want to expose the SPI bus on the pin header. There was a
>> similar discussion for a mikrobus connector [1].
>>
> Yes I want to expose the SPI on the pin header for two reasons:
Then "mediatek,genio" doesn't really describe the hardware, does it?
If you read that linked thread, NXP was also trying exposing the SPI
bus on a pin header. IMHO this is just misusing the userspace spi-dev.
That being said, exposing something on a pinheader (or on a standardized
connector) seems like a common thing and we should be working towards
a good solution. I still think Robs proposal for the mikrobus connector
makes also sense for your case.
-michael
next prev parent reply other threads:[~2023-01-23 10:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 16:28 [PATCH 0/2] Add MediaTek MT8365 SPI support Alexandre Mergnat
2023-01-19 16:28 ` [PATCH 1/2] arm64: dts: mediatek: add spidev support for mt8365-evk board Alexandre Mergnat
2023-01-19 16:28 ` [PATCH 2/2] spi: spidev: add new mediatek support Alexandre Mergnat
2023-01-19 16:39 ` Mark Brown
2023-01-19 16:40 ` Matthias Brugger
2023-01-19 16:49 ` Krzysztof Kozlowski
2023-01-19 19:18 ` Alexandre Mergnat
2023-01-20 7:44 ` Krzysztof Kozlowski
2023-01-20 7:58 ` Krzysztof Kozlowski
2023-01-20 7:47 ` Krzysztof Kozlowski
2023-01-23 10:06 ` Alexandre Mergnat
2023-01-23 15:55 ` Krzysztof Kozlowski
2023-01-20 8:20 ` Michael Walle
2023-01-23 9:37 ` Alexandre Mergnat
2023-01-23 10:44 ` Michael Walle [this message]
2023-01-23 14:57 ` Alexandre Mergnat
2023-01-23 12:19 ` Mark Brown
2023-01-23 15:07 ` Alexandre Mergnat
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=2aa2ff64cfd3b5ccd1342873fffa6cb4@walle.cc \
--to=michael@walle.cc \
--cc=amergnat@baylibre.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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).