public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Conor Dooley <conor@kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: <ulf.hansson@linaro.org>,
	Conor Dooley <conor.dooley@microchip.com>, <arnd@arndb.de>,
	<jiajie.ho@starfivetech.com>, <linux-pm@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>, <robh@kernel.org>,
	<walker.chen@starfivetech.com>
Subject: Re: [GIT PULL 2/5] dt-bindings: power: Add power-domain header for JH7110
Date: Wed, 27 Sep 2023 09:31:18 +0800	[thread overview]
Message-ID: <88457ee3-b97a-b350-7f87-20cdc18cb4e9@starfivetech.com> (raw)
In-Reply-To: <20230926-trio-sweat-9b878df53209@spud>



>>>  #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
>>
>> These values are conflicting with similarly-named values above:
>>
>>     #define JH7110_PD_SYSTOP        0
>>     #define JH7110_PD_CPU           1
>>
>> Upon closer look, and diving into the driver, this header file contains
>> definitions for two separate number spaces: the first set is meant
>> to be used in PM Domain specifiers referring to a node compatible
>> with "starfive,jh7110-pmu", while the second set is meant to be
>> used in PM Domain specifiers referring to a node compatible with
>> "starfive,jh7110-aon-syscon".
> 
> Yeah, apologies for the confusion there. I maybe should have
> requested an additional file, since the relevant compatibles
> are different.
> 
>> I think it would be nice to have this reflected in the names of
>> the defines (e.g. JH7110_PD_AON_DPHY_TX), and/or to add comments
>> clearly delimiting the two separate number spaces, and explaining
>> where they apply to.
> 
> Since this is 6.7 material, there's still plenty of time remaining to
> make either of these changes. Changhuang Liang, do you think you would
> be able to send a patch implementing either of the suggestions made by
> Geert?
> 

Hi Conor,

I will send a patch to fix this confusion.

Thanks,
Changhuang

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

  reply	other threads:[~2023-09-27  1:31 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 ` [GIT PULL 2/5] dt-bindings: power: Add power-domain header for JH7110 Conor Dooley
2023-09-26 10:55   ` Geert Uytterhoeven
2023-09-26 11:20     ` Conor Dooley
2023-09-27  1:31       ` Changhuang Liang [this message]
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=88457ee3-b97a-b350-7f87-20cdc18cb4e9@starfivetech.com \
    --to=changhuang.liang@starfivetech.com \
    --cc=arnd@arndb.de \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=geert@linux-m68k.org \
    --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