linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Duje Mihanović" <duje@dujemihanovic.xyz>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	David Wronek <david@mainlining.org>,
	Karel Balej <balejk@matfyz.cz>,
	phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH RFC 2/5] dt-bindings: power: Add Marvell PXA1908 domains
Date: Fri, 08 Aug 2025 21:46:58 +0200	[thread overview]
Message-ID: <2017616.PYKUYFuaPT@radijator> (raw)
In-Reply-To: <20250808-portable-expert-turkey-4f8f19@kuoka>

On Friday, 8 August 2025 09:34:54 Central European Summer Time Krzysztof Kozlowski wrote:
> On Wed, Aug 06, 2025 at 07:33:21PM +0200, Duje Mihanović wrote:
> > +          A number of phandles to clocks that need to be enabled during
> > domain +          power up.
> 
> This does not exist in your example, so it is just confusing.

This is because I have not implemented any of the clocks used by the
domains at this moment.

Actually, I am not sure anymore whether it is necessary to assign
clocks to the domains as I have just yesterday successfully brought up
the GPU with some out-of-tree code and that did not require giving the
domains any clocks even though the vendor kernel does this. Should I
just go with that and drop all clock handling from the power domain
driver, at which point there would be no need for the individual domain
nodes? If not, how should I in the future assign clocks to the domains?

> > +examples:
> > +  - |
> > +    #include <dt-bindings/power/marvell,pxa1908-power.h>
> > +
> > +    clock-controller@d4282800 {
> > +      compatible = "marvell,pxa1908-apmu", "simple-mfd", "syscon";
> > +      reg = <0xd4282800 0x400>;
> > +      #clock-cells = <1>;
> > +
> > +      power-controller {
> > +        compatible = "marvell,pxa1908-power-controller";
> 
> No address space, so this should be folded into the parent.

By this, do you mean that the clock driver registers the power domain
controller through devm_mfd_add_devices()?

Regards,
--
Duje




  reply	other threads:[~2025-08-08 19:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 17:33 [PATCH RFC 0/5] Marvell PXA1908 power domains Duje Mihanović
2025-08-06 17:33 ` [PATCH RFC 1/5] dt-bindings: clock: marvell,pxa1908: Add simple-mfd, syscon compatible to apmu Duje Mihanović
2025-08-08  7:35   ` Krzysztof Kozlowski
2025-08-06 17:33 ` [PATCH RFC 2/5] dt-bindings: power: Add Marvell PXA1908 domains Duje Mihanović
2025-08-08  7:34   ` Krzysztof Kozlowski
2025-08-08 19:46     ` Duje Mihanović [this message]
2025-08-11  6:38       ` Krzysztof Kozlowski
2025-08-14 22:08         ` Duje Mihanović
2025-08-15  6:08           ` Krzysztof Kozlowski
2025-08-16 15:13             ` Duje Mihanović
2025-08-17  6:14               ` Krzysztof Kozlowski
2025-08-06 17:33 ` [PATCH RFC 3/5] pmdomain: marvell: Add PXA1908 power domains Duje Mihanović
2025-08-19 10:17   ` Ulf Hansson
2025-08-06 17:33 ` [PATCH RFC 4/5] MAINTAINERS: PXA1908: Add power domain controller Duje Mihanović
2025-08-06 17:33 ` [PATCH RFC 5/5] arm64: dts: marvell: pxa1908: Add power controller Duje Mihanović
2025-08-07 15:40 ` [PATCH RFC 0/5] Marvell PXA1908 power domains Conor Dooley
2025-08-08 19:51   ` Duje Mihanović

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=2017616.PYKUYFuaPT@radijator \
    --to=duje@dujemihanovic.xyz \
    --cc=balejk@matfyz.cz \
    --cc=conor+dt@kernel.org \
    --cc=david@mainlining.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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;
as well as URLs for NNTP newsgroup(s).