From: Krzysztof Kozlowski <krzk@kernel.org>
To: Riccardo Mereu <r.mereu.kernel@arduino.cc>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, broonie@kernel.org
Cc: linux@roeck-us.net, Jonathan.Cameron@huawei.com,
wenswang@yeah.net, naresh.solanki@9elements.com,
michal.simek@amd.com, nuno.sa@analog.com, chou.cosmo@gmail.com,
grantpeltier93@gmail.com, eajames@linux.ibm.com,
farouk.bouabid@cherry.de, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, mm.facchin@arduino.cc,
Riccardo Mereu <r.mereu@arduino.cc>
Subject: Re: [PATCH 2/5] drivers: spi: spidev: add compatible for arduino spi mcu interface
Date: Fri, 7 Nov 2025 08:13:19 +0100 [thread overview]
Message-ID: <84f0ed2f-bf51-4dd5-93f1-f26e077a2549@kernel.org> (raw)
In-Reply-To: <20251106153119.266840-3-r.mereu@arduino.cc>
On 06/11/2025 16:31, Riccardo Mereu wrote:
> Add compatible entry in spidev describing in Arduino boards one of the
> interfaces between microprocessor and microcontroller.
>
> Signed-off-by: Riccardo Mereu <r.mereu@arduino.cc>
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
It is almost never "drivers" (with one or two exceptions).
> ---
> drivers/spi/spidev.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
> index 5300c942a2a4..f0dd516c2083 100644
> --- a/drivers/spi/spidev.c
> +++ b/drivers/spi/spidev.c
> @@ -704,6 +704,7 @@ static const struct class spidev_class = {
> */
> static const struct spi_device_id spidev_spi_ids[] = {
> { .name = /* abb */ "spi-sensor" },
> + { .name = /* arduino */ "mcu" },
> { .name = /* cisco */ "spi-petra" },
> { .name = /* dh */ "dhcom-board" },
> { .name = /* elgin */ "jg10309-01" },
> @@ -737,6 +738,7 @@ static int spidev_of_check(struct device *dev)
>
> static const struct of_device_id spidev_dt_ids[] = {
> { .compatible = "abb,spi-sensor", .data = &spidev_of_check },
> + { .compatible = "arduino,mcu", .data = &spidev_of_check },
That's way too generic, IMO. First, I am not aware of Arduino boards
mounted on top of regular development boards, so basically you are not
describing actual hardware setup but what could be potentially plugged
into box with Linux... and then it is like saying "you can plug
anything" because MCU covers everything, like calling it "Raspberry
Pi-clone".
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-07 7:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 15:31 [PATCH 0/5] arm64: qcom: add support for Arduino UnoQ SBC Riccardo Mereu
2025-11-06 15:31 ` [PATCH 1/5] dt-binding: trivial-devices: add arduino spi mcu interface Riccardo Mereu
2025-11-07 7:10 ` Krzysztof Kozlowski
2025-11-07 8:09 ` Krzysztof Kozlowski
2025-11-06 15:31 ` [PATCH 2/5] drivers: spi: spidev: add compatible for " Riccardo Mereu
2025-11-07 7:13 ` Krzysztof Kozlowski [this message]
2025-11-11 13:33 ` Riccardo Mereu Linux Kernel
2025-11-11 17:54 ` Conor Dooley
2025-11-06 15:31 ` [PATCH 3/5] dt-binding: arm: qcom: add arduino unoq codename Riccardo Mereu
2025-11-07 7:13 ` Krzysztof Kozlowski
2025-11-11 12:27 ` Dmitry Baryshkov
2025-11-11 16:18 ` Bjorn Andersson
2025-11-12 7:35 ` Krzysztof Kozlowski
2025-11-06 15:31 ` [PATCH 4/5] arm64: dts: qcom: qcm2290: add uart2 node Riccardo Mereu
2025-11-06 16:27 ` Konrad Dybcio
2025-11-11 12:27 ` Dmitry Baryshkov
2025-11-06 15:31 ` [PATCH 5/5] arm64: dts: qcom: unoq: add dts for arduino unoq Riccardo Mereu
2025-11-06 16:29 ` Konrad Dybcio
2025-11-11 12:28 ` Dmitry Baryshkov
2025-11-11 16:14 ` Bjorn Andersson
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=84f0ed2f-bf51-4dd5-93f1-f26e077a2549@kernel.org \
--to=krzk@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=chou.cosmo@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=farouk.bouabid@cherry.de \
--cc=grantpeltier93@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michal.simek@amd.com \
--cc=mm.facchin@arduino.cc \
--cc=naresh.solanki@9elements.com \
--cc=nuno.sa@analog.com \
--cc=r.mereu.kernel@arduino.cc \
--cc=r.mereu@arduino.cc \
--cc=robh@kernel.org \
--cc=wenswang@yeah.net \
/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).