From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Caleb Connolly <caleb.connolly@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: Bjorn Andersson <quic_bjorande@quicinc.com>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-db845c: make pcie0_3p3v_dual always-on
Date: Wed, 20 Mar 2024 13:29:18 +0100 [thread overview]
Message-ID: <8c815d0d-e716-49fe-9e94-4c5636380360@linaro.org> (raw)
In-Reply-To: <20240320122515.3243711-1-caleb.connolly@linaro.org>
On 3/20/24 13:25, Caleb Connolly wrote:
> This regulator is responsible not just for the PCIe 3.3v rail, but also
> for 5v VBUS on the left USB port. There is currently no way to correctly
> model this dependency on the USB controller, as a result when the PCIe
> driver is not available (for example when in the initramfs) USB is
> non-functional.
>
> Until support is added for modelling this property (likely by
> referencing it as a supply under a usb-connector node), let's just make
> it always on. We don't target any power constrained usecases and this
> regulator is required for USB to function correctly.
>
> Fixes: 3f72e2d3e682 ("arm64: dts: qcom: Add Dragonboard 845c")
> Suggested-by: Bjorn Andersson <quic_bjorande@quicinc.com>
> Signed-off-by: Caleb Connolly <caleb.connolly@linaro.org>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
next prev parent reply other threads:[~2024-03-20 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 12:25 [PATCH] arm64: dts: qcom: sdm845-db845c: make pcie0_3p3v_dual always-on Caleb Connolly
2024-03-20 12:29 ` Konrad Dybcio [this message]
2024-04-21 22:29 ` Bjorn Andersson
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=8c815d0d-e716-49fe-9e94-4c5636380360@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=robh@kernel.org \
--cc=vivek.gautam@codeaurora.org \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.