From: sylvester.nawrocki@gmail.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 1/7] media: V4L2: add temporary clock helpers
Date: Thu, 11 Apr 2013 22:14:43 +0200 [thread overview]
Message-ID: <516719B3.8060502@gmail.com> (raw)
In-Reply-To: <20130411185258.7915.67263@quantum>
Hi,
On 04/11/2013 08:52 PM, Mike Turquette wrote:
[...]
>>> So, you enable CFF, it provides its own clk_* implementation like
>>> clk_get_rate() etc. Now, PXA already has it defined in
>>> arch/arm/mach-pxa/clock.c. Don't think this is going to fly.
>>
>> agree.
>
> Hi,
>
> I came into this thread late and don't have the actual patches in my
> inbox for review. That said, I don't understand why V4L2 cares about
> the clk framework *implementation*? The clk.h api is the same for
> platforms using the common struct clk and those still using the legacy
> method of defining their own struct clk. If drivers are only consumers
> of the clk.h api then the implementation underneath should not matter.
I came to similar conclusions previously, but in case when one of the two
drivers is the clock provider I think there is still an issue there.
The drivers are supposed to be platform agnostic, but the clock provider
would have to include mach specific declarations of struct clk, wouldn't
it ?
Regards,
Sylwester
next prev parent reply other threads:[~2013-04-11 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGsJ_4zCRBvEX9xEDCr27JLK6wYp_2T_wk2hzVjqpKinbL=9pg@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.1304110921480.23859@axis700.grange>
2013-04-11 8:22 ` [PATCH v8 1/7] media: V4L2: add temporary clock helpers Barry Song
2013-04-11 8:36 ` Guennadi Liakhovetski
2013-04-11 8:59 ` Barry Song
2013-04-11 18:52 ` Mike Turquette
2013-04-11 20:14 ` Sylwester Nawrocki [this message]
2013-04-11 22:35 ` Laurent Pinchart
2013-04-11 23:19 ` Mike Turquette
2013-04-12 8:22 ` Laurent Pinchart
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=516719B3.8060502@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).