All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Müller" <dave.mueller@gmx.ch>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	"Fujinaka, Todd" <todd.fujinaka@intel.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"e1000-devel@lists.sf.net" <e1000-devel@lists.sf.net>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [E1000-devel] igb driver with Intel Atom Bay Trail issue
Date: Thu, 28 Mar 2019 15:35:58 +0100	[thread overview]
Message-ID: <5dd6a6ac-94de-07ad-df5a-2601cbc7e9d0@gmx.ch> (raw)
In-Reply-To: <20190327191925.GP9224@smile.fi.intel.com>

Hello

Andy Shevchenko wrote:
> On Wed, Mar 27, 2019 at 06:31:19PM +0100, David Müller wrote:
>> The pmc_plt_clks may also be used for external hardware purposes without
>> the need for a driver involved. So I'm afraid a fix similar to the r8169
>> approach will not suit all needs. Please see
>> https://www.spinics.net/lists/linux-clk/msg35800.html for details.
>
> Any driver for device which is using PMC clock should take it into
> consideration.

I agree that each driver should properly request the clocks and other
resources needed.

But what if the PMC clock is used by hardware for which no driver is
being loaded or needed?


Dave

  reply	other threads:[~2019-03-28 14:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1c433bef-055e-2ac3-990c-325aa2d3899e@factor-ts.ru>
     [not found] ` <9B4A1B1917080E46B64F07F2989DADD69AF4DDE7@ORSMSX115.amr.corp.intel.com>
2019-03-27 16:02   ` [E1000-devel] igb driver with Intel Atom Bay Trail issue Hans de Goede
2019-03-27 16:47     ` Andy Shevchenko
2019-03-27 17:31       ` David Müller
2019-03-27 19:19         ` Andy Shevchenko
2019-03-28 14:35           ` David Müller [this message]
2019-03-28 14:58             ` Andy Shevchenko
2019-03-28 15:01               ` Hans de Goede
2019-03-28 15:24                 ` Andy Shevchenko
2019-03-28 15:32                   ` Hans de Goede
2019-03-28 15:49                     ` Andy Shevchenko
2019-03-29  4:46                       ` Hisashi T Fujinaka
2019-03-29 12:32                         ` Hans de Goede
2019-03-29 12:30                       ` Hans de Goede
2019-03-29 13:59                         ` Семен Верченко
2019-03-29 15:53                           ` Hans de Goede
2019-04-04 14:43                             ` Hans de Goede
     [not found]                               ` <20190408172111.GX9224@smile.fi.intel.com>
2019-04-08 18:43                                 ` Hans de Goede
2019-04-09 15:31                                   ` Andy Shevchenko
2019-04-18 13:09                                     ` Hans de Goede
2019-04-18 13:26                                       ` Semyon Verchenko
2019-04-18 15:12                                         ` Hans de Goede
2019-04-22 10:20                                           ` Semyon Verchenko
2019-04-29 15:02                                             ` Hans de Goede
2019-03-28 14:48       ` Hans de Goede

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=5dd6a6ac-94de-07ad-df5a-2601cbc7e9d0@gmx.ch \
    --to=dave.mueller@gmx.ch \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=e1000-devel@lists.sf.net \
    --cc=hdegoede@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=sboyd@kernel.org \
    --cc=todd.fujinaka@intel.com \
    /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.