public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Johan Jonker <jbx6244@gmail.com>
To: kever.yang@rock-chips.com
Cc: sjg@chromium.org, philipp.tomsich@vrull.eu, lukma@denx.de,
	seanga2@gmail.com, u-boot@lists.denx.de
Subject: [PATCH v8 01/15] rockchip: rk3066-power: sync power domain dt-binding header from Linux
Date: Tue, 18 Jan 2022 01:36:49 +0100	[thread overview]
Message-ID: <20220118003703.10678-2-jbx6244@gmail.com> (raw)
In-Reply-To: <20220118003703.10678-1-jbx6244@gmail.com>

In order to update the DT for rk3066
sync the power domain dt-binding header.
This is the state as of v5.12 in Linux.

Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---
 include/dt-bindings/power/rk3066-power.h | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 include/dt-bindings/power/rk3066-power.h

diff --git a/include/dt-bindings/power/rk3066-power.h b/include/dt-bindings/power/rk3066-power.h
new file mode 100644
index 00000000..acf9f310
--- /dev/null
+++ b/include/dt-bindings/power/rk3066-power.h
@@ -0,0 +1,22 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+#ifndef __DT_BINDINGS_POWER_RK3066_POWER_H__
+#define __DT_BINDINGS_POWER_RK3066_POWER_H__
+
+/* VD_CORE */
+#define RK3066_PD_A9_0		0
+#define RK3066_PD_A9_1		1
+#define RK3066_PD_DBG		4
+#define RK3066_PD_SCU		5
+
+/* VD_LOGIC */
+#define RK3066_PD_VIDEO		6
+#define RK3066_PD_VIO		7
+#define RK3066_PD_GPU		8
+#define RK3066_PD_PERI		9
+#define RK3066_PD_CPU		10
+#define RK3066_PD_ALIVE		11
+
+/* VD_PMU */
+#define RK3066_PD_RTC		12
+
+#endif
-- 
2.20.1


  reply	other threads:[~2022-01-18  0:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  0:36 [PATCH v8 00/15] Add Rikomagic MK808 board Johan Jonker
2022-01-18  0:36 ` Johan Jonker [this message]
2022-01-18  0:36 ` [PATCH v8 02/15] rockchip: rk3066: add grf header file Johan Jonker
2022-01-18  0:36 ` [PATCH v8 03/15] rockchip: rk3066: add clock driver for rk3066 soc Johan Jonker
2022-01-20  0:31   ` Sean Anderson
2022-01-18  0:36 ` [PATCH v8 04/15] rockchip: rk3066: add rk3066 pinctrl driver Johan Jonker
2022-01-18  0:36 ` [PATCH v8 05/15] rockchip: rk3066: add sdram driver Johan Jonker
2022-01-18  0:36 ` [PATCH v8 06/15] arm: dts: rockchip: fix rk3xxx-u-boot.dtsi Johan Jonker
2022-01-18  0:36 ` [PATCH v8 07/15] arm: dts: rockchip: add rk3066a.dtsi Johan Jonker
2022-01-18  0:36 ` [PATCH v8 08/15] arm: dts: rockchip: add rk3066a-mk808.dts Johan Jonker
2022-01-18  0:36 ` [PATCH v8 09/15] rockchip: rk3066: add include Johan Jonker
2022-01-18  0:36 ` [PATCH v8 10/15] rockchip: rk3066: add rk3066_common.h include Johan Jonker
2022-01-18  0:36 ` [PATCH v8 11/15] rockchip: rk3066: add core support Johan Jonker
2022-01-18  0:37 ` [PATCH v8 12/15] rockchip: rk3066: add Rikomagic MK808 board Johan Jonker
2022-01-18  0:37 ` [PATCH v8 13/15] rockchip: rk3066: add mk808_defconfig Johan Jonker
2022-01-18  0:37 ` [PATCH v8 14/15] rockchip: tools: add rk3066 support to rkcommon.c Johan Jonker
2022-01-18  0:37 ` [PATCH v8 15/15] doc: rockchip: add rk3066 Rikomagic MK808 Johan Jonker

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=20220118003703.10678-2-jbx6244@gmail.com \
    --to=jbx6244@gmail.com \
    --cc=kever.yang@rock-chips.com \
    --cc=lukma@denx.de \
    --cc=philipp.tomsich@vrull.eu \
    --cc=seanga2@gmail.com \
    --cc=sjg@chromium.org \
    --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