On 4/14/20 12:45 PM, Mark Brown wrote:
On Thu, Apr 09, 2020 at 02:58:27PM -0500, Pierre-Louis Bossart wrote:
Using devm_clk_get() with a NULL string fails on ACPI platforms, use
the "sclk" string as a fallback.
Is this something that could be fixed at the ACPI level?
I guess to fix this we'd need some sort of ACPI-level connection or
description of the clock, and I've never seen such a description?
All the examples I've seen use an explicit 'mclk' string (that's e.g.
what we did for the PMC clocks for Baytrail/Cherrytrail machine drivers,
we added a lookup). Here I used 'sclk' since it's what TI refers to in
their documentation.
I vaguely recall AMD had similar issues with another codec.
