From: Steev Klimaszewski <steev@kali.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Sven Peter <sven@svenpeter.dev>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-bluetooth@vger.kernel.org,
Mark Pearson <markpearson@lenovo.com>
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: thinkpad-x13s: Add bluetooth
Date: Tue, 31 Jan 2023 21:13:49 -0600 [thread overview]
Message-ID: <20230201031349.56405-1-steev@kali.org> (raw)
In-Reply-To: <c515aae3-88e4-948c-a856-7b45dd2caed9@linaro.org>
>On 31/01/2023 05:38, Steev Klimaszewski wrote:
>> Signed-off-by: Steev Klimaszewski <steev@kali.org>
>> ---
>> .../qcom/sc8280xp-lenovo-thinkpad-x13s.dts | 68 +++++++++++++++++++
>> 1 file changed, 68 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts b/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts
>> index f936b020a71d..951438ac5946 100644
>> --- a/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts
>> +++ b/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts
>> @@ -24,6 +24,8 @@ / {
>> aliases {
>> i2c4 = &i2c4;
>> i2c21 = &i2c21;
>> + serial0 = &uart17;
>> + serial1 = &uart2;
>> };
>>
>> wcd938x: audio-codec {
>> @@ -712,6 +714,32 @@ &qup0 {
>> status = "okay";
>> };
>>
>> +&uart2 {
>> + status = "okay";
>> +
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&uart2_state>;
>> +
>> + bluetooth {
>> + compatible = "qcom,wcn6855-bt";
>> +
>> +/*
> Why dead code should be in the kernel?
As mentioned in the cover letter, this is a bit closer to an RFC than ready to
go in, and I do apologize that it wasn't clear enough. I do not have access to
the schematics, and based on my reading of the schema for bluetooth, these
entries are supposed to be required, however, like the wcn6750, I have dummy
data entered into the qca_soc_data_wcn6855 struct. I know that these should be
there, I just do not have access to the correct information to put, if that
makes sense?
<snip>
>Does not look like you tested the DTS against bindings. Please run `make
>dtbs_check` (see Documentation/devicetree/bindings/writing-schema.rst
>for instructions).
Correct I had not, but I have now, and will make the corrections test and they
will be included in v3.
>Best regards,
>Krzysztof
I appreciate the guidance for what I was doing incorrectly.
-- steev
next prev parent reply other threads:[~2023-02-01 3:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 4:38 [PATCH v2 0/4] Attempt at adding WCN6855 BT support Steev Klimaszewski
2023-01-31 4:38 ` [PATCH v2 1/4] dt-bindings: net: Add WCN6855 Bluetooth Steev Klimaszewski
2023-01-31 18:59 ` Krzysztof Kozlowski
2023-01-31 4:38 ` [PATCH v2 2/4] Bluetooth: hci_qca: Add support for QTI Bluetooth chip wcn6855 Steev Klimaszewski
2023-01-31 19:00 ` Krzysztof Kozlowski
2023-02-01 3:05 ` Steev Klimaszewski
2023-02-01 7:19 ` Krzysztof Kozlowski
2023-01-31 4:38 ` [PATCH v2 3/4] arm64: dts: qcom: sc8280xp: Define uart2 Steev Klimaszewski
2023-01-31 11:15 ` Brian Masney
2023-01-31 4:38 ` [PATCH v2 4/4] arm64: dts: qcom: thinkpad-x13s: Add bluetooth Steev Klimaszewski
2023-01-31 19:01 ` Krzysztof Kozlowski
2023-02-01 3:13 ` Steev Klimaszewski [this message]
2023-02-01 7:18 ` Krzysztof Kozlowski
2023-02-03 20:12 ` Luiz Augusto von Dentz
2023-02-05 21:17 ` Steev Klimaszewski
2023-04-05 4:09 ` [PATCH v2 0/4] Attempt at adding WCN6855 BT support 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=20230201031349.56405-1-steev@kali.org \
--to=steev@kali.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=markpearson@lenovo.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=sven@svenpeter.dev \
/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;
as well as URLs for NNTP newsgroup(s).