From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: Add support for X1E80100 Dell Inspirion 14 Plus 7441
Date: Fri, 25 Apr 2025 22:06:07 +0200 [thread overview]
Message-ID: <891c7909-69ef-4d9c-a99c-8d6d08dbfd02@oss.qualcomm.com> (raw)
In-Reply-To: <20250424-qcom-linux-arm64-for-6-16-dell-inspiron14p-v1-2-ace76b31d024@linaro.org>
On 4/24/25 1:53 AM, Bryan O'Donoghue wrote:
> Add support for Dell Inspiron 14p 7441.
>
> Working:
> - WiFi
> - Bluetooth
> - USB Type-C x 2
> - USB Type-A
> - USB Finger Print reader
> - Display
> - NVME
> - Keyboard
> - Touchpad
>
> WIP not included:
> - Audio
> - Camera
> - Embedded Controller
> - Battery
>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> ---
[...]
> + pinctrl-names = "default";
> + pinctrl-0 = <&cam_indicator_en>;
property-n
property-names
file-wide, please
[...]
> + /*
> + * TODO: These two regulators are actually part of the removable M.2
> + * card and not the CRD mainboard. Need to describe this differently.
> + * Functionally it works correctly, because all we need to do is to
> + * turn on the actual 3.3V supply above.
> + */
Well there's definitely no CRD mainboard in there.. not quite, anyway
[...]
> +&i2c5 {
> + clock-frequency = <400000>;
> +
> + status = "okay";
> +
> + /* Type A Port1 */
But there only seems to be one?
[...]
> + /* FRP eUSB */
Factory Reset Protection?
Please spell out Fingerprint scanner if that's what that is
[...]
> +&i2c20 {
> + /* GPIO_80, GPIO_81 */
That can be tracked down by looking up the node definition, it
would be however good to know what sits on this bus and at what
addresses
[...]
> + cam_rgb_default: cam-rgb-default-state {
> + mclk-pins {
> + /* cam_aon_mclk4 */
I don't think this comment adds much
[...]
> +&usb_mp_dwc3 {
> + phys = <&usb_mp_hsphy0>, <&usb_mp_qmpphy0>;
> + phy-names = "usb2-0", "usb3-0";
Any reason to limit these?
looks nice otherwise
Konrad
next prev parent reply other threads:[~2025-04-25 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 23:53 [PATCH 0/3] Add x1e Dell Inpsiron 14p Bryan O'Donoghue
2025-04-23 23:53 ` [PATCH 1/3] dt-bindings: arm: qcom: Add Dell Inspiron 14 Plus 7441 Bryan O'Donoghue
2025-04-28 8:24 ` Krzysztof Kozlowski
2025-04-23 23:53 ` [PATCH 2/3] arm64: dts: qcom: Add support for X1E80100 Dell Inspirion " Bryan O'Donoghue
2025-04-25 20:06 ` Konrad Dybcio [this message]
2025-07-11 19:38 ` Laurentiu Tudor
2025-04-23 23:53 ` [PATCH 3/3] arm64: dts: qcom: x1e80100-dell-inspiron14-7441: Switch on CAMSS RGB sensor Bryan O'Donoghue
2025-04-24 15:42 ` [PATCH 0/3] Add x1e Dell Inpsiron 14p Rob Clark
2025-04-24 15:45 ` Bryan O'Donoghue
2025-07-01 20:43 ` Aleksandrs Vinarskis
2025-07-01 21:48 ` Val Packett
2025-07-01 22:04 ` Aleksandrs Vinarskis
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=891c7909-69ef-4d9c-a99c-8d6d08dbfd02@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.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-kernel@vger.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
all inboxes | Powered by JetHome®