From: Aliaksandr Smirnou <support@pinefeat.co.uk>
To: conor@kernel.org
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org, robh@kernel.org,
support@pinefeat.co.uk
Subject: Re: [PATCH v3 1/2] dt-bindings: Pinefeat cef168 lens control board
Date: Mon, 18 Aug 2025 20:29:15 +0100 [thread overview]
Message-ID: <20250818192915.11553-1-support@pinefeat.co.uk> (raw)
In-Reply-To: <20250818-stark-unsocial-96d32a311cab@spud>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=yes, Size: 871 bytes --]
On Mon, 18 Aug 2025 18:36:50 +0100, Conor Dooley wrote:
> Wut? This doesn't make sense, you have supplies so they should be
> documented. The fact that they're shared with a bunch of other things on
> the SBC you're aiming the product at doesn't matter. What if someone
> doesn't use this sensor with an RPi and there is a dedicated regulator?
The supply was introduced in the second patch version but later removed
following feedback from another maintainer. I’m fine with adding it back
if needed - I just want to make sure we’re consistent.
https://lore.kernel.org/all/c1b848b9-b1da-4976-9838-d474394a0992@kernel.org/
Would you prefer it described as before?
> Is that actually your email address?
will change to a named one
> Don't mention drivers in bindings, how linux handles things is not
relevant to a hardware description.
will remove driver mention
next prev parent reply other threads:[~2025-08-18 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 13:05 [PATCH v3 0/2] Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2025-08-17 13:05 ` [PATCH v3 1/2] dt-bindings: Pinefeat cef168 lens control board Aliaksandr Smirnou
2025-08-18 17:36 ` Conor Dooley
2025-08-18 19:29 ` Aliaksandr Smirnou [this message]
2025-08-19 8:21 ` Krzysztof Kozlowski
2025-08-17 13:05 ` [PATCH v3 2/2] media: i2c: Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2025-08-19 13:47 ` Jacopo Mondi
2025-08-19 21:32 ` Aliaksandr Smirnou
2025-08-20 12:56 ` Jacopo Mondi
2025-08-22 17:04 ` Aliaksandr Smirnou
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=20250818192915.11553-1-support@pinefeat.co.uk \
--to=support@pinefeat.co.uk \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@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).