X86 platform drivers
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Carlo Caione <carlo@endlessm.com>,
	Platform Driver <platform-driver-x86@vger.kernel.org>
Cc: Darren Hart <dvhart@infradead.org>,
	irina.tirdea@intel.com,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	nic_swsd@realtek.com, Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: r8169 broken when enabling the Atom PMC platform clocks
Date: Mon, 10 Jul 2017 17:20:43 +0300	[thread overview]
Message-ID: <1499696443.22624.327.camel@linux.intel.com> (raw)
In-Reply-To: <CAL9uMOGxNGp_dgk+u0n0EngbUOgp9jT8ZpEwk-m4LzAbhYoqzg@mail.gmail.com>

On Mon, 2017-07-10 at 16:15 +0200, Carlo Caione wrote:
> Hi,
> We are working on an Asus Z550M shipping a baytrail processor. From
> the 4.11 kernel we noticed that the system is not bootable anymore
> since it hangs during boot when probing the r8169 driver, not even a
> trace is available.
> 
> We bisected this problem down to commit 282a4e4 ("platform/x86: Enable
> Atom PMC platform clocks").
> 
> We suspected that the problem is that one of the PMC clocks is being
> used by the Ethernet board as XTAL clock and since it is not
> explicitly claimed by the driver, it is gated at boot by the clock
> framework, causing the system to hang.
> 
> We have a quirk downstream in place where we basically modified the
> r8169 driver to claim the 25MHz pmc_plt_clk_4 clock, and this seems to
> work fine, but we really want to find a more upstreamable and
> definitive solution.

Can you copy in-place the hack patch you have?

> The best solution would probably be avoiding to gate the clocks at all
> when booting if these are being already used by the firmware, but IIUC
> this information is not always available in the enable clock register.

Yes, sounds sane.

> Any idea how to approach this issue? I guess in the future we will see
> more platforms needing a quirk like this because of fancy clock
> routings.

As simplest way we might do DMI matching, though I prefer to avoid as
much as possible loading kernel by quirks.

Pierre?

Darren, it seems not the first report regarding this series.
Like a quick fix we perhaps need to revert enabling patch and propagate
to stable. Opinions?

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-07-10 14:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 14:15 r8169 broken when enabling the Atom PMC platform clocks Carlo Caione
2017-07-10 14:20 ` Andy Shevchenko [this message]
2017-07-10 14:23   ` Carlo Caione
2017-07-10 16:06   ` Darren Hart
2017-07-10 17:50     ` Carlo Caione
2017-07-10 18:23       ` Carlo Caione
2017-07-10 18:46         ` 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=1499696443.22624.327.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=carlo@endlessm.com \
    --cc=dvhart@infradead.org \
    --cc=irina.tirdea@intel.com \
    --cc=linux@endlessm.com \
    --cc=nic_swsd@realtek.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=sboyd@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox