From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vishwaroop A <va@nvidia.com>,
robh@kernel.org, jonathanh@nvidia.com, krzk+dt@kernel.org,
conor+dt@kernel.org, thierry.reding@gmail.com,
broonie@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-spi@vger.kernel.org
Subject: Re: [PATCH 3/3] spi: spidev: add "tegra-spidev" name string
Date: Tue, 26 Nov 2024 15:02:23 +0100 [thread overview]
Message-ID: <3d286a32-a76d-493b-88e6-4c652441258b@kernel.org> (raw)
In-Reply-To: <20241126134529.936451-4-va@nvidia.com>
On 26/11/2024 14:45, Vishwaroop A wrote:
> Add "tegra-spidev" name string to load spidev driver
> which allows user-space programs to access and communicate
> with SPI devices connected to the system.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>
> Signed-off-by: Vishwaroop A <va@nvidia.com>
> ---
> drivers/spi/spidev.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
> index 653f82984216..1d2c01bd76a9 100644
> --- a/drivers/spi/spidev.c
> +++ b/drivers/spi/spidev.c
> @@ -711,6 +711,7 @@ static const struct spi_device_id spidev_spi_ids[] = {
> { .name = "spi-authenta" },
> { .name = "em3581" },
> { .name = "si3210" },
> + { .name = "tegra-spidev" },
> {},
> };
> MODULE_DEVICE_TABLE(spi, spidev_spi_ids);
> @@ -741,6 +742,7 @@ static const struct of_device_id spidev_dt_ids[] = {
> { .compatible = "semtech,sx1301", .data = &spidev_of_check },
> { .compatible = "silabs,em3581", .data = &spidev_of_check },
> { .compatible = "silabs,si3210", .data = &spidev_of_check },
> + { .compatible = "nvidia,tegra-spidev", .data = &spidev_of_check },
That's too generic. You need to come with compatibles matching exactly
the device connected.
Above comment applies to all your patches here - DTS and bindings as well.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-11-26 14:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 13:45 [PATCH 0/3] Add spidev nodes for SPI controllers Vishwaroop A
2024-11-26 13:45 ` [PATCH 1/3] arm64: tegra: " Vishwaroop A
2024-11-26 13:45 ` [PATCH 2/3] dt-bindings: spi: Add DT schema for Tegra SPIDEV controller Vishwaroop A
2024-11-26 13:56 ` Mark Brown
2024-11-27 15:54 ` Jon Hunter
2024-11-27 16:09 ` Mark Brown
2024-11-27 17:24 ` Jon Hunter
2024-11-27 17:31 ` Mark Brown
2025-03-25 10:36 ` Jon Hunter
2025-03-25 12:10 ` Mark Brown
2025-03-25 12:45 ` Thierry Reding
2025-03-25 13:05 ` Thierry Reding
2025-03-25 15:55 ` Mark Brown
2025-03-25 16:38 ` Thierry Reding
2025-03-25 17:05 ` Mark Brown
2025-03-26 12:16 ` Jon Hunter
2025-03-27 15:33 ` Mark Brown
2025-03-31 12:34 ` Jon Hunter
2025-03-31 12:44 ` Mark Brown
2025-03-31 13:11 ` Jon Hunter
2025-03-31 14:09 ` Mark Brown
2025-03-25 13:57 ` Mark Brown
2024-11-26 13:45 ` [PATCH 3/3] spi: spidev: add "tegra-spidev" name string Vishwaroop A
2024-11-26 14:02 ` Krzysztof Kozlowski [this message]
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=3d286a32-a76d-493b-88e6-4c652441258b@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=va@nvidia.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