From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] arm64: dts: qcom: qrb4210-rb2: Add GPIO LEDs
Date: Thu, 18 May 2023 11:41:41 +0200 [thread overview]
Message-ID: <b050f3c4-6ff0-d687-73bf-0f98a2e74bed@linaro.org> (raw)
In-Reply-To: <20230518021307.z63xrx5v2lhd3byf@ripper>
On 18.05.2023 04:13, Bjorn Andersson wrote:
> On Mon, May 15, 2023 at 03:04:14PM +0200, Konrad Dybcio wrote:
>> Add the three LEDs (blue/yellow/green) connected to TLMM GPIOs.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>> ---
>> arch/arm64/boot/dts/qcom/qrb4210-rb2.dts | 36 ++++++++++++++++++++++++++++++--
>> 1 file changed, 34 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qrb4210-rb2.dts b/arch/arm64/boot/dts/qcom/qrb4210-rb2.dts
>> index 9b539720f05d..eeee268ebfe2 100644
>> --- a/arch/arm64/boot/dts/qcom/qrb4210-rb2.dts
>> +++ b/arch/arm64/boot/dts/qcom/qrb4210-rb2.dts
>> @@ -5,6 +5,7 @@
>>
>> /dts-v1/;
>>
>> +#include <dt-bindings/leds/common.h>
>> #include "sm4250.dtsi"
>>
>> / {
>> @@ -30,6 +31,38 @@ hdmi_con: endpoint {
>> };
>> };
>>
>> + leds {
>> + compatible = "gpio-leds";
>> +
>> + led-bt {
>> + label = "blue:bt";
>> + function = LED_FUNCTION_BLUETOOTH;
>> + color = <LED_COLOR_ID_BLUE>;
>> + gpios = <&tlmm 45 GPIO_ACTIVE_HIGH>;
>> + linux,default-trigger = "bluetooth-power";
>> + default-state = "off";
>> + };
>> +
>> + led-user0 {
>> + label = "green:user0";
>> + function = LED_FUNCTION_INDICATOR;
>> + color = <LED_COLOR_ID_GREEN>;
>> + gpios = <&tlmm 52 GPIO_ACTIVE_HIGH>;
>> + linux,default-trigger = "none";
>> + default-state = "off";
>> + panic-indicator;
>> + };
>> +
>> + led-wlan {
>> + label = "yellow:wlan";
>> + function = LED_FUNCTION_WLAN;
>> + color = <LED_COLOR_ID_YELLOW>;
>> + gpios = <&tlmm 47 GPIO_ACTIVE_HIGH>;
>> + linux,default-trigger = "phy0tx";
>> + default-state = "off";
>> + };
>> + };
>> +
>> vreg_hdmi_out_1p2: regulator-hdmi-out-1p2 {
>> compatible = "regulator-fixed";
>> regulator-name = "VREG_HDMI_OUT_1P2";
>> @@ -385,8 +418,7 @@ &sleep_clk {
>> };
>>
>> &tlmm {
>> - gpio-reserved-ranges = <43 2>, <47 1>,
>> - <49 1>, <52 1>, <54 1>,
>> + gpio-reserved-ranges = <43 2>, <49 1>, <54 1>,
>
> How come pin 49 becomes inaccessible here? Was this intended for the
> previous patch?
It doesn't, the "remove" part of the diff is 2-lines.
This reserved-ranges is totally bogus since introduction.. I can send
a separate patch squaring it out.
Konrad
>
> Regards,
> Bjorn
>
>> <56 3>, <61 2>, <64 1>,
>> <68 1>, <72 8>, <96 1>;
>>
>>
>> --
>> 2.40.1
>>
next prev parent reply other threads:[~2023-05-18 9:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 13:04 [PATCH 0/5] QTI RB2 features Konrad Dybcio
2023-05-15 13:04 ` [PATCH 1/5] arm64: dts: qcom: qrb4210-rb2: Describe fixed regulators Konrad Dybcio
2023-05-15 13:04 ` [PATCH 2/5] arm64: dts: qcom: qrb4210-rb2: Enable display out Konrad Dybcio
2023-05-15 15:57 ` Caleb Connolly
2023-05-15 17:00 ` Konrad Dybcio
2023-05-15 19:15 ` Dmitry Baryshkov
2023-05-15 13:04 ` [PATCH 3/5] arm64: dts: qcom: qrb4210-rb2: Add GPIO LEDs Konrad Dybcio
2023-05-18 2:13 ` Bjorn Andersson
2023-05-18 9:41 ` Konrad Dybcio [this message]
2023-05-15 13:04 ` [PATCH 4/5] arm64: dts: qcom: qrb4210-rb2: Enable load setting on SDHCI VQMMC Konrad Dybcio
2023-05-15 13:04 ` [PATCH 5/5] arm64: dts: qcom: qrb4210-rb2: Enable CAN bus controller Konrad Dybcio
2023-05-16 7:48 ` [PATCH 0/5] QTI RB2 features Bhupesh Sharma
2023-05-23 19:40 ` 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=b050f3c4-6ff0-d687-73bf-0f98a2e74bed@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.sharma@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=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robh+dt@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®