From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: kgene.kim@samsung.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, m.szyprowski@samsung.com
Subject: Re: [PATCH] ARM: dts: Specify default clocks for Exynos4 FIMC devices
Date: Fri, 26 Sep 2014 15:45:09 +0200 [thread overview]
Message-ID: <54256DE5.5050203@samsung.com> (raw)
In-Reply-To: <5425690A.6080102@gmail.com>
On 26/09/14 15:24, Tomasz Figa wrote:
> I'm not concerned specifically with Exynos4210, but with placing such
> kind of data in common dtsi files.
>
> Notice that even on boards which have correct initialization done by
> firmware, this will cause the settings to be overwritten, even if the
> firmware sets correct, but different values, regardless of them being
> clock parents or rates.
>
> To me, even if this would mean duplicating some data, making this per
> board and present only in dts files of boards that actually need this
> (i.e. are known to have broken firmware) sounds more reasonable.
OTOH by having those settings in device tree would ensure the clock
tree is set correctly, regardless of the firmware. There is only one
correct clock parent for these devices, so the kernel couldn't do any
harm. I'd say it never worked in practice to rely on the bootloader
to configure these things, and one could say the firmware has been
broken in general with regards to this issue.
--
Regards,
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: Fri, 26 Sep 2014 15:45:09 +0200 [thread overview]
Message-ID: <54256DE5.5050203@samsung.com> (raw)
In-Reply-To: <5425690A.6080102@gmail.com>
On 26/09/14 15:24, Tomasz Figa wrote:
> I'm not concerned specifically with Exynos4210, but with placing such
> kind of data in common dtsi files.
>
> Notice that even on boards which have correct initialization done by
> firmware, this will cause the settings to be overwritten, even if the
> firmware sets correct, but different values, regardless of them being
> clock parents or rates.
>
> To me, even if this would mean duplicating some data, making this per
> board and present only in dts files of boards that actually need this
> (i.e. are known to have broken firmware) sounds more reasonable.
OTOH by having those settings in device tree would ensure the clock
tree is set correctly, regardless of the firmware. There is only one
correct clock parent for these devices, so the kernel couldn't do any
harm. I'd say it never worked in practice to rely on the bootloader
to configure these things, and one could say the firmware has been
broken in general with regards to this issue.
--
Regards,
Sylwester
next prev parent reply other threads:[~2014-09-26 13:45 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
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 [this message]
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=54256DE5.5050203@samsung.com \
--to=s.nawrocki@samsung.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 \
--cc=tomasz.figa@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 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.