From: Richard Acayan <mailingradian@gmail.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org,
Robert Mader <robert.mader@collabora.com>
Subject: Re: [PATCH v4 1/5] dt-bindings: media: i2c: Add Sony IMX355
Date: Sat, 13 Dec 2025 16:50:07 -0500 [thread overview]
Message-ID: <aT3eUlQuwXptSFGD@rdacayan> (raw)
In-Reply-To: <25c8ad84-2a3f-4e09-a32f-8af68379858e@linaro.org>
On Thu, Dec 11, 2025 at 01:02:49PM +0200, Vladimir Zapolskiy wrote:
> On 12/11/25 03:48, Richard Acayan wrote:
<snip>
> > + reset-gpios:
> > + maxItems: 1
>
> Please explicitly document that the reset GPIO is active low, and make
> the correspondent dts changes.
On my local copy, the DTS already specifies active low, and I haven't
changed it since sending. I'll just change the dt-bindings.
next prev parent reply other threads:[~2025-12-13 21:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 1:48 [PATCH v4 0/5] media: i2c: IMX355 for the Pixel 3a Richard Acayan
2025-12-11 1:48 ` [PATCH v4 1/5] dt-bindings: media: i2c: Add Sony IMX355 Richard Acayan
2025-12-11 3:12 ` Krzysztof Kozlowski
2025-12-11 3:26 ` Rob Herring (Arm)
2025-12-11 5:02 ` Krzysztof Kozlowski
2025-12-12 0:23 ` Richard Acayan
2025-12-11 5:05 ` Krzysztof Kozlowski
2025-12-11 9:35 ` Vladimir Zapolskiy
2025-12-11 11:02 ` Vladimir Zapolskiy
2025-12-13 21:50 ` Richard Acayan [this message]
2025-12-13 21:52 ` Richard Acayan
2025-12-11 1:48 ` [PATCH v4 2/5] media: i2c: imx355: Support devicetree and power management Richard Acayan
2025-12-11 9:37 ` David Heidelberg
2025-12-11 11:00 ` Vladimir Zapolskiy
2025-12-12 1:43 ` Krzysztof Kozlowski
2025-12-12 1:45 ` Krzysztof Kozlowski
2025-12-12 1:49 ` Bryan O'Donoghue
2025-12-11 1:48 ` [PATCH v4 3/5] arm64: dts: qcom: sdm670: remove camss endpoint nodes Richard Acayan
2025-12-11 10:46 ` Vladimir Zapolskiy
2025-12-12 1:39 ` Bryan O'Donoghue
2025-12-11 1:48 ` [PATCH v4 4/5] arm64: dts: qcom: sdm670: add camera mclk pins Richard Acayan
2025-12-11 10:47 ` Vladimir Zapolskiy
2025-12-12 1:40 ` Bryan O'Donoghue
2025-12-13 11:01 ` David Heidelberg
2025-12-11 1:48 ` [PATCH v4 5/5] arm64: dts: qcom: sdm670-google-sargo: add imx355 front camera Richard Acayan
2025-12-11 5:16 ` Dmitry Baryshkov
2025-12-12 0:41 ` Richard Acayan
2025-12-12 1:45 ` Bryan O'Donoghue
2025-12-12 2:19 ` Richard Acayan
2025-12-12 2:20 ` Bryan O'Donoghue
2025-12-12 19:22 ` Dmitry Baryshkov
2025-12-11 10:49 ` Vladimir Zapolskiy
2025-12-12 22:41 ` David Heidelberg
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=aT3eUlQuwXptSFGD@rdacayan \
--to=mailingradian@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robert.mader@collabora.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@intel.com \
--cc=vladimir.zapolskiy@linaro.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).