public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Jiri Slaby <jirislaby@kernel.org>, Yao Zi <ziyao@disroot.org>,
	Heiko Stuebner <heiko@sntech.de>, Chukun Pan <amadeus@jmu.edu.cn>,
	linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-serial@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Conor Dooley <conor+dt@kernel.org>,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 4/5] dt-bindings: serial: snps-dw-apb-uart: Allow use of a power-domain
Date: Wed, 23 Jul 2025 08:47:45 -0500	[thread overview]
Message-ID: <175327846490.2145535.759049072094464087.robh@kernel.org> (raw)
In-Reply-To: <20250723085654.2273324-5-jonas@kwiboo.se>


On Wed, 23 Jul 2025 08:56:46 +0000, Jonas Karlman wrote:
> The UART controllers in most Rockchip SoCs are part of power domains
> that are always powered on. 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 UART controllers
> power domain of Rockchip SoCs.
> 
> On Rockchip RK3528 the UART controllers are spread out among the
> described PD_RKVENC, PD_VO and PD_VPU power domains. However, one UART
> controller belong to an undescribed always powered on power domain.
> 
> Add support to describe an optional power-domains for the UART
> controllers.
> 
> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
> ---
> v2: New patch
> ---
>  Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml | 3 +++
>  1 file changed, 3 insertions(+)
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>


  reply	other threads:[~2025-07-23 13:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23  8:56 [PATCH v2 0/5] rockchip: Add power controller support for RK3528 Jonas Karlman
2025-07-23  8:56 ` [PATCH v2 1/5] dt-bindings: gpio: rockchip: Allow use of a power-domain Jonas Karlman
2025-07-23 13:47   ` Rob Herring (Arm)
2025-07-23  8:56 ` [PATCH v2 2/5] dt-bindings: i2c: i2c-rk3x: " Jonas Karlman
2025-07-23 13:47   ` Rob Herring (Arm)
2025-07-23 22:45   ` Andi Shyti
2025-07-23  8:56 ` [PATCH v2 3/5] dt-bindings: iio: adc: rockchip-saradc: " Jonas Karlman
2025-07-23 13:47   ` Rob Herring (Arm)
2025-07-23 15:50   ` Jonathan Cameron
2025-07-23  8:56 ` [PATCH v2 4/5] dt-bindings: serial: snps-dw-apb-uart: " Jonas Karlman
2025-07-23 13:47   ` Rob Herring (Arm) [this message]
2025-07-23  8:56 ` [PATCH v2 5/5] arm64: dts: rockchip: Enable more power domains for RK3528 Jonas Karlman
2025-07-24  9:55 ` (subset) [PATCH v2 0/5] rockchip: Add power controller support " Bartosz Golaszewski

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=175327846490.2145535.759049072094464087.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=amadeus@jmu.edu.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=jirislaby@kernel.org \
    --cc=jonas@kwiboo.se \
    --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=linux-serial@vger.kernel.org \
    --cc=ziyao@disroot.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