[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <os7rxycm2tsganlvrffxvkcnkj2dcccsfcfxv6mhesvekeu6wb@ui6msrjmgtai>
Date: Thu, 24 Jul 2025 00:45:07 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Jonas Karlman <jonas@...boo.se>
Cc: Heiko Stuebner <heiko@...ech.de>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Yao Zi <ziyao@...root.org>,
Chukun Pan <amadeus@....edu.cn>, devicetree@...r.kernel.org, linux-rockchip@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org
Subject: Re: [PATCH v2 2/5] dt-bindings: i2c: i2c-rk3x: Allow use of a
power-domain
Hi Jonas,
On Wed, Jul 23, 2025 at 08:56:44AM +0000, Jonas Karlman wrote:
> The I2C controllers in most Rockchip SoCs are part of power domains that
> are always powered on, i.e. PD_BUS or PD_PMU. These always powered
> on power domains have typically not been described in the device tree.
>
> Because these power domains have been left out of the device tree there
> has not been any real need to properly describe the I2C controllers
> power domain.
>
> On RK3528 the I2C controllers are spread out among the described
> PD_RKVENC, PD_VO and PD_VPU power domains. However, one I2C controller
> belong to an undescribed always powered on power domain.
>
> Add support to describe an optional power-domains for the I2C
> controllers in Rockchip SoCs.
>
> Signed-off-by: Jonas Karlman <jonas@...boo.se>
merged to i2c/i2c-host.
Thanks,
Andi
Powered by blists - more mailing lists