All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/4] ARM: imx: add initial support for MVF600
Date: Fri, 17 May 2013 14:29:52 +0200	[thread overview]
Message-ID: <201305171429.52646.arnd@arndb.de> (raw)
In-Reply-To: <20130517085714.GG8607@S2101-09.ap.freescale.net>

On Friday 17 May 2013, Shawn Guo wrote:
> On Thu, May 16, 2013 at 12:29:28PM +0200, Arnd Bergmann wrote:
> > On Thursday 16 May 2013 14:10:46 Jingchang Lu wrote:
> > > +config SOC_MVF600
> > 
> > Shouldn't that 'depends on ARCH_MULTI_V7'?
> > 
> SOC_MVF600 is added as a sub-item of ARCH_MXC which already handles the
> ARCH_MULTI_* dependency.

Ah, makes sense.

> > Can you describe how much Vybrid is actually like MXC? Do you actually
> > use most of the mach-imx code?
> > 
> Jingchang mentioned some IP blocks shared between IMX and Vybrid.  Right
> now, mvf600 reuses mxc_restart() and some amount of clk code
> clk-pllv3.c, clk-gate2.c clk.c etc. in arch/arm/mach-imx.

Ok.

> > Actually I think you should move that driver to drivers/clk and use
> > of_clk_init(NULL) to initialize it.
> > 
> The mvf600 clock driver uses a lot of base clk support from mach-imx,
> and can not be moved into drivers/clk as a single driver.  Right now, in
> IMX clock drivers, we call of_clk_init() to only register fixed rate
> clocks, since all the other clocks are not represented in device tree.

What are your plans for this in the long run?

> > It would be nice if we could integrate that into the watchdog driver,
> > so that driver just registers a pm_restart function when it gets loaded.
> > It is a rather small driver, so it would not hurt to always load it.
> > 
> Sound like a good idea.  We will consider it as another cleanup task for
> mach-imx.

Ok
 
> > What is the mscm? Shouldn't the boot loader have set this up correctly?
> > If you can remove that code from the kernel, you can use the default
> > irqchip_init call.
> > 
> Yeah, and if we find another way for l2x0_of_init() call.

Good point. That is something we need to do anyway.

> > > +static const char *mvf600_dt_compat[] __initdata = {
> > > +	"fsl,mvf600",
> > > +	NULL,
> > > +};
> > > +
> > > +DT_MACHINE_START(VYBRID_VF6XX, "Freescale Vybrid MVF600 (Device Tree)")
> > > +	.init_irq	= mvf600_init_irq,
> > > +	.init_time	= mvf600_init_time,
> > > +	.init_machine   = mvf600_init_machine,
> > > +	.dt_compat	= mvf600_dt_compat,
> > > +	.restart	= mxc_restart,
> > > +MACHINE_END
> > 
> > If we can do all of the above, we can actually remove the entire machine
> > descriptor here, since all its members are NULL.
> > 
> Yeah, we understand the goal, and this will be the goal of mach-imx
> cleanup.

Ok. I guess we just won't be there for 3.11 then.

	Arnd

  reply	other threads:[~2013-05-17 12:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  6:10 [PATCH v3 0/4] Add initial Freescale Vybrid MVF600 support Jingchang Lu
2013-05-16  6:10 ` [PATCH v3 1/4] ARM: imx: add MVF600 clock support Jingchang Lu
2013-05-16  6:10 ` [PATCH v3 2/4] ARM: imx: add initial support for MVF600 Jingchang Lu
2013-05-16 10:29   ` Arnd Bergmann
2013-05-17  8:57     ` Shawn Guo
2013-05-17 12:29       ` Arnd Bergmann [this message]
2013-05-17 12:31         ` Arnd Bergmann
2013-05-17 13:06         ` Shawn Guo
2013-05-17 13:17           ` Arnd Bergmann
2013-05-17 13:54             ` Shawn Guo
2013-05-21  2:17             ` Shawn Guo
2013-05-17  9:08   ` Shawn Guo
2013-05-18  1:27   ` Shawn Guo
2013-05-16  6:10 ` [PATCH v3 3/4] ARM: dts: add SoC level device tree source " Jingchang Lu
2013-05-19 14:14   ` Shawn Guo
2013-05-16  6:10 ` [PATCH v3 4/4] ARM: dts: add initial MVF600 Tower board dts support Jingchang Lu
2013-05-19 15:29   ` Shawn Guo
2013-05-20  5:01     ` Lu Jingchang-B35083
2013-05-20  5:53       ` Shawn Guo

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=201305171429.52646.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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.