mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Cercueil <paul.cercueil@bootlin.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>, Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Paul Cercueil <paul.cercueil@bootlin.com>
Subject: [PATCH v5 0/1] ACPI: platform: ACPI 6.5 fixed clock support
Date: Fri, 20 Nov 2026 17:10:19 +0100	[thread overview]
Message-ID: <20261120161020.297735-1-paul.cercueil@bootlin.com> (raw)

Hi Rafael,

Here's the v5 of my patchset that adds partial support for ACPI 6.5
clock resources.

I don't modify clk_find() anymore. Instead, the first clock is now
registered without a connection name (con_id is NULL) which means that
it can be obtained with clk_get(NULL). Every subsequent ACPI fixed clock
found will have a name, "acpi-clkX".

Each clock is also now registered to the clk core using a system-wide
identifier derived from the ACPI device name.

Changelog since v4:

- Old patch [1/2] "clkdev: Improve clock discovery with clk_find()" is
  gone.

- [1/1] (previously [2/2]):
    Register fixed clock as "<ACPI_ID>-clkX" because we need a
    system-wide identifier there, and we don't have the 16-characters
    limit there.
    Register the first clock to clkdev without a name, so that
    clk_get(NULL) will obtain it.
    Register every other clock for that ACPI device with a "acpi-clkX"
    name.

Cheers,
-Paul

Paul Cercueil (1):
  ACPI: platform: Add basic support for ACPI 6.5 fixed clock resources

 drivers/acpi/acpi_platform.c | 75 ++++++++++++++++++++++++++++++++++++
 1 file changed, 75 insertions(+)

-- 
2.47.3


             reply	other threads:[~2026-11-20 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 16:10 Paul Cercueil [this message]
2026-11-20 16:10 ` [PATCH v5 1/1] ACPI: platform: Add basic support for ACPI 6.5 fixed clock resources Paul Cercueil

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=20261120161020.297735-1-paul.cercueil@bootlin.com \
    --to=paul.cercueil@bootlin.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=thomas.petazzoni@bootlin.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

all inboxes | Powered by JetHome®