public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-clk@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>
Subject: Re: [RFC PATCH 0/4] ARM: dts: renesas: mtd-rom has no clock and power domain
Date: Wed, 1 Oct 2025 15:10:05 +0200	[thread overview]
Message-ID: <aN0oLZekzv8gZETr@shikoro> (raw)
In-Reply-To: <CAMuHMdUjPCO=zVcY-XYWrPMy8sQ0iVM6_H5OETp3Z7sF7-XuYw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 297 bytes --]

Hi Geert,

> Does mtd-rom go through drivers/mtd/maps/physmap-core.c?
> Then the clock domain is handled through Runtime PM since commit
> 0bc448b49e8a017e ("mtd: maps: physmap: Add minimal Runtime PM support").

Thank you, Geert, for the pointers. I will have a try.

Happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2025-10-01 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 10:16 [RFC PATCH 0/4] ARM: dts: renesas: mtd-rom has no clock and power domain Wolfram Sang
2025-09-30 10:16 ` [RFC PATCH 1/4] clk: renesas: mstp: mark 'spibsc' clocks as critical Wolfram Sang
2025-10-01  7:55 ` [RFC PATCH 0/4] ARM: dts: renesas: mtd-rom has no clock and power domain Geert Uytterhoeven
2025-10-01 13:10   ` Wolfram Sang [this message]

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=aN0oLZekzv8gZETr@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.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