From: Conor Dooley <conor@kernel.org>
To: Petar Stoykov <pd.pstoykov@gmail.com>
Cc: linux-iio@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Angel Iglesias <ang.iglesiasg@gmail.com>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: iio: pressure: Add Sensirion SDP500
Date: Wed, 1 May 2024 14:38:47 +0100 [thread overview]
Message-ID: <20240501-glare-cyclist-14ecbafde79d@spud> (raw)
In-Reply-To: <CADFWO8FnMh3OSXO5c9YnafDEf8dxu7MHuH-J32H_Dgx4VSZ=Tw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Wed, May 01, 2024 at 02:06:12PM +0200, Petar Stoykov wrote:
> On Tue, Apr 30, 2024 at 6:50 PM Conor Dooley <conor@kernel.org> wrote:
> > On Tue, Apr 30, 2024 at 05:27:20PM +0200, Petar Stoykov wrote:
> > Other than the fact that a fallback compatible might be required here,
> > this looks like a candidate for trivial-devices.yaml.
>
> This sounds like a more serious comment. We will definitely continue using
> this driver internally for now. But do you think it's still worth adding
> it as a separate driver instead of leaving it for "trivial-devices"?
> It has been a useful driver for us so we thought it is worth sharing.
trivial-devices.yaml is about the binding, not the driver - you still
get to have a dedicated driver.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-05-01 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 15:27 [PATCH v2 1/3] dt-bindings: iio: pressure: Add Sensirion SDP500 Petar Stoykov
2024-04-30 15:37 ` Andy Shevchenko
2024-04-30 16:50 ` Conor Dooley
2024-05-01 12:06 ` Petar Stoykov
2024-05-01 13:38 ` Conor Dooley [this message]
2024-05-05 10:20 ` Jonathan Cameron
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=20240501-glare-cyclist-14ecbafde79d@spud \
--to=conor@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ang.iglesiasg@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pd.pstoykov@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