[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181030161534.wk5cf7nxbwhp2far@picard>
Date: Tue, 30 Oct 2018 16:15:34 +0000
From: Dean Wallace <duffydack73@...il.com>
To: Hans de Goede <hdegoede@...hat.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
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)
On 30-10-18, Hans de Goede wrote:
> 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?
Here's mine, for a coreboot uefi based swanky.
https://ptpb.pw/~swanky-dmi-log
--
Dean
Powered by blists - more mailing lists