From: Josh Cartwright <josh.cartwright@ni.com>
To: Nick Bowler <nbowler@elliptictech.com>
Cc: arm@kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
John Linn <john.linn@xilinx.com>
Subject: Re: [PATCH v3 3/5] zynq: remove use of CLKDEV_LOOKUP
Date: Wed, 24 Oct 2012 13:16:56 -0500 [thread overview]
Message-ID: <20121024181656.GS20593@beefymiracle.amer.corp.natinst.com> (raw)
In-Reply-To: <20121024133231.GA28661@elliptictech.com>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
On Wed, Oct 24, 2012 at 09:32:32AM -0400, Nick Bowler wrote:
> On 2012-10-23 19:34 -0500, Josh Cartwright wrote:
> > The Zynq support in mainline does not (yet) make use of any of the
> > generic clk or clk lookup functionality. Remove what is upstream for
> > now, until the out-of-tree implementation is in suitable form for
> > merging.
> >
> > An important side effect of this patch is that it allows the building of
> > a Zynq kernel without running into unresolved symbol problems:
> >
> > drivers/built-in.o: In function `amba_get_enable_pclk':
> > clkdev.c:(.text+0x444): undefined reference to `clk_enable'
>
> For the record, I think this was introduced by commit 56a34b03ff427
> ("ARM: versatile: Make plat-versatile clock optional") which forgot to
> select PLAT_VERSATILE_CLOCK on Zynq. This is not all that surprising,
> because the fact that Zynq "uses" PLAT_VERSATILE is secretly hidden in
> the Makefile.
Yes, indeed. I did try to fix my problems by having ARCH_ZYNQ select
PLAT_VERSATILE_CLOCK, but I recall running into additional build
problems...
But now that I just tried it again, it all seems to work, barring
Kconfig complaining I've selected PLAT_VERSATILE_CLOCK, but not
PLAT_VERSATILE. (Having ARCH_ZYNQ select PLAT_VERSATILE, however, leads
to additional build problems).
> Nevertheless, the only feature from versatile that Zynq needed was the
> clock support, so this patch should *also* delete the secret use of
> plat-versatile by removing this line from arch/arm/Makefile:
>
> plat-$(CONFIG_ARCH_ZYNQ) += versatile
Yes, indeed it should.
Thanks,
Josh
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-10-24 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 0:32 [PATCH v3 0/5] zynq subarch cleanups Josh Cartwright
2012-10-24 0:33 ` [PATCH v3 1/5] zynq: use GIC device tree bindings Josh Cartwright
2012-10-24 12:03 ` Arnd Bergmann
2012-10-24 0:34 ` [PATCH v3 2/5] zynq: use pl310 " Josh Cartwright
2012-10-24 12:04 ` Arnd Bergmann
2012-10-24 0:34 ` [PATCH v3 3/5] zynq: remove use of CLKDEV_LOOKUP Josh Cartwright
2012-10-24 12:05 ` Arnd Bergmann
2012-10-24 13:32 ` Nick Bowler
2012-10-24 18:16 ` Josh Cartwright [this message]
2012-10-24 0:35 ` [PATCH v3 4/5] ARM: annotate VMALLOC_END definition with _AC Josh Cartwright
2012-10-24 12:07 ` Arnd Bergmann
2012-10-24 0:35 ` [PATCH v3 5/5] zynq: move static peripheral mappings Josh Cartwright
2012-10-24 12:08 ` Arnd Bergmann
2012-10-24 12:09 ` [PATCH v3 0/5] zynq subarch cleanups Arnd Bergmann
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=20121024181656.GS20593@beefymiracle.amer.corp.natinst.com \
--to=josh.cartwright@ni.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=john.linn@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@elliptictech.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
Powered by JetHome