public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: Kever Yang <kever.yang@rock-chips.com>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, linux-amarula@amarulasolutions.com,
	Manoj Sai <abbaraju.manojsai@amarulasolutions.com>,
	Suniel Mahesh <sunil@amarulasolutions.com>
Subject: [PATCH v4 11/12] rockchip: rk3568: Select DM_REGULATOR_FIXED
Date: Fri, 17 Feb 2023 17:28:44 +0530	[thread overview]
Message-ID: <20230217115845.75303-12-jagan@amarulasolutions.com> (raw)
In-Reply-To: <20230217115845.75303-1-jagan@amarulasolutions.com>

From: Manoj Sai <abbaraju.manojsai@amarulasolutions.com>

Select the DM_REGULATOR_FIXED on RK3568 platform.

Co-developed-by: Suniel Mahesh <sunil@amarulasolutions.com>
Signed-off-by: Suniel Mahesh <sunil@amarulasolutions.com>
Signed-off-by: Manoj Sai <abbaraju.manojsai@amarulasolutions.com>
---
 arch/arm/mach-rockchip/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm/mach-rockchip/Kconfig b/arch/arm/mach-rockchip/Kconfig
index 3dc85df65d..6fa8c050cb 100644
--- a/arch/arm/mach-rockchip/Kconfig
+++ b/arch/arm/mach-rockchip/Kconfig
@@ -286,6 +286,7 @@ config ROCKCHIP_RK3568
 	select REGMAP
 	select SYSCON
 	select BOARD_LATE_INIT
+	select DM_REGULATOR_FIXED
 	select DM_RESET
 	imply ROCKCHIP_COMMON_BOARD
 	help
-- 
2.25.1


  parent reply	other threads:[~2023-02-17 12:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 11:58 [PATCH v4 00/12] rockchip: Add Radxa CM3 support Jagan Teki
2023-02-17 11:58 ` [PATCH v4 01/12] rockchip: rk3568: Move DM_RESET in arch kconfig Jagan Teki
2023-02-21  9:28   ` Kever Yang
2023-02-17 11:58 ` [PATCH v4 02/12] dt-bindings: rockchip: Sync rockchip, vop2.h from Linux Jagan Teki
2023-02-17 11:58 ` [PATCH v4 03/12] arm64: dts: rockchip: rk3566: Add Radxa Compute Module 3 Jagan Teki
2023-02-17 11:58 ` [PATCH v4 04/12] arm64: dts: rockchip: rk3566: Add Radxa Compute Module 3 IO Jagan Teki
2023-02-21  9:29   ` Kever Yang
2023-02-17 11:58 ` [PATCH v4 05/12] board: rockchip: Add Radxa Compute Module 3 IO Board Jagan Teki
2023-02-17 11:58 ` [PATCH v4 06/12] phy: rockchip: inno-usb2: Add support #address_cells = 2 Jagan Teki
2023-02-21  9:29   ` Kever Yang
2023-02-17 11:58 ` [PATCH v4 07/12] phy: rockchip-inno-usb2: Add USB2 PHY for rk3568 Jagan Teki
2023-02-21  9:30   ` Kever Yang
2023-02-17 11:58 ` [PATCH v4 08/12] drivers: phy: add naneng combphy " Jagan Teki
2023-02-21  9:31   ` Kever Yang
2023-02-17 11:58 ` [PATCH v4 09/12] arm64: dts: rk356x-u-boot: Drop combphy1 assigned-clocks/rates Jagan Teki
2023-02-21  9:32   ` Kever Yang
2023-02-17 11:58 ` [PATCH v4 10/12] rockchip: rk3568: add rk3568 pinctrl driver Jagan Teki
2023-02-21  9:32   ` Kever Yang
2023-02-17 11:58 ` Jagan Teki [this message]
2023-02-21  9:33   ` [PATCH v4 11/12] rockchip: rk3568: Select DM_REGULATOR_FIXED Kever Yang
2023-02-17 11:58 ` [PATCH v4 12/12] rk3566: radxa-cm3: Enable USB2.0, USB3.0 support Jagan Teki
2023-02-21  9:33   ` Kever Yang

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=20230217115845.75303-12-jagan@amarulasolutions.com \
    --to=jagan@amarulasolutions.com \
    --cc=abbaraju.manojsai@amarulasolutions.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --cc=sunil@amarulasolutions.com \
    --cc=u-boot@lists.denx.de \
    /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