RE: [PATCH 2/3] ARM: exynos5420: dt: add clock entries to watchdog node

[Kukjin Kim <kgene@kernel.org>]

Sachin Kamat wrote:
> 
> On 24 July 2013 16:42, Tomasz Figa <t.figa@samsung.com> wrote:
> > On Wednesday 24 of July 2013 15:31:43 Sachin Kamat wrote:
> >> Hi Tomasz,
> >>
> >> On 24 July 2013 15:24, Tomasz Figa <t.figa@samsung.com> wrote:
> >> > Hi Sachin,
> >> >
> >> > On Wednesday 24 of July 2013 15:18:26 Sachin Kamat wrote:
> >> >> Hi Leela,
> >> >>
> >> >> On 24 July 2013 15:08, Leela Krishna Amudala <l.krishna@samsung.com>
> >> >
> >> > wrote:
> >> >> > This patch adds clock entries to watchdog node for exynos5420
> >> >> > as per the common clock framework of exynos5420
> >> >> >
> >> >> > Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
> >> >> > Reviewed-by: Doug Anderson <dianders@chromium.org>
> >> >> > Signed-off-by: Leela Krishna Amudala <l.krishna@samsung.com>
> >> >> > ---
> >> >> >
> >> >> >  arch/arm/boot/dts/exynos5420.dtsi |    6 ++++++
> >> >> >  1 file changed, 6 insertions(+)
> >> >> >
> >> >> > diff --git a/arch/arm/boot/dts/exynos5420.dtsi
> >> >> > b/arch/arm/boot/dts/exynos5420.dtsi index 8c54c4b..e1d2d20 100644
> >> >> > --- a/arch/arm/boot/dts/exynos5420.dtsi
> >> >> > +++ b/arch/arm/boot/dts/exynos5420.dtsi
> >> >> > @@ -145,4 +145,10 @@
> >> >> >
> >> >> >                 clocks = <&clock 260>, <&clock 131>;
> >> >> >                 clock-names = "uart", "clk_uart_baud0";
> >> >> >
> >> >> >         };
> >> >> >
> >> >> > +
> >> >> > +       watchdog {
> >> >> > +               clocks = <&clock 316>;
> >> >> > +               clock-names = "watchdog";
> >> >> > +               status = "okay";
> >> >>
> >> >> Generally you do "okay" in specific board dts files.
> >> >
> >> > Not necessarily. The status property should be set to okay whenever
> the
> >> > device represented by such node can already work with given set of
> >> > information (properties).
> >> >
> >> > Given the fact that watchdog driver does not require any board
> specific
> >> > information, it can be instantiated regardless of the board.
> >>
> >> Yes you are right. But I was thinking of keeping this (enabling) as an
> >> option at the board level.
> >> We do this for some of the other IPs too where even though we have all
> >> the properties we keep them disabled.
> >
> > Yes and this is wrong. Device tree is only a way to list all the
> hardware
> > present on particular platform. You don't define which components are
> used
> > or not depending on use case, but rather all the hardware that can be
> used
> > on given board should be enabled on DT level.
> 
> This is contrary to the fact that we disable everything by default in
> the top level dt files and only enable them as required in the board
> dts files.
> 
> >
> > To illustrate the problem please consider that in the end, a dtb file
> will
> > be fused into board ROM (or at most flash memory) and passed to the
> kernel
> > by the bootloader. If you disable some hardware on DT level even if it
> can
> > be physically used on the board, there will be no way to reenable it, if
> > some user wanted to use it, because that would require editing the fused
> > dtb.
> 
> I believe some h/w will be disabled in dt only if it should not be
> used for whatever reason. If there is no reason then ofcourse they
> would be enabled IMHO. Whatever be the case the choice of enabling or
> disabling should be done at the leaf node (at board level). No?
> 
In my opinion, some IPs can be disabled according to the board manager. And
if updated DTB is required due to kernel updating or whatever, DTB should be
updated accordingly.

One more, actually we don't have no general way to fuse DTB in firmware when
kernel is updated. So board manger who controls/decides what features should
be supported on their board should consider the board's features and
environments...

- Kukjin