public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric Gonçalves" <ghatto404@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.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>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] arm64: dts: qcom: r0q: add gpio keys
Date: Sat, 20 Sep 2025 17:22:28 -0300	[thread overview]
Message-ID: <B58EE981-3702-4FA3-B150-A3C862643870@gmail.com> (raw)
In-Reply-To: <r6e23h4nkddktkle5rohdiiqkw667rq26j7u2yodao6p3scixp@y3roqbly4oje>



On September 20, 2025 5:15:41 PM GMT-03:00, Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> wrote:
>On Sat, Sep 20, 2025 at 03:02:42PM -0300, Eric Gonçalves wrote:
>> 
>> 
>> On September 20, 2025 12:45:27 PM GMT-03:00, Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> wrote:
>> >On Sat, Sep 20, 2025 at 01:46:33AM +0000, Eric Gonçalves wrote:
>> >> Add GPIO keys support to Samsung Galaxy S22 (r0q).
>> >> 
>> >> Signed-off-by: Eric Gonçalves <ghatto404@gmail.com>
>> >> ---
>> >>  .../boot/dts/qcom/sm8450-samsung-r0q.dts      | 53 +++++++++++++++----
>> >>  1 file changed, 44 insertions(+), 9 deletions(-)
>> >> 
>> >> diff --git a/arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts b/arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
>> >> index 880d74ae6032..70e953824996 100644
>> >> --- a/arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
>> >> +++ b/arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
>> >> @@ -2,11 +2,12 @@
>> >>  
>> >>  /dts-v1/;
>> >>  
>> >> +#include <dt-bindings/input/linux-event-codes.h>
>> >>  #include <dt-bindings/regulator/qcom,rpmh-regulator.h>
>> >> -
>> >>  #include "sm8450.dtsi"
>> >>  #include "pm8350.dtsi"
>> >>  #include "pm8350c.dtsi"
>> >> +#include "pmk8350.dtsi"
>> >>  
>> >>  / {
>> >>  	model = "Samsung Galaxy S22 5G";
>> >> @@ -28,13 +29,19 @@ framebuffer: framebuffer@b8000000 {
>> >>  		};
>> >>  	};
>> >>  
>> >> -	vph_pwr: regulator-vph-pwr {
>> >> -		compatible = "regulator-fixed";
>> >> -		regulator-name = "vph_pwr";
>> >> -		regulator-min-microvolt = <3700000>;
>> >> -		regulator-max-microvolt = <3700000>;
>> >> -		regulator-always-on;
>> >> -		regulator-boot-on;
>> >
>> >Please don't mix up refactorings and new features. Split this patch into
>> >several.
>> The patch only added gpio-keys node and pon_resin,
>> pon_pwrkey. Do you mean I have to split each button
>> into separate patches?
>
>No. The patch also moves regulator-vph-pwr and changes the comment in
>the TLMM node.
>
I thought they would be too small to be
patches on their own. Is it okay if I split
them into 2: arm64: dts: qcom: r0q: small refactor
and arm64: dts: qcom: r0q: add gpio keys?
>> >
>> >> +	gpio-keys {
>> >> +		compatible = "gpio-keys";
>> >> +		autorepeat;
>> >> +
>> >> +		pinctrl-0 = <&vol_up_n>;
>> >> +		pinctrl-names = "default";
>> >> +
>> >> +		key-vol-up {
>> >> +			label = "Volume Up";
>> >> +			linux,code = <KEY_VOLUMEUP>;
>> >> +			gpios = <&pm8350_gpios 6 GPIO_ACTIVE_LOW>;
>> >> +			debounce-interval = <15>;
>> >> +		};
>> >>  	};
>> >>  
>> >>  	reserved-memory {
>> >> @@ -47,6 +54,15 @@ splash-region@b8000000 {
>> >>  			no-map;
>> >>  		};
>> >>  	};
>> >> +
>> >> +	vph_pwr: regulator-vph-pwr {
>> >> +		compatible = "regulator-fixed";
>> >> +		regulator-name = "vph_pwr";
>> >> +		regulator-min-microvolt = <3700000>;
>> >> +		regulator-max-microvolt = <3700000>;
>> >> +		regulator-always-on;
>> >> +		regulator-boot-on;
>> >> +	};
>> >>  };
>> >>  
>> >>  &apps_rsc {
>> >> @@ -119,8 +135,27 @@ vreg_l1c_1p8: ldo1 {
>> >>  	};
>> >>  };
>> >>  
>> >> +&pm8350_gpios {
>> >> +	vol_up_n: vol-up-n-state {
>> >> +		pins = "gpio6";
>> >> +		function = "normal";
>> >> +		power-source = <1>;
>> >> +		input-enable;
>> >> +	};
>> >> +};
>> >> +
>> >> +&pon_pwrkey {
>> >> +	status = "okay";
>> >> +};
>> >> +
>> >> +&pon_resin {
>> >> +	linux,code = <KEY_VOLUMEDOWN>;
>> >> +
>> >> +	status = "okay";
>> >> +};
>> >> +
>> >>  &tlmm {
>> >> -	gpio-reserved-ranges = <36 4>; /* SPI (not linked to anything) */
>> >> +	gpio-reserved-ranges = <36 4>; /* SPI (Unused) */
>> >>  };
>> >>  
>> >>  &usb_1 {
>> >> -- 
>> >> 2.51.0
>> >> 
>> >
>> Resend because I forgot to CC the mailing lists
>

  reply	other threads:[~2025-09-20 20:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20  1:46 [PATCH 0/5] arm64: dts: qcom: r0q: enable more peripherals Eric Gonçalves
2025-09-20  1:46 ` [PATCH 1/5] arm64: dts: qcom: r0q: add gpio keys Eric Gonçalves
2025-09-20 15:45   ` Dmitry Baryshkov
2025-09-20 18:02     ` Eric Gonçalves
2025-09-20 20:15       ` Dmitry Baryshkov
2025-09-20 20:22         ` Eric Gonçalves [this message]
2025-09-20 23:21           ` Dmitry Baryshkov
2025-09-20  1:46 ` [PATCH 2/5] arm64: dts: qcom: r0q: add touchscreen support Eric Gonçalves
2025-09-20 15:46   ` Dmitry Baryshkov
2025-09-25 13:08   ` Konrad Dybcio
2025-09-25 21:37     ` Eric Gonçalves
2025-09-20  1:46 ` [PATCH 3/5] arm64: dts: qcom: r0q: enable max77705 PMIC Eric Gonçalves
2025-09-20 15:48   ` Dmitry Baryshkov
2025-09-20 18:04     ` Eric Gonçalves
2025-09-25 13:06   ` Konrad Dybcio
2025-09-26  2:19     ` Eric Gonçalves
2025-10-08  8:34       ` Konrad Dybcio
2025-10-09 20:31         ` Eric Gonçalves
2025-10-20 12:06           ` Konrad Dybcio
2025-09-20  1:46 ` [PATCH 4/5] arm64: dts: qcom: r0q: enable hardware clocks Eric Gonçalves
2025-09-25 13:09   ` Konrad Dybcio
2025-10-05  3:50     ` Eric Gonçalves
2025-10-06 12:31       ` Konrad Dybcio
2025-10-06 15:49         ` Eric Gonçalves
2025-10-08  8:48           ` Konrad Dybcio
2025-10-09 19:20             ` Eric Gonçalves
2025-09-20  1:46 ` [PATCH 5/5] arm64: dts: qcom: r0q: enable ufs storage Eric Gonçalves
2025-09-20 20:16   ` Dmitry Baryshkov
2025-09-25 13:07   ` Konrad Dybcio
2025-09-25 21:37     ` Eric Gonçalves
2025-10-06 12:08       ` Konrad Dybcio
2025-10-06 15:49         ` Eric Gonçalves
2025-09-22 17:27 ` [PATCH 0/5] arm64: dts: qcom: r0q: enable more peripherals Rob Herring (Arm)

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=B58EE981-3702-4FA3-B150-A3C862643870@gmail.com \
    --to=ghatto404@gmail.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --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