ARM Sunxi Platform Development
 help / color / mirror / Atom feed
From: "Kryštof Černý" <cleverline1mc@gmail.com>
To: wens@csie.org
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH PATCH] arm64: dts: sunxi: nanopi-neo-plus2: Add pio regulators
Date: Sat, 24 Aug 2024 16:24:41 +0200	[thread overview]
Message-ID: <aa33692c-4cae-4c41-959d-f2ecd56334b7@gmail.com> (raw)
In-Reply-To: <CAGb2v65M6Zz7=TfRwF0urbELNaaazMZYsd3dtHYzwdJvzoho3A@mail.gmail.com>

Yes, you are right with vcc-pd, I misunderstood it, thank you. Let me 
explain and ask about the rest:
VDD_SYS_3.3V = reg_vcc3v3
Groups PA, PE, PF are powered from vcc-io, according to Allwinner H5 
datasheet, Vcc-io is connected to VDD_SYS_3.3V, just like mmc0. Should 
those be set or omitted?
vcc-pc (ball G15), which is labeled as vcc_io2 (probably wrong), which 
is also connected to VDD_SYS_3.3V.
vcc-pd (ball J15) is bonded to VDD_PHY_2.5V, which is always on and made 
from VDD_SYS_3.3V, so I should make a new fixed regulator of name 
"reg_gmac_2v5"? Mainline eth driver does not implement this pin, so it 
would be used only for the pio.
vcc-pg (ball H7) is also VDD_SYS_3.3V.
While PL is supplied from vcc-rtc (vcc_rtc, ball K6), it is connected 
directly to the VDD_SYS_3.3V too, should this be the same regulator or a 
new one or omitted too?
Do you agree with my findings? I hope they are 100% now. If so, I will 
try to make V2 with a new fixed regulator of 2.5V for the PD.

Many thanks for your replies, I will do better next time.

Dne 24. 08. 24 v 14:34 Chen-Yu Tsai napsal(a):
> Hi,
>
> On Sat, Aug 24, 2024 at 5:08 PM Kryštof Černý <cleverline1mc@gmail.com> wrote:
>> I am sorry if the message is wrong, this is my first patch ever sent to
>> the Linux kernel. I have checked the schematic of the board and it
>> shares the same power line with mmc0, so I assumed I can use the same
>> regulator. Thanks for your feedback and I would be glad for your further
>> response.
> So some of the pin groups do have dedicated supplies, and should thus be
> described, but not all of them. The schematic only shows dedicated
> supplies for PD and PG pingroups. So just add those. PD supply is from
> 2.5V ethernet PHY I/O regulator supply, so you would need to add that
> as well.
>
> The datasheet also mentions a separate supply pin for PC pingroup, but
> it is not shown in the schematic. I would just omit that.
>
> And as Krzysztof mentioned, device tree changes should be to model
> the hardware, not to work around some operating system warning. At
> least most of the time that is. So your commit message should also
> be about fixing the description or providing more detail, and not
> about the operating system.
>
>
> ChenYu
>
>> Dne 24. 08. 24 v 9:40 Krzysztof Kozlowski napsal(a):
>>> On 24/08/2024 09:09, Kryštof Černý wrote:
>>>> The board does not have a dedicated regulator for pio and r_pio,
>>>> but this fixes the kernel warning about dummy regulators being used.
>>>> Tested on the actual board.
>>>>
>>> Judging by commit msg these are not correct regulators. Please do not
>>> add incorrect hardware description to silence some warnings coming from
>>> OS. Either you need proper (correct) hardware description or fix the
>>> problem other way, assuming there is anything to fix in the first place.
>>>
>>> Best regards,
>>> Krzysztof
>>>

  reply	other threads:[~2024-08-24 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-24  7:09 [PATCH PATCH] arm64: dts: sunxi: nanopi-neo-plus2: Add pio regulators Kryštof Černý
2024-08-24  7:40 ` Krzysztof Kozlowski
2024-08-24  9:08   ` Kryštof Černý
2024-08-24 12:34     ` Chen-Yu Tsai
2024-08-24 14:24       ` Kryštof Černý [this message]
2024-08-26 22:44         ` Andre Przywara

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=aa33692c-4cae-4c41-959d-f2ecd56334b7@gmail.com \
    --to=cleverline1mc@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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