From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Daniel Drake <drake@endlessm.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH] ARM: dts: Specify default clocks for Exynos4 FIMC devices
Date: Thu, 25 Sep 2014 20:17:46 +0200 [thread overview]
Message-ID: <54245C4A.8050902@samsung.com> (raw)
In-Reply-To: <CAD8Lp44n3xArQ-xvZsFdYn13x80Dqv1oCY=dLm1UPxKr8XbyJQ@mail.gmail.com>
On 19/09/14 01:53, Daniel Drake wrote:
> On Wed, Sep 10, 2014 at 10:37 AM, Sylwester Nawrocki
> <s.nawrocki@samsung.com> wrote:
>> The default mux and divider clocks are specified in device tree
>> so that the FIMC devices in Exynos4210 and Exynos4x12 SoCs are
>> clocked from recommended clock source and with maximum supported
>> frequency. If needed these settings could be overrode in board
>> specific dts files, however they are in practice optimal in most
>> cases.
>
> Another consideration for this patch.
>
> fimc-core.c already has probe-time code that tries to set the clock
> frequency, using a clock-frequency property in the DT, and falling
> back to a hardcoded value in the driver. Maybe it is best to just set
> the clock rate from one place.
Indeed, thanks for pointing this out. I will submit a patch to remove
the fallback in fimc-core.c. So the driver doesn't touch both: clock
rate and parent setting if 'clock-rates' property is specified in DT.
I think clock-frequency property in the FIMC DT binding should be
deprecated. So the initial parent clock and frequency settings are
handled similarly for all relevant IP blocks, and there is no need
to code such things in each individual driver.
--
Thanks,
Sylwester
WARNING: multiple messages have this Message-ID (diff)
From: s.nawrocki@samsung.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: Specify default clocks for Exynos4 FIMC devices
Date: Thu, 25 Sep 2014 20:17:46 +0200 [thread overview]
Message-ID: <54245C4A.8050902@samsung.com> (raw)
In-Reply-To: <CAD8Lp44n3xArQ-xvZsFdYn13x80Dqv1oCY=dLm1UPxKr8XbyJQ@mail.gmail.com>
On 19/09/14 01:53, Daniel Drake wrote:
> On Wed, Sep 10, 2014 at 10:37 AM, Sylwester Nawrocki
> <s.nawrocki@samsung.com> wrote:
>> The default mux and divider clocks are specified in device tree
>> so that the FIMC devices in Exynos4210 and Exynos4x12 SoCs are
>> clocked from recommended clock source and with maximum supported
>> frequency. If needed these settings could be overrode in board
>> specific dts files, however they are in practice optimal in most
>> cases.
>
> Another consideration for this patch.
>
> fimc-core.c already has probe-time code that tries to set the clock
> frequency, using a clock-frequency property in the DT, and falling
> back to a hardcoded value in the driver. Maybe it is best to just set
> the clock rate from one place.
Indeed, thanks for pointing this out. I will submit a patch to remove
the fallback in fimc-core.c. So the driver doesn't touch both: clock
rate and parent setting if 'clock-rates' property is specified in DT.
I think clock-frequency property in the FIMC DT binding should be
deprecated. So the initial parent clock and frequency settings are
handled similarly for all relevant IP blocks, and there is no need
to code such things in each individual driver.
--
Thanks,
Sylwester
next prev parent reply other threads:[~2014-09-25 18:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 16:37 [PATCH] ARM: dts: Specify default clocks for Exynos4 FIMC devices Sylwester Nawrocki
2014-09-10 16:37 ` Sylwester Nawrocki
2014-09-18 19:27 ` Daniel Drake
2014-09-18 19:27 ` Daniel Drake
2014-09-25 18:05 ` Sylwester Nawrocki
2014-09-25 18:05 ` Sylwester Nawrocki
2014-09-25 19:44 ` Daniel Drake
2014-09-25 19:44 ` Daniel Drake
2014-09-25 20:47 ` Daniel Drake
2014-09-25 20:47 ` Daniel Drake
2014-09-18 23:53 ` Daniel Drake
2014-09-18 23:53 ` Daniel Drake
2014-09-25 18:17 ` Sylwester Nawrocki [this message]
2014-09-25 18:17 ` Sylwester Nawrocki
2014-09-25 21:58 ` Tomasz Figa
2014-09-25 21:58 ` Tomasz Figa
2014-09-26 11:01 ` Sylwester Nawrocki
2014-09-26 11:01 ` Sylwester Nawrocki
2014-09-26 13:24 ` Tomasz Figa
2014-09-26 13:24 ` Tomasz Figa
2014-09-26 13:45 ` Sylwester Nawrocki
2014-09-26 13:45 ` Sylwester Nawrocki
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=54245C4A.8050902@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=drake@endlessm.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.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 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.