On Mon, Jun 04, 2018 at 01:14:10PM -0500, Pierre-Louis Bossart wrote:
On 06/04/2018 11:27 AM, Mark Brown wrote:
On Mon, Jun 04, 2018 at 08:48:40AM -0500, Pierre-Louis Bossart wrote:
Bottom line there is an 'easy' solution for this specific case and a more complicated one but potentially more generic based on the clock API - hence the RFC.
As far as I can see the two aren't that far off - creating a fixed frequency clock based on DMI data shouldn't be that much harder than doing a set_sysclk().
Not sure how DMI could be used for devices with connectors? The information should come from the additional ASL code that we typically add to SSDT or initrd, e.g. [1]. This ASL code can add additional information clock as needed, e.g. with _DSD properties, but the link with the clock API isn't there atm.
Presumably there's some way you can add IDs for quirking with these? This is the idiomatic way of handling this sort of stuff in ACPI as far as I can tell. Otherwise presumably whatever works for letting you call set_sysclk() would let you set up a clock instead?
It really feels like some of the ACPI users need to step up here and do the work on handling clocks.