All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Adam Skladowski <a39.skl@gmail.com>,
	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>, Kees Cook <kees@kernel.org>,
	Tony Luck <tony.luck@intel.com>,
	"Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH 3/7] arm64: dts: qcom: Add Motorola One
Date: Mon, 17 Aug 2026 17:59:10 +0200	[thread overview]
Message-ID: <db394200-2a29-4f17-a2d9-61d5ab15df60@oss.qualcomm.com> (raw)
In-Reply-To: <20260810-next-patches-v1-3-79a779d76173@gmail.com>

On 8/10/26 6:55 PM, Adam Skladowski wrote:
> Add a devicetree for the Motorola One smartphone, which is based
> on the Jacala/MSM8953 SoC.

[...]

> +&i2c_1 {
> +	status = "disabled";
> +
> +	typec-portc@22 {
> +		compatible = "fcs,fusb302";
> +		reg = <0x22>;
> +		interrupts-extended = <&tlmm 9 IRQ_TYPE_EDGE_RISING>;
> +
> +		status = "disabled";

Why are the bus and this chip disabled?

[...]

> +&tlmm {
> +	gpio-reserved-ranges = <96 4>, <111 1>, <126 1>;

Preferably one a line with a best-effort set of comments describing
what these pins correspond to (see glymur-crd.dtsi)


> +
> +	disp_reset_n_active: disp-reset-n-active-state {
> +		pins = "gpio61";
> +		function = "gpio";
> +		drive-strength = <8>;
> +		bias-disable;
> +		output-high;

Drop output-foo from TLMM pins, the consumer driver should set the output
state via the GPIO APIs

Konrad

  parent reply	other threads:[~2026-08-17 15:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 16:55 [PATCH 0/7] arm64: dts: qcom: Add 3 new devices Adam Skladowski
2026-08-10 16:55 ` [PATCH 1/7] dt-bindings: vendor-prefixes: Add LeEco Adam Skladowski
2026-08-14 10:33   ` Krzysztof Kozlowski
2026-08-10 16:55 ` [PATCH 2/7] dt-bindings: arm: qcom: Document Motorola Moto One Adam Skladowski
2026-08-14 10:33   ` Krzysztof Kozlowski
2026-08-10 16:55 ` [PATCH 3/7] arm64: dts: qcom: Add Motorola One Adam Skladowski
2026-08-10 17:29   ` sashiko-bot
2026-08-11  9:12   ` Dmitry Baryshkov
2026-08-17 15:59   ` Konrad Dybcio [this message]
2026-08-10 16:55 ` [PATCH 4/7] dt-bindings: arm: qcom: Document LeEco Le2 Adam Skladowski
2026-08-14 10:34   ` Krzysztof Kozlowski
2026-08-10 16:55 ` [PATCH 5/7] arm64: dts: qcom: Add " Adam Skladowski
2026-08-10 17:49   ` sashiko-bot
2026-08-11  9:16   ` Dmitry Baryshkov
2026-08-17 15:57   ` Konrad Dybcio
2026-08-10 16:55 ` [PATCH 6/7] dt-bindings: arm: qcom: Document Xiaomi Redmi 9T Adam Skladowski
2026-08-14 10:34   ` Krzysztof Kozlowski
2026-08-10 16:55 ` [PATCH 7/7] arm64: dts: qcom: Add " Adam Skladowski
2026-08-11  9:19   ` Dmitry Baryshkov
2026-08-17 16:08   ` Konrad Dybcio

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=db394200-2a29-4f17-a2d9-61d5ab15df60@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=a39.skl@gmail.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gpiccoli@igalia.com \
    --cc=kees@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tony.luck@intel.com \
    /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.