From: Christoph Fritz <chf.fritz@googlemail.com>
To: Nishanth Menon <nm@ti.com>
Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Ulf Hansson <ulf.hansson@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Tony Lindgren <tony@atomide.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Archit Taneja <archit@ti.com>,
bcousson@baylibre.com, "Hans J. Koch" <hjk@hansjkoch.de>,
Daniel Mack <zonque@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, Tero Kristo <t-kristo@ti.com>
Subject: Re: [PATCH v2 4/5] ARM: OMAP2+: Add pdata quirk for sys_clkout2 for omap3 DBB056
Date: Mon, 27 Jan 2014 01:01:18 +0100 [thread overview]
Message-ID: <20140127000118.GA30378@mars> (raw)
In-Reply-To: <52E01D01.2010709@ti.com>
Hi Nishanth,
thanks for reviewing this patch. Please see my comments below.
On Wed, Jan 22, 2014 at 01:33:21PM -0600, Nishanth Menon wrote:
> On 01/22/2014 01:04 PM, Christoph Fritz wrote:
> > Full device tree support for clock control is not yet accomplished. Until
> > then, configure the 24Mhz of sys_clkout2 to feed an USB-Hub here.
> >
> > Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
> > ---
> > arch/arm/mach-omap2/pdata-quirks.c | 37 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 37 insertions(+)
> >
> > diff --git a/arch/arm/mach-omap2/pdata-quirks.c b/arch/arm/mach-omap2/pdata-quirks.c
> > index a58590f..9ef7ca8 100644
> > --- a/arch/arm/mach-omap2/pdata-quirks.c
> > +++ b/arch/arm/mach-omap2/pdata-quirks.c
> > @@ -171,6 +171,43 @@ static void __init am3517_evm_legacy_init(void)
> > }
> > static void __init omap3_dbb056_legacy_init(void)
> > {
> > + struct clk *clkout2;
> > + struct clk *cm96fck;
> > +
> > + /* Reparent clkout2 to 96M_FCK */
> > + pr_info("a83x-quirk: Late Reparent clkout2 to 96M_FCK\n");
> what'd be a83x?
It's the computer-on-module name. Will get changed to __func__.
> > + clkout2 = clk_get(NULL, "clkout2_src_ck");
> > + if(clkout2 < 0) {
> > + pr_err("a83x-quirk: couldn't get clkout2_src_ck\n");
> > + return;
> > + }
> > + cm96fck = clk_get(NULL, "cm_96m_fck");
> > + if(cm96fck < 0) {
> > + pr_err("a83x-quirk: couldn't get cm_96m_fck\n");
> > + return;
> > + }
> > + if(clk_set_parent(clkout2, cm96fck) < 0) {
> > + pr_err("a83x-quirk: couldn't reparent clkout2_src_ck\n");
> > + return;
> > + }
> yep - we have bunch of similar code in drivers/clk/ti -> but we'd need
> a generic property to handle this.
This whole quirk of configuring sys_clkout2 in a platform file will
go away. Tero is planning to post some RFC patches to configure this
by DT.
> > +
> > + /* Set clkout2 to 24MHz for internal usb hub*/
> > + pr_info("a83x-quirk: Set clkout2 to 24MHz for internal usb hub\n");
> > + clkout2 = clk_get(NULL, "sys_clkout2");
> > + if(clkout2 < 0) {
> > + pr_err("a83x-quirk: couldn't get sys_clkout2\n");
> > + return;
> > + }
> > + if(clk_set_rate(clkout2, 24000000) < 0) {
> same here.
> > + printk(KERN_ERR "board-omap3evm: couldn't set sys_clkout2 rate\n");
> "board-omap3evm:" copy paste?
> any reason why not pr_err?
will get fixed
> > + return;
> > + }
> > + if(clk_prepare_enable(clkout2) < 0) {
> > + pr_err("a83x-quirk: couldn't enable sys_clkout2\n");
> > + return;
> > + }
> > +
> > + /* Initialize display */
> > omap3_dbb056_display_init_of();
> > }
> > #endif /* CONFIG_ARCH_OMAP3 */
> >
>
> looking at the coding style, I assume we'd missed running
> checkpatch.pl --strict?
Let me reroll this patch in a new v3 set.
Thanks
-- Christoph
WARNING: multiple messages have this Message-ID (diff)
From: chf.fritz@googlemail.com (Christoph Fritz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/5] ARM: OMAP2+: Add pdata quirk for sys_clkout2 for omap3 DBB056
Date: Mon, 27 Jan 2014 01:01:18 +0100 [thread overview]
Message-ID: <20140127000118.GA30378@mars> (raw)
In-Reply-To: <52E01D01.2010709@ti.com>
Hi Nishanth,
thanks for reviewing this patch. Please see my comments below.
On Wed, Jan 22, 2014 at 01:33:21PM -0600, Nishanth Menon wrote:
> On 01/22/2014 01:04 PM, Christoph Fritz wrote:
> > Full device tree support for clock control is not yet accomplished. Until
> > then, configure the 24Mhz of sys_clkout2 to feed an USB-Hub here.
> >
> > Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
> > ---
> > arch/arm/mach-omap2/pdata-quirks.c | 37 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 37 insertions(+)
> >
> > diff --git a/arch/arm/mach-omap2/pdata-quirks.c b/arch/arm/mach-omap2/pdata-quirks.c
> > index a58590f..9ef7ca8 100644
> > --- a/arch/arm/mach-omap2/pdata-quirks.c
> > +++ b/arch/arm/mach-omap2/pdata-quirks.c
> > @@ -171,6 +171,43 @@ static void __init am3517_evm_legacy_init(void)
> > }
> > static void __init omap3_dbb056_legacy_init(void)
> > {
> > + struct clk *clkout2;
> > + struct clk *cm96fck;
> > +
> > + /* Reparent clkout2 to 96M_FCK */
> > + pr_info("a83x-quirk: Late Reparent clkout2 to 96M_FCK\n");
> what'd be a83x?
It's the computer-on-module name. Will get changed to __func__.
> > + clkout2 = clk_get(NULL, "clkout2_src_ck");
> > + if(clkout2 < 0) {
> > + pr_err("a83x-quirk: couldn't get clkout2_src_ck\n");
> > + return;
> > + }
> > + cm96fck = clk_get(NULL, "cm_96m_fck");
> > + if(cm96fck < 0) {
> > + pr_err("a83x-quirk: couldn't get cm_96m_fck\n");
> > + return;
> > + }
> > + if(clk_set_parent(clkout2, cm96fck) < 0) {
> > + pr_err("a83x-quirk: couldn't reparent clkout2_src_ck\n");
> > + return;
> > + }
> yep - we have bunch of similar code in drivers/clk/ti -> but we'd need
> a generic property to handle this.
This whole quirk of configuring sys_clkout2 in a platform file will
go away. Tero is planning to post some RFC patches to configure this
by DT.
> > +
> > + /* Set clkout2 to 24MHz for internal usb hub*/
> > + pr_info("a83x-quirk: Set clkout2 to 24MHz for internal usb hub\n");
> > + clkout2 = clk_get(NULL, "sys_clkout2");
> > + if(clkout2 < 0) {
> > + pr_err("a83x-quirk: couldn't get sys_clkout2\n");
> > + return;
> > + }
> > + if(clk_set_rate(clkout2, 24000000) < 0) {
> same here.
> > + printk(KERN_ERR "board-omap3evm: couldn't set sys_clkout2 rate\n");
> "board-omap3evm:" copy paste?
> any reason why not pr_err?
will get fixed
> > + return;
> > + }
> > + if(clk_prepare_enable(clkout2) < 0) {
> > + pr_err("a83x-quirk: couldn't enable sys_clkout2\n");
> > + return;
> > + }
> > +
> > + /* Initialize display */
> > omap3_dbb056_display_init_of();
> > }
> > #endif /* CONFIG_ARCH_OMAP3 */
> >
>
> looking at the coding style, I assume we'd missed running
> checkpatch.pl --strict?
Let me reroll this patch in a new v3 set.
Thanks
-- Christoph
next prev parent reply other threads:[~2014-01-27 0:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 19:04 [PATCH v2 0/5] ARM: add omap3 INCOstartec board support Christoph Fritz
2014-01-22 19:04 ` Christoph Fritz
2014-01-22 19:04 ` [PATCH v2 1/5] ARM: dts: omap3: Add support for INCOstartec a83x module Christoph Fritz
2014-01-22 19:04 ` Christoph Fritz
2014-01-22 19:48 ` Nishanth Menon
2014-01-22 19:48 ` Nishanth Menon
2014-01-27 0:04 ` Christoph Fritz
2014-01-27 0:04 ` Christoph Fritz
2014-01-22 19:04 ` [PATCH v2 2/5] ARM: dts: omap3: Add support for INCOstartec DBB056 baseboard Christoph Fritz
2014-01-22 19:04 ` Christoph Fritz
2014-01-22 19:04 ` [PATCH v2 3/5] ARM: OMAP2+: add legacy display for omap3 DBB056 Christoph Fritz
2014-01-22 19:04 ` Christoph Fritz
2014-01-22 19:04 ` [PATCH v2 4/5] ARM: OMAP2+: Add pdata quirk for sys_clkout2 " Christoph Fritz
2014-01-22 19:04 ` Christoph Fritz
2014-01-22 19:33 ` Nishanth Menon
2014-01-22 19:33 ` Nishanth Menon
2014-01-27 0:01 ` Christoph Fritz [this message]
2014-01-27 0:01 ` Christoph Fritz
2014-01-22 19:04 ` [PATCH v2 5/5] [RFC] omapdss: remove FEAT_DPI_USES_VDDS_DSI from omap3 Christoph Fritz
2014-01-22 19:04 ` Christoph Fritz
2014-01-22 19:21 ` Javier Martinez Canillas
2014-01-22 19:21 ` Javier Martinez Canillas
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=20140127000118.GA30378@mars \
--to=chf.fritz@googlemail.com \
--cc=archit@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=hjk@hansjkoch.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=t-kristo@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.org \
--cc=zonque@gmail.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.