From: Adrian Hunter <adrian.hunter@intel.com>
To: Paul Cercueil <paul.cercueil@bootlin.com>,
Tanmay Kathpalia <tanmay.kathpalia@altera.com>,
Ulf Hansson <ulfh@kernel.org>
Cc: <linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] mmc: sdhci-cadence: enable probing from ACPI
Date: Wed, 4 Nov 2026 18:05:30 +0200 [thread overview]
Message-ID: <d9a9f45c-931f-4799-8c17-3f39bf4dc50d@intel.com> (raw)
In-Reply-To: <21015d0ab9c99bbe8b187792836ecd267e02d4dd.camel@bootlin.com>
On 04/11/2026 16:38, Paul Cercueil wrote:
> Hi Adrian,
>
> Le mercredi 04 novembre 2026 à 16:30 +0200, Adrian Hunter a écrit :
>> On 03/11/2026 11:35, Paul Cercueil wrote:
>>> Use the device property API instead of the OF-specific property API.
>>> This way, the driver will also probe from ACPI.
>>>
>>> Note the change in the core's probe function for SD6HC. We can't have
>>> named clocks in ACPI.
>>
>> Do you mean in the future? ACPI does not provide clocks at all
>> at the moment does it? Otherwise, clocks registered directly by
>> clk_register_clkdev() can have names. Maybe I misunderstand,
>> but perhaps clarify the commit message.
>
> I sent another patch in parallel of this one, that adds basic support for clock
> resources introduced in ACPI 6.5:
>
> https://lore.kernel.org/linux-acpi/20261103084718.8222-1-paul.cercueil@bootlin.com/T/#u
>
Would have been worth mentioning that in a cover letter.
Seems like it gives the clock a name
+ snprintf(name, sizeof(name), "%s-clk%u", dev_name(dev), data->idx++);
+
+ err = devm_clk_hw_register_clkdev(dev, clk, name, dev_name(dev));
but clk_find() doesn't look like it would match then - the comment says:
* An entry with a NULL ID is assumed to be a wildcard.
* If an entry has a device ID, it must match
* If an entry has a connection ID, it must match <------
next prev parent reply other threads:[~2026-11-04 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 9:35 Paul Cercueil
2026-11-04 14:30 ` Adrian Hunter
2026-11-04 14:38 ` Paul Cercueil
2026-11-04 16:05 ` Adrian Hunter [this message]
2026-11-04 16:18 ` 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=d9a9f45c-931f-4799-8c17-3f39bf4dc50d@intel.com \
--to=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=paul.cercueil@bootlin.com \
--cc=tanmay.kathpalia@altera.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=ulfh@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
all inboxes | Powered by JetHome®