From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Olof Johansson' <olof@lixom.net>
Cc: linux-samsung-soc@vger.kernel.org,
'Thomas Abraham' <thomas.ab@samsung.com>,
'Linus Walleij' <linus.walleij@linaro.org>,
'Grant Likely' <grant.likely@secretlab.ca>,
devicetree-discuss@lists.ozlabs.org
Subject: RE: [PATCH 2/2] ARM: dts: fix compatible value for exynos pinctrl
Date: Wed, 09 Jan 2013 17:34:03 -0800 [thread overview]
Message-ID: <00e001cdeed2$94c89a90$be59cfb0$@samsung.com> (raw)
In-Reply-To: <CAOesGMiSgcuD7z4yc2Z+_hi+PZnuv9pa7saeGymwT0DPz=j8dQ@mail.gmail.com>
Olof Johansson wrote:
>
> On Wed, Jan 2, 2013 at 4:20 PM, Kukjin Kim <kgene.kim@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?
>
OK, let me create one patch to fix it :-)
>
> > 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.
>
Agree, let me check again.
> Once we do care, then you can update the dts/dtsi files, but you'll
> need to keep both the old and the new bindings in the C file below.
>
OK, I see.
Thanks.
[...]
- Kukjin
next prev parent reply other threads:[~2013-01-10 1:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 0:20 [PATCH 1/2] ARM: dts: Fix compatible value of pinctrl module on EXYNOS5440 Kukjin Kim
2013-01-03 0:20 ` [PATCH 2/2] ARM: dts: fix compatible value for exynos pinctrl Kukjin Kim
2013-01-05 22:57 ` Olof Johansson
2013-01-10 1:34 ` Kukjin Kim [this message]
2013-01-17 10:16 ` Tomasz Figa
2013-01-17 11:06 ` Tomasz Figa
2013-01-17 14:03 ` Linus Walleij
[not found] ` <1357172423-8217-1-git-send-email-kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-01-05 22:54 ` [PATCH 1/2] ARM: dts: Fix compatible value of pinctrl module on EXYNOS5440 Olof Johansson
2013-01-17 8:34 ` Linus Walleij
2013-01-17 16:39 ` Stephen Warren
2013-01-18 2:24 ` Rob Herring
2013-01-18 3:40 ` Kukjin Kim
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='00e001cdeed2$94c89a90$be59cfb0$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=thomas.ab@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.