From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mike Turquette <mturquette@linaro.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jin Yao <yao.jin@linux.intel.com>,
Li Aubrey <aubrey.li@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 3/4] clk: new basic clk type for fractional divider
Date: Sat, 17 May 2014 02:15:43 +0200 [thread overview]
Message-ID: <3823442.HzUarSqr07@vostro.rjw.lan> (raw)
In-Reply-To: <20140516230905.9521.88763@quantum>
On Friday, May 16, 2014 04:09:05 PM Mike Turquette wrote:
> Quoting Rafael J. Wysocki (2014-05-16 15:38:05)
> > On Thursday, May 15, 2014 09:53:49 AM Mike Turquette wrote:
> > > Quoting Heikki Krogerus (2014-05-15 06:40:25)
> > > > Fractional divider clocks are fairly common. This adds basic
> > > > type for them.
> > > >
> > > > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > >
> > > Taken into clk-next.
> > >
> > > Just FYI, there was some talk at Embedded Linux Conference on providing
> > > a better abstraction layer for some of these "basic" clock types. This
> > > abstraction would allow the basic clock types to implement the
> > > machine-agnostic logic (e.g. an incoming rate is divided by a value) and
> > > then platforms and drivers could plug in the machine-specific parts
> > > (e.g. divider is made up of m/n, or divider is power-of-two, or divider
> > > is a simple integer with min == 1 and max == 5).
> > >
> > > All of that is to say that in time this fractional divider could go away
> > > once the abstraction layer allows us to fold the m/n divider stuff into
> > > a core divider implementation.
> > >
> > > Nothing wrong with the patch for now, so I've taken it for 3.16.
> >
> > Well, OK, but I guess [4/4] depends on it and [4/4] also depends on
> > [1-2/4], so how you're proposing to resolve this?
>
> I haven't yet published this patch to my tree, so no harm done. How
> about the following Formal Proposals?
>
> 1) I ack the patch and don't merge it through my tree. You take it.
> 2) I provide a topic branch that we both merge.
>
> Your choice.
Thanks! I'd prefer 1) to be honest. :-)
Rafael
next prev parent reply other threads:[~2014-05-16 23:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 13:40 [PATCHv2 0/4] ACPI / LPSS: Solution for two issues seen on Asus T100 Heikki Krogerus
2014-05-15 13:40 ` [PATCHv2 1/4] ACPI / PM: Export rest of the subsys functions Heikki Krogerus
2014-05-15 13:40 ` [PATCHv2 2/4] ACPI / LPSS: custom power domain for LPSS Heikki Krogerus
2014-05-20 21:33 ` Rafael J. Wysocki
2014-05-21 10:05 ` Heikki Krogerus
2014-05-21 11:01 ` Rafael J. Wysocki
2014-05-21 10:52 ` Heikki Krogerus
2014-05-21 23:28 ` Rafael J. Wysocki
2014-05-23 12:30 ` Heikki Krogerus
2014-05-23 13:10 ` Rafael J. Wysocki
2014-05-23 13:02 ` Heikki Krogerus
2014-05-23 13:15 ` [PATCHv3 " Heikki Krogerus
2014-05-26 13:03 ` Rafael J. Wysocki
2014-05-26 13:42 ` Heikki Krogerus
2014-05-26 21:30 ` Rafael J. Wysocki
2014-05-15 13:40 ` [PATCHv2 3/4] clk: new basic clk type for fractional divider Heikki Krogerus
2014-05-15 16:53 ` Mike Turquette
2014-05-16 22:38 ` Rafael J. Wysocki
[not found] ` <20140516230905.9521.88763@quantum>
2014-05-17 0:15 ` Rafael J. Wysocki [this message]
[not found] ` <20140517013403.9521.86191@quantum>
2014-05-19 0:15 ` Rafael J. Wysocki
2014-05-15 13:40 ` [PATCHv2 4/4] ACPI / LPSS: support for fractional divider clock Heikki Krogerus
2014-05-19 11:42 ` [PATCHv3 " Heikki Krogerus
2014-05-15 14:35 ` [PATCHv2 0/4] ACPI / LPSS: Solution for two issues seen on Asus T100 Li, Aubrey
2014-05-15 14:53 ` Andy Shevchenko
2014-05-15 15:59 ` Li, Aubrey
2014-05-15 16:11 ` Mika Westerberg
2014-05-15 23:29 ` Li, Aubrey
2014-05-16 7:04 ` Andy Shevchenko
2014-05-16 13:37 ` Li, Aubrey
2014-05-16 14:45 ` Andy Shevchenko
2014-05-20 11:17 ` Li, Aubrey
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=3823442.HzUarSqr07@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=mturquette@linaro.org \
--cc=yao.jin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®