mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: "Szőke Benjamin" <egyszeregy@freemail.hu>
Cc: Mark Brown <broonie@kernel.org>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] spidev: Introduce "linux,spidev-name" property for device tree of spidev.
Date: Fri, 7 Jun 2024 17:07:23 +0100	[thread overview]
Message-ID: <20240607-upcoming-tidiness-401e5d0a8af0@spud> (raw)
In-Reply-To: <30944fda-6d18-4fc1-8c73-bcda4814a417@freemail.hu>

[-- Attachment #1: Type: text/plain, Size: 748 bytes --]

On Sun, Jun 02, 2024 at 05:31:10PM +0200, Szőke Benjamin wrote:

>     spidev@0 {
>         reg = <0>;
>         compatible = "rohm,dh2228fv";
>         spi-max-frequency = <1000000>;
> 
>         // via my kernel patch -> /dev/spidev-mysensor
>         // linux,spidev-name = "mysensor";

Given you are describing a DAC as a "sensor", I doubt you actually even
have a dh2228fv*. You're looking to have a consistent name here, but you
can't even rely on Linux even continuing to bind the spidev driver
against this compatible if somebody comes along and writes an IIO driver
for this DAC!

That said, google seems to return no results for a dh2228fv, only for a
bh2228fv. Makes me wonder if this device actually even exists...


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2024-06-07 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-19 21:13 egyszeregy
2024-05-20 13:20 ` Mark Brown
2024-05-20 17:20   ` Szőke Benjamin
2024-05-20 20:14     ` Mark Brown
2024-06-02 15:31       ` Szőke Benjamin
2024-06-07 15:55         ` Mark Brown
2024-06-07 16:07         ` Conor Dooley [this message]
2024-06-11 10:41           ` Andy Shevchenko

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=20240607-upcoming-tidiness-401e5d0a8af0@spud \
    --to=conor@kernel.org \
    --cc=broonie@kernel.org \
    --cc=egyszeregy@freemail.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.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

all inboxes | Powered by JetHome®