[PATCH 2/2] ARM: dts: fix compatible value for exynos pinctrl

[Tomasz Figa]

Hi Olof,

On Saturday 05 of January 2013 14:57:54 Olof Johansson wrote:
> On Wed, Jan 2, 2013 at 4:20 PM, Kukjin Kim <kgene.kim at samsung.com> 
wrote:
> > Fix the incorrect compatible property value of pinctrl for EXYNOS4
> > SoCs.
> Ah, this answers my question from the previous patch. So, why do 5450
> as a separate patch?
> 
> > diff --git
> > a/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt
> > b/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt index
> > e97a278..4598a47 100644
> > --- a/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt
> > +++ b/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt
> > @@ -7,9 +7,9 @@ on-chip controllers onto these pads.
> > 
> >  Required Properties:
> >  - compatible: should be one of the following.
> > 
> > -  - "samsung,pinctrl-exynos4210": for Exynos4210 compatible
> > pin-controller. -  - "samsung,pinctrl-exynos4x12": for Exynos4x12
> > compatible pin-controller. -  - "samsung,pinctrl-exynos5250": for
> > Exynos5250 compatible pin-controller. +  -
> > "samsung,exynos4210-pinctrl": for Exynos4210 compatible
> > pin-controller. +  - "samsung,exynos4x12-pinctrl": for Exynos4x12
> > compatible pin-controller. +  - "samsung,exynos5250-pinctrl": for
> > Exynos5250 compatible pin-controller.
> Do we care about backwards compatibility for ARM device trees yet?
> It's becoming time to start caring soon, if we don't. So while this
> might be OK for this time around, we should start requiring some
> backwards compatibility for bindings that have been used in at least
> one released kernel.

This also brings the general problem of dts verification.

As of now, we don't have any way of checking dts files for compliance with 
defined bindings. Moreover we don't even have a way of defining those 
bindings other than plain text documentation.

Now, the problem is that anyone can put anything in their device tree 
sources and we can't check if the information is specified correctly by 
any other means that someone reading it and confirming with documentation 
and/or driver code (the documentation isn't always up to date...).

I remember there was some effort going towards encoding device tree 
bindings using something like XML schemas, but I'm not sure to what point 
it got and what was the conclusion. (Personally I think that it was a bit 
overcomplicated, but I never had time to polish and implement some of my 
ideas, eventually letting the problem fade off from my mind.)

Best regards,
-- 
Tomasz Figa
Samsung Poland R&D Center
SW Solution Development, Linux Platform