From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Sylwester Nawrocki <snjw23@gmail.com>,
Josh Wu <josh.wu@atmel.com>,
linux-media@vger.kernel.org,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] [media] at91: add code to initialize and manage the ISI_MCK for Atmel ISI driver.
Date: Thu, 15 Sep 2011 17:30:31 +0200 [thread overview]
Message-ID: <4E721A17.40206@samsung.com> (raw)
In-Reply-To: <20110915132301.GK28104@game.jcrosoft.org>
On 09/15/2011 03:23 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 23:08 Tue 06 Sep , Sylwester Nawrocki wrote:
>> On 09/06/2011 10:05 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>>> I'm not entirely sure on this one, but as we had a similar situation with
>>>> clocks, we decided to extablish the clock hierarchy in the board code, and
>>>> only deal with the actual device clocks in the driver itself. I.e., we
>>>> moved all clk_set_parent() and setting up the parent clock into the board.
>>>> And I do think, this makes more sense, than doing this in the driver, not
>>>> all users of this driver will need to manage the parent clock, right?
>>>
>>> I don't like to manage the clock in the board except if it's manadatory otherwise
>>> we manage this at soc level
You often just can't decide about clocks hierarchy at SoC level as it
can depend on the board layout and which devices are used on it.
>>>
>>> the driver does not have to manage the clock hierachy or detail implementation
>>> but manage the clock enable/disable and speed depending on it's need
I think everyone agrees on that.
>>
>> We had a similar problem in the past and we ended up having the boot loader
>> setting up the parent clock for the device clock. The driver only controls clock
>> gating and sets its clock frequency based on an internal IP version information,
>> derived from the SoC revision.
> sorry NACK
:) When we tried to upstream the code setting up parent clocks in board files
some people disagreed on that too..
>
> I do not want to rely on bootloader
Yeah, I don't believe this is best possible solution either..
> when we will have the DT we will pass it via it right now we need find an
I hope this can be be properly resolved with the DT. I thought there is not
much work
going on yet wrt supporting clocks hierarchy in DT though.
> other generic way
>
> Best Regards,
> J.
--
Regards,
Sylwester
next prev parent reply other threads:[~2011-09-15 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 5:56 [PATCH v2] [media] at91: add code to initialize and manage the ISI_MCK for Atmel ISI driver Josh Wu
2011-09-06 6:54 ` Guennadi Liakhovetski
2011-09-06 20:05 ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-06 21:08 ` Sylwester Nawrocki
2011-09-15 13:23 ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-15 15:30 ` Sylwester Nawrocki [this message]
2011-09-09 10:04 ` Nicolas Ferre
2011-09-22 3:23 ` Wu, Josh
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=4E721A17.40206@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=g.liakhovetski@gmx.de \
--cc=josh.wu@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=snjw23@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox