Hi kg...@kernel.org,

> Lukasz Majewski wrote:
> > 
> > Hi Kukjin,
> > 
> Hi,
> 
> > > Hi Kukjin,
> > >
> > > > The TMU device tree node definition for Exynos4x12 family of
> > > > SoCs.
> > > >
> > > > Signed-off-by: Lukasz Majewski <l.majew...@samsung.com>
> > > > Reviewed-by: Bartlomiej Zolnierkiewicz
> > > > <b.zolnier...@samsung.com> Reviewed-by: Tomasz Figa
> > > > <t.f...@samsung.com>
> > > >
> > > > ---
> > > > Changes for v2:
> > > > - None
> > > >
> > > >  arch/arm/boot/dts/exynos4x12.dtsi |   10 ++++++++++
> > > >  1 file changed, 10 insertions(+)
> > > >
> > > > diff --git a/arch/arm/boot/dts/exynos4x12.dtsi
> > > > b/arch/arm/boot/dts/exynos4x12.dtsi index ad531fe..64c0ece
> > > > 100644 --- a/arch/arm/boot/dts/exynos4x12.dtsi
> > > > +++ b/arch/arm/boot/dts/exynos4x12.dtsi
> > > > @@ -176,4 +176,14 @@
> > > >                         };
> > > >                 };
> > > >         };
> > > > +
> > > > +       tmu@100C0000 {
> > > > +               compatible = "samsung,exynos4412-tmu";
> > > > +               interrupt-parent = <&combiner>;
> > > > +               interrupts = <2 4>;
> > > > +               reg = <0x100C0000 0x100>;
> > > > +               clocks = <&clock 383>;
> > > > +               clock-names = "tmu_apbif";
> > > > +               status = "disabled";
> > > > +       };
> > > >  };
> > >
> > > Can you pull this DT node definition for TMU (as a fix to v3.12)?
> > >
> > > It is crucial for Exynos4412.
> > >
> > 
> > Kukjin, could you pull this patch?
> > 
> Yes, but I'm not sure this is _really_ critical bug fix so maybe this
> will be queued for 3.14.

The thermal fixes were taken by Eduardo for 3.12-rcX cycle. Those were
critical.

The code, which expects those definitions is already in ML, so we can
try to upstream those ASAP.

> 
> If any problem, please kindly let me know.
> 
> Thanks,
> Kukjin
> 

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to