[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e48696f0-aa3e-e20e-d038-9d8dda9cbfce@redhat.com>
Date: Tue, 30 Oct 2018 17:04:22 +0100
From: Hans de Goede <hdegoede@...hat.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Dean Wallace <duffydack73@...il.com>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
Stephen Boyd <sboyd@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
linux-clk <linux-clk@...r.kernel.org>,
Stable <stable@...r.kernel.org>,
Johannes Stezenbach <js@...21.net>,
Carlo Caione <carlo@...lessm.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mogens Jensen <mogens-jensen@...tonmail.com>
Subject: Re: Regression found (Stop-marking-clocks-as-CLK_IS_CRITICAL)
Hi,
On 30-10-18 16:46, Hans de Goede wrote:
> Hi,
>
> On 30-10-18 16:04, Pierre-Louis Bossart wrote:
>> In addition I am not aware of any baytrail device using plt_clk_0, so moving a common machine driver such a cht_bsw_max98090_ti to use plt_clk0 only would break other devices (e.g. Rambi/Orco). Asking for both clocks to be on might work though,
>
> Ok, so we need to have a DMI based quirk for the Swanky and maybe also
> the clapper to use plt_clk_0 there. Asking for 2 clks if we only need
> one does not seem like a good plan.
Dean, Mogens,
To write a proper patch for this I'm going to need DMI strings
from your devices.
Can you please run (as normal user):
grep . /sys/class/dmi/id/* 2> /dev/null
And reply with the output of this command?
Thanks,
Hans
Powered by blists - more mailing lists