From: Scott Wood <scottwood@freescale.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: Tang Yuantian <Yuantian.Tang@freescale.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Liberman Igal-B31950 <Igal.Liberman@freescale.com>,
Bucur Madalin-Cristian-B32716 <madalin.bucur@freescale.com>,
<linux-clk@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver
Date: Thu, 1 Oct 2015 19:26:29 -0500 [thread overview]
Message-ID: <1443745589.5336.185.camel@freescale.com> (raw)
In-Reply-To: <20150811182535.31346.52965@quantum>
[Resending to updated e-mail address]
On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote:
> Hi Scott,
>
> Quoting Scott Wood (2015-06-18 19:49:10)
> > The existing device tree bindings are error-prone and inflexible.
> > Correct the mistake by moving the knowledge into the driver, which
> > has more flexibility in describing the quirks of each chip. This leaves
> > the device tree to its proper role of identifying a programming interface
> > rather than describing its individual registers.
>
> Sorry for not responding to this one sooner. Fell through the cracks.
>
> All of the changes to drives/clk/clk-qoriq.c look great to me. I assume
> you need to keep all of these patches together and want to the take
> through the freescale tree? If so feel free to add,
>
> Acked-by: Michael Turquette <mturquette@baylibre.com>
Is the ack still valid for the v3 patchset?
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: devicetree@vger.kernel.org,
Liberman Igal-B31950 <Igal.Liberman@freescale.com>,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Tang Yuantian <Yuantian.Tang@freescale.com>,
linuxppc-dev@lists.ozlabs.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Bucur Madalin-Cristian-B32716 <madalin.bucur@freescale.com>
Subject: Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver
Date: Thu, 1 Oct 2015 19:26:29 -0500 [thread overview]
Message-ID: <1443745589.5336.185.camel@freescale.com> (raw)
In-Reply-To: <20150811182535.31346.52965@quantum>
[Resending to updated e-mail address]
On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote:
> Hi Scott,
>
> Quoting Scott Wood (2015-06-18 19:49:10)
> > The existing device tree bindings are error-prone and inflexible.
> > Correct the mistake by moving the knowledge into the driver, which
> > has more flexibility in describing the quirks of each chip. This leaves
> > the device tree to its proper role of identifying a programming interface
> > rather than describing its individual registers.
>
> Sorry for not responding to this one sooner. Fell through the cracks.
>
> All of the changes to drives/clk/clk-qoriq.c look great to me. I assume
> you need to keep all of these patches together and want to the take
> through the freescale tree? If so feel free to add,
>
> Acked-by: Michael Turquette <mturquette@baylibre.com>
Is the ack still valid for the v3 patchset?
-Scott
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
WARNING: multiple messages have this Message-ID (diff)
From: scottwood@freescale.com (Scott Wood)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver
Date: Thu, 1 Oct 2015 19:26:29 -0500 [thread overview]
Message-ID: <1443745589.5336.185.camel@freescale.com> (raw)
In-Reply-To: <20150811182535.31346.52965@quantum>
[Resending to updated e-mail address]
On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote:
> Hi Scott,
>
> Quoting Scott Wood (2015-06-18 19:49:10)
> > The existing device tree bindings are error-prone and inflexible.
> > Correct the mistake by moving the knowledge into the driver, which
> > has more flexibility in describing the quirks of each chip. This leaves
> > the device tree to its proper role of identifying a programming interface
> > rather than describing its individual registers.
>
> Sorry for not responding to this one sooner. Fell through the cracks.
>
> All of the changes to drives/clk/clk-qoriq.c look great to me. I assume
> you need to keep all of these patches together and want to the take
> through the freescale tree? If so feel free to add,
>
> Acked-by: Michael Turquette <mturquette@baylibre.com>
Is the ack still valid for the v3 patchset?
-Scott
next prev parent reply other threads:[~2015-10-02 0:26 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 2:49 [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` [RFC PATCH 1/8] ARM: dts: ls1021a: Fix clockgen node Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` [RFC PATCH 2/8] cpufreq: qoriq: Don't look at clock implementation details Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` [RFC PATCH 3/8] powerpc/fsl: Move fsl_guts.h out of arch/powerpc Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` [RFC PATCH 4/8] clk: qoriq: Move chip-specific knowledge into driver Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` [RFC PATCH 5/8] clk: qoriq: Redirect legacy clock nodes to new clocks Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` [RFC PATCH 6/8] cpufreq: qoriq: Remove frequency masking and minimum Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` [RFC PATCH 7/8] clk: qoriq: Expose OF clocks directly from the clockgen node Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` [RFC PATCH 8/8] powerpc/fsl: Use new clockgen binding Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-06-19 2:49 ` Scott Wood
2015-07-30 15:32 ` Liberman Igal
2015-07-30 15:32 ` Liberman Igal
2015-07-30 15:32 ` Liberman Igal
2015-07-30 15:32 ` Liberman Igal
2015-08-11 18:25 ` [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver Michael Turquette
2015-08-11 18:25 ` Michael Turquette
2015-08-11 18:25 ` Michael Turquette
2015-08-11 18:25 ` Michael Turquette
2015-08-15 6:43 ` Scott Wood
2015-08-15 6:43 ` Scott Wood
2015-08-15 6:43 ` Scott Wood
2015-10-02 0:23 ` Scott Wood
2015-10-02 0:23 ` Scott Wood
2015-10-02 0:23 ` Scott Wood
2015-10-02 0:26 ` Scott Wood [this message]
2015-10-02 0:26 ` Scott Wood
2015-10-02 0:26 ` Scott Wood
2015-10-09 23:57 ` Scott Wood
2015-10-09 23:57 ` Scott Wood
2015-10-09 23:57 ` Scott Wood
2015-10-22 10:11 ` Michael Turquette
2015-10-22 10:11 ` Michael Turquette
2015-10-22 10:11 ` Michael Turquette
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=1443745589.5336.185.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Igal.Liberman@freescale.com \
--cc=Yuantian.Tang@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--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 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.