From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Vikram Sharma <quic_vikramsa@quicinc.com>,
rfoss@kernel.org, todor.too@gmail.com, mchehab@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
akapatra@quicinc.com, hariramp@quicinc.com, andersson@kernel.org,
konradybcio@kernel.org, hverkuil-cisco@xs4all.nl,
cros-qcom-dts-watchers@chromium.org, catalin.marinas@arm.com,
will@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@quicinc.com
Subject: Re: [PATCH v10 4/4] arm64: dts: qcom: qcs6490-rb3gen2-vision-mezzanine: Add vision mezzanine
Date: Fri, 3 Jan 2025 14:48:23 +0000 [thread overview]
Message-ID: <3e3136e5-cb59-45a8-8bd3-43bf401c14cb@linaro.org> (raw)
In-Reply-To: <c7253f5f-eb4a-4636-b0f9-7d284a2f5a8d@linaro.org>
On 19/12/2024 19:32, Vladimir Zapolskiy wrote:
>>>> + rst-pins {
>>>> + pins = "gpio78";
>>>> + function = "gpio";
>>>> + drive-strength = <2>;
>>>> + bias-pull-down;
>>>> + output-low;
>>>> + };
>>>
>>> I have doubts that it's proper to embed a reset gpio into driver's
>>> pinctrl suspend/resume power management.
>>>
>>> Konrad, can you please confirm that it's really accepted?
>>>
>>> I'd rather ask to remove this reset pin control.
>>
>> There's certainly some appearances of this in the tree.
>>
>> You could make the argument that it makes sense to prevent
>> misconfiguration
>> (i.e. the bootloader may set the pin in input mode), but then the counter
>> argument is that the (Linux) gpiod APIs request OUT_LOW/HIGH, and we
>> would
>> expect that the driver uses that if the GPIO is requested through
>> e.g. reset-gpios.
>>
>> I'm not particularly sure what to recommend here. Krzysztof?
>>
>
> I'm worried by a possibility that a device reset/shutdown control GPIO
> could
> be turned off by entering the "sleep" pinctrl setup. If a particular
> GPIO/pin
> is off, is it still continuously functional as a control GPIO of some
> device?
> I believe it is not anymore in general, this is my concern here.
I agree for this particular case that rst-pin should be excised.
- RST is an active low signal, which is typically _pulsed_ for a period
when the sensor is powered to trigger a reset in the state machine of
the sensor
- What is the use-case of pulling RST down the GPIO in suspend ?
I'd remove the output-low though it should make no difference as
the sensor regulators will be off.
- MCLK I think should have a suspend state specified or at least
I can't think of a good reason right now why what I see here is wrong.
For the default state this patch disables the GPIO pull down bias, which
to me seems logical and correct.
TBH I don't have a big concern about the RST pin in reset because the
regulators will be off.
---
bod
prev parent reply other threads:[~2025-01-03 14:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 14:06 [PATCH v10 0/4] media: qcom: camss: Add sc7280 support Vikram Sharma
2024-12-17 14:06 ` [PATCH v10 1/4] media: dt-bindings: update clocks for sc7280-camss Vikram Sharma
2024-12-17 14:10 ` Krzysztof Kozlowski
2024-12-17 16:12 ` Bryan O'Donoghue
2024-12-17 16:23 ` Krzysztof Kozlowski
2024-12-17 16:30 ` Bryan O'Donoghue
2024-12-17 17:43 ` Vikram Sharma
2024-12-18 11:36 ` Dmitry Baryshkov
2024-12-18 12:17 ` Bryan O'Donoghue
2024-12-18 12:18 ` Bryan O'Donoghue
2024-12-17 14:06 ` [PATCH v10 2/4] media: qcom: camss: update clock names for sc7280 Vikram Sharma
2024-12-17 14:11 ` Krzysztof Kozlowski
2024-12-17 14:06 ` [PATCH v10 3/4] arm64: dts: qcom: sc7280: Add support for camss Vikram Sharma
2024-12-19 19:07 ` Konrad Dybcio
2024-12-17 14:06 ` [PATCH v10 4/4] arm64: dts: qcom: qcs6490-rb3gen2-vision-mezzanine: Add vision mezzanine Vikram Sharma
2024-12-17 14:40 ` Vladimir Zapolskiy
2024-12-17 17:49 ` Vikram Sharma
2024-12-19 19:06 ` Konrad Dybcio
2024-12-19 19:32 ` Vladimir Zapolskiy
2025-01-03 14:48 ` Bryan O'Donoghue [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=3e3136e5-cb59-45a8-8bd3-43bf401c14cb@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=akapatra@quicinc.com \
--cc=andersson@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=hariramp@quicinc.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_vikramsa@quicinc.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.org \
--cc=will@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