public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: ulf.hansson@linaro.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
	arnd@arndb.de, changhuang.liang@starfivetech.com,
	jiajie.ho@starfivetech.com, linux-pm@vger.kernel.org,
	linux-riscv@lists.infradead.org, robh@kernel.org,
	walker.chen@starfivetech.com
Subject: [GIT PULL 2/5] dt-bindings: power: Add power-domain header for JH7110
Date: Wed, 13 Sep 2023 14:54:25 +0100	[thread overview]
Message-ID: <20230913-grumbly-rewrite-34c85539f2ed@spud> (raw)
In-Reply-To: <20230913-bloomers-scorebook-fb45e0a2aa19@spud>

From: Changhuang Liang <changhuang.liang@starfivetech.com>

Add power-domain header for JH7110 SoC, it can use to operate dphy
power.

Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
 include/dt-bindings/power/starfive,jh7110-pmu.h | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/include/dt-bindings/power/starfive,jh7110-pmu.h b/include/dt-bindings/power/starfive,jh7110-pmu.h
index 132bfe401fc8..341e2a0676ba 100644
--- a/include/dt-bindings/power/starfive,jh7110-pmu.h
+++ b/include/dt-bindings/power/starfive,jh7110-pmu.h
@@ -1,6 +1,6 @@
 /* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
 /*
- * Copyright (C) 2022 StarFive Technology Co., Ltd.
+ * Copyright (C) 2022-2023 StarFive Technology Co., Ltd.
  * Author: Walker Chen <walker.chen@starfivetech.com>
  */
 #ifndef __DT_BINDINGS_POWER_JH7110_POWER_H__
@@ -14,4 +14,7 @@
 #define JH7110_PD_ISP		5
 #define JH7110_PD_VENC		6
 
+#define JH7110_PD_DPHY_TX	0
+#define JH7110_PD_DPHY_RX	1
+
 #endif
-- 
2.39.2


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2023-09-13 13:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 13:54 [GIT PULL 0/5] Missed starfive pmdomain changes for v6.6, now for v6.7 Conor Dooley
2023-09-13 13:54 ` [GIT PULL 1/5] pmdomain: starfive: Explicitly include correct DT includes Conor Dooley
2023-09-13 13:54 ` Conor Dooley [this message]
2023-09-26 10:55   ` [GIT PULL 2/5] dt-bindings: power: Add power-domain header for JH7110 Geert Uytterhoeven
2023-09-26 11:20     ` Conor Dooley
2023-09-27  1:31       ` Changhuang Liang
2023-09-27  1:24     ` Changhuang Liang
2023-09-27  7:12       ` Geert Uytterhoeven
2023-09-27 13:26     ` Changhuang Liang
2023-09-13 13:54 ` [GIT PULL 3/5] pmdomain: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE Conor Dooley
2023-09-13 13:54 ` [GIT PULL 4/5] pmdomain: starfive: Extract JH7110 pmu private operations Conor Dooley
2023-09-13 13:54 ` [GIT PULL 5/5] pmdomain: starfive: Add JH7110 AON PMU support Conor Dooley
2023-09-13 22:30 ` [GIT PULL 0/5] Missed starfive pmdomain changes for v6.6, now for v6.7 Ulf Hansson
2023-09-14  6:46   ` Conor Dooley
2023-09-14 13:57   ` Rob Herring
2023-09-14 14:09     ` Ulf Hansson

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=20230913-grumbly-rewrite-34c85539f2ed@spud \
    --to=conor@kernel.org \
    --cc=arnd@arndb.de \
    --cc=changhuang.liang@starfivetech.com \
    --cc=conor.dooley@microchip.com \
    --cc=jiajie.ho@starfivetech.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=walker.chen@starfivetech.com \
    /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