From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: "David Müller" <dave.mueller@gmx.ch>
Cc: linux-clk <linux-clk@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH] clk: x86: Add system specific quirk to mark clocks as critical
Date: Thu, 28 Mar 2019 16:05:57 +0200 [thread overview]
Message-ID: <CAHp75VdYKj+TkrciaTF2Puw_uyD-i3TwF35vKcuQAHh5VEMMiQ@mail.gmail.com> (raw)
In-Reply-To: <20190328124939.23139-1-dave.mueller@gmx.ch>
On Thu, Mar 28, 2019 at 2:50 PM David Müller <dave.mueller@gmx.ch> wrote:
>
> Since commit 648e921888ad ("clk: x86: Stop marking clocks as
> CLK_IS_CRITICAL"), the pmc_plt_clocks of the Bay Trail SoC are
> unconditionally gated off. Unfortunately this will break systems
> where these clocks are used for external purposes beyond the kernel's
> knowledge.
> Fix it by implementing a system specific quirk to mark the necessary
> pmc_plt_clks as critical.
>
I didn't see a reply to this:
https://marc.info/?l=linux-clk&m=155371441300575&w=2
I think we can avoid this hack to be returned back.
> Fixes: 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL")
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-03-28 14:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 12:49 [PATCH] clk: x86: Add system specific quirk to mark clocks as critical David Müller
2019-03-28 14:05 ` Andy Shevchenko [this message]
2019-03-28 14:53 ` Hans de Goede
2019-03-28 15:41 ` David Müller
2019-03-28 15:42 ` Hans de Goede
2019-03-28 15:44 ` Andy Shevchenko
2019-04-03 14:08 ` [PATCH v2] " David Müller
2019-04-03 15:30 ` Hans de Goede
2019-04-03 15:36 ` Andy Shevchenko
2019-04-03 15:38 ` Hans de Goede
2019-04-04 8:00 ` David Müller
2019-04-04 8:02 ` Hans de Goede
2019-04-04 8:00 ` David Müller
2019-04-04 14:13 ` [PATCH v3] " David Müller
2019-04-04 14:41 ` Hans de Goede
2019-04-05 15:19 ` Andy Shevchenko
2019-04-05 17:19 ` David Müller
2019-04-08 13:33 ` [PATCH v4] " David Müller
2019-04-08 16:49 ` Andy Shevchenko
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=CAHp75VdYKj+TkrciaTF2Puw_uyD-i3TwF35vKcuQAHh5VEMMiQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dave.mueller@gmx.ch \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.