From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-media@vger.kernel.org
Subject: Re: v4.1-rcX regression in v4l2 build
Date: Wed, 13 May 2015 21:26:03 +0200 [thread overview]
Message-ID: <87pp64l1o4.fsf@belgarion.home> (raw)
In-Reply-To: <Pine.LNX.4.64.1505122302570.11250@axis700.grange> (Guennadi Liakhovetski's message of "Tue, 12 May 2015 23:09:14 +0200 (CEST)")
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
...zip...
First, a question for Russell :
Given that the current PXA architecture is not implementing the
clk_round_rate() function, while implementing clk_get(), etc..., is it correct
to say that it is betraying the clk API by doing so ?
And now the answers to your mail Guennadi :
>> I've seen some patches on ALKML for PXA CCF, is it in the mainline now?
>> Could that have been the reason? Is CONFIG_COMMON_CLK defined in your
>> .config? Although, no, it's not PXA CCF, it's most probably this
No it's not in clock common framework yet.
PXA will switch to CCF in 4.2, as it missed the 4.1 merge window.
> I think I know how this is possible. PXA uses arch/arm/mach-pxa/clock.c
> for clk ops, and clk_round_rate() isn't defined there... Can we add a
> dummy for PXA? It won't be used anyway as long as PXA doesn't support CCF.
I could do it. I'm a bit reluctant because I already prepared my pull request
which fully shifts PXA to CCF, and adding a dummy function will create a merge
issue.
But is PXA the only one in this case ?
>From a first sight there are 5 ARM architectures in the same case :
rj@belgarion:~/mio_linux/kernel/arch/arm$ grep -rsl 'EXPORT_SYMBOL(clk_round_rate' *
mach-davinci/clock.c
mach-lpc32xx/clock.c
mach-omap1/clock.c
plat-versatile/clock.c
rj@belgarion:~/mio_linux/kernel/arch/arm$ grep -rsl 'EXPORT_SYMBOL(clk_get_rate' *
mach-davinci/clock.c
mach-ep93xx/clock.c
mach-lpc32xx/clock.c
mach-mmp/clock.c
mach-omap1/clock.c
mach-pxa/clock.c
mach-sa1100/clock.c
mach-w90x900/clock.c
plat-versatile/clock.c
Cheers.
--
Robert
next prev parent reply other threads:[~2015-05-13 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 19:46 v4.1-rcX regression in v4l2 build Robert Jarzmik
2015-05-12 20:51 ` Guennadi Liakhovetski
2015-05-12 21:09 ` Guennadi Liakhovetski
2015-05-13 19:26 ` Robert Jarzmik [this message]
2015-05-13 19:48 ` Russell King - ARM Linux
2015-05-13 19:54 ` Robert Jarzmik
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=87pp64l1o4.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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