linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	guptarud@gmail.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	phone-devel@vger.kernel.org,
	"Rudraksha Gupta" <guptarud@gmail.com>,
	"Ondrej Jirman" <megi@xff.cz>,
	"Martijn Braam" <martijn@brixit.nl>,
	"Kamil Trzciński" <ayufan@ayufan.eu>
Subject: Re: [PATCH v5 1/4] arm64: dts: rockchip: Add light/proximity sensor to Pinephone Pro
Date: Mon, 15 Dec 2025 12:36:26 +0100	[thread overview]
Message-ID: <10855349.CDJkKcVGEf@phil> (raw)
In-Reply-To: <20251124-ppp_light_accel_mag_vol-down-v5-1-f9a10a0a50eb@gmail.com>

Hi,

Am Dienstag, 25. November 2025, 04:47:00 Mitteleuropäische Normalzeit schrieb Rudraksha Gupta via B4 Relay:

> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts b/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
> index 6f97e57f36f5..2d2858ee149e 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
> @@ -520,6 +520,16 @@ touchscreen@14 {
>  		touchscreen-size-x = <720>;
>  		touchscreen-size-y = <1440>;
>  	};
> +
> +	light-sensor@48 {
> +		compatible = "sensortek,stk3311";
> +		proximity-near-level = <300>;

proximity-next-... belongs below pinctrl-*


> +		reg = <0x48>;
> +		interrupt-parent = <&gpio4>;
> +		interrupts = <RK_PD3 IRQ_TYPE_EDGE_FALLING>;
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&light_int_l>;
> +	};
>  };
>  
>  &i2c4 {
> @@ -689,6 +699,12 @@ vcc1v8_codec_en: vcc1v8-codec-en {
>  		};
>  	};
>  
> +	stk3311 {

please sort nodes alphabetically
(stk3311 after vcc1v8-codec-en is incorrect)


> +		light_int_l: light-int-l {
> +			rockchip,pins = <4 RK_PD3 RK_FUNC_GPIO &pcfg_input_pull_up>;
> +		};
> +	};
> +
>  	wireless-bluetooth {
>  		bt_wake_pin: bt-wake-pin {
>  			rockchip,pins = <2 RK_PD2 RK_FUNC_GPIO &pcfg_pull_none>;
> 
> 


Heiko





  reply	other threads:[~2025-12-15 11:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25  3:46 [PATCH v5 0/4] Upstreaming Pinephone Pro Patches Rudraksha Gupta via B4 Relay
2025-11-25  3:47 ` [PATCH v5 1/4] arm64: dts: rockchip: Add light/proximity sensor to Pinephone Pro Rudraksha Gupta via B4 Relay
2025-12-15 11:36   ` Heiko Stuebner [this message]
2025-11-25  3:47 ` [PATCH v5 2/4] arm64: dts: rockchip: Add accelerometer " Rudraksha Gupta via B4 Relay
2025-11-25  3:47 ` [PATCH v5 3/4] arm64: dts: rockchip: Add magnetometer " Rudraksha Gupta via B4 Relay
2025-12-15 11:38   ` Heiko Stuebner
2025-11-25  3:47 ` [PATCH v5 4/4] arm64: dts: rockchip: Fix voltage threshold for volume keys for " Rudraksha Gupta via B4 Relay
2025-12-15 11:47 ` (subset) [PATCH v5 0/4] Upstreaming Pinephone Pro Patches Heiko Stuebner

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=10855349.CDJkKcVGEf@phil \
    --to=heiko@sntech.de \
    --cc=ayufan@ayufan.eu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=guptarud@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=martijn@brixit.nl \
    --cc=megi@xff.cz \
    --cc=phone-devel@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;
as well as URLs for NNTP newsgroup(s).