From: Johan Hovold <johan@kernel.org>
To: maud_spierings@hotmail.com
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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Stephan Gerhold <stephan.gerhold@linaro.org>
Subject: Re: [PATCH v5 3/3] arm64: dts: qcom: x1e80100-vivobook-s15: Add bluetooth
Date: Tue, 3 Dec 2024 09:52:28 +0100 [thread overview]
Message-ID: <Z07GzL3suEjGlnwF@hovoldconsulting.com> (raw)
In-Reply-To: <20241202-asus_qcom_display-v5-3-e0d3752ff71f@hotmail.com>
On Mon, Dec 02, 2024 at 07:18:13PM +0100, Maud Spierings via B4 Relay wrote:
> From: Maud Spierings <maud_spierings@hotmail.com>
>
> Add bluetooth for the asus vivobook s15
> Describe wlan configuration
I assume you copied most of these (effectively boilerplate) definitions
from somewhere so perhaps you can mention that here (e.g. if it was
copied from Stephan's patches [1]).
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Signed-off-by: Maud Spierings <maud_spierings@hotmail.com>
> ---
> .../boot/dts/qcom/x1e80100-asus-vivobook-s15.dts | 163 +++++++++++++++++++++
> 1 file changed, 163 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts b/arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts
> index 7269f8e7709988657b363004875163a69142f16c..0774bd65ae8cddab81b98e27a116fd5adbe1363c 100644
> --- a/arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts
> +++ b/arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts
> @@ -18,6 +18,11 @@ / {
> compatible = "asus,vivobook-s15", "qcom,x1e80100";
> chassis-type = "laptop";
>
> + aliases {
> + serial0 = &uart21;
No need to add an alias for the console port which is likely not
accessible on this device (without some tinkering).
> + serial1 = &uart14;
> + };
> +
> gpio-keys {
> compatible = "gpio-keys";
> pinctrl-0 = <&hall_int_n_default>;
> + wcn_bt_en: bt-en-state {
Looks like you want a "wcn-" prefix on the node name here too.
> + pins = "gpio116";
> + function = "gpio";
> + drive-strength = <16>;
Is this the drive-strength the firmware uses? The default 2 should be
enough, but you can leave it as-is if it matches the fw settings if you
prefer.
> + output-low;
I don't think you should be setting the pin state already in the pin
configuration as this should be left up to the driver to control.
> + bias-pull-down;
A pull-down should not be needed for this output either.
> + };
> +
> + wcn_sw_en: wcn-sw-en-state {
> + pins = "gpio214";
> + function = "gpio";
> + drive-strength = <16>;
> + bias-disable;
> + };
> +
> + wcn_wlan_en: wlan-en-state {
> + pins = "gpio117";
> + function = "gpio";
> + drive-strength = <16>;
> + bias-disable;
> + };
Same question about the drive strength applies to these two.
> +};
Johan
[1] https://lore.kernel.org/all/20241007-x1e80100-pwrseq-qcp-v1-0-f7166510ab17@linaro.org/
next prev parent reply other threads:[~2024-12-03 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 18:18 [PATCH v5 0/3] Asus vivobook s15 improvements Maud Spierings via B4 Relay
2024-12-02 18:18 ` [PATCH v5 1/3] arm64: dts: qcom: x1e80100-vivobook-s15: Use the samsung,atna33xc20 panel driver Maud Spierings via B4 Relay
2024-12-03 8:38 ` Johan Hovold
2024-12-02 18:18 ` [PATCH v5 2/3] arm64: dts: qcom: x1e80100-vivobook-s15: Add lid switch Maud Spierings via B4 Relay
2024-12-02 18:18 ` [PATCH v5 3/3] arm64: dts: qcom: x1e80100-vivobook-s15: Add bluetooth Maud Spierings via B4 Relay
2024-12-03 8:52 ` Johan Hovold [this message]
2024-12-03 9:06 ` Maud Spierings
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=Z07GzL3suEjGlnwF@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maud_spierings@hotmail.com \
--cc=robh@kernel.org \
--cc=stephan.gerhold@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