From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: exynos: Select PINCTRL_EXYNOS for exynos5
Date: Thu, 09 May 2013 11:45:10 +0200 [thread overview]
Message-ID: <1614776.P66h1VoFPp@amdc1227> (raw)
In-Reply-To: <CAOesGMi=K4iJKjSk3RoynhiCMPPT98v5jADnqZ__TwX_YLw65Q@mail.gmail.com>
Hi Doug, Olof,
On Wednesday 08 of May 2013 12:33:34 Olof Johansson wrote:
> Hi,
>
> On Wed, May 8, 2013 at 11:48 AM, Doug Anderson <dianders@chromium.org>
wrote:
> > Olof,
> >
> > On Wed, May 8, 2013 at 11:19 AM, Olof Johansson <olof@lixom.net> wrote:
> >> Seems like this should be selected by the SoC (ARCH_EXYNOS5) instead
> >> of the board. Actually, I'm not sure we need the board Kconfig entry
> >> long-term; all boards will be dt-only.
> >
> > Good point. Hopefully someone at Samsung can work on removing the
> > board itself? If you'd like me to take this on then let me know and I
> > can put it on my list.
>
> Nothing stops you from doing that on your own. I tend to push back
> onto the maintainers to get them engaged in their own housekeeping,
> but anyone is free to :)
>
> > I'm happy to resubmit my patch under ARCH_EXYNOS5. I'll move the
> > exynos4 one at the same time.
>
> Great.
>
> > I'm going to make the assumption that PINCTRL_EXYNOS and
> > PINCTRL_EXYNOS5440 can happily coexist. Certainly I've got both
> > defined in my tree right now and nothing blows up. I haven't tested
> > on 5440 but things ought to be handled by "compatible" checks, right?
>
> Yes, if they can't coexist then that's a bug.
>
> > I'll also assume that eventually someone will move PINCTRL_EXYNOS5440
> > into PINCTRL_EXYNOS. If PINCTRL_EXYNOS5440 won't eventually move
> > under PINCTRL_EXYNOS then it makes less sense to define PINCTRL_EXYNOS
> > for all exynos parts.
>
> Yeah, it should -- this is just in transition since 5440 was first out
> of the gate with pinctrl.
AFAIK, Exynos5440 contains a completely different pin controller block, which
is not compatible with pinctrl-samsung driver, so I don't see any point of
moving it under PINCTRL_EXYNOS, which is currently used for Exynos 4210, 4x12
and 5250, but will be also extended with driver data for S5PV210 as well.
I'd say that CPU_EXYNOS4210, SOC_EXYNOS4212, SOC_EXYNOS4412 and SOC_EXYNOS5250
should select PINCTRL_EXYNOS and SOC_EXYNOS5440 should be left as is,
selecting PINCTRL_EXYNOS5440.
Best regards,
--
Tomasz Figa
Samsung Poland R&D Center
SW Solution Development, Kernel and System Framework
next prev parent reply other threads:[~2013-05-09 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 17:32 [PATCH] ARM: exynos: Select PINCTRL_EXYNOS for exynos5 Doug Anderson
2013-05-08 18:19 ` Olof Johansson
2013-05-08 18:48 ` Doug Anderson
2013-05-08 19:33 ` Olof Johansson
2013-05-09 9:45 ` Tomasz Figa [this message]
2013-05-09 18:11 ` Doug Anderson
2013-05-09 23:29 ` Kukjin Kim
2013-05-08 18:52 ` [PATCH v2] ARM: exynos: Select PINCTRL_EXYNOS for exynos4/5 at arch level Doug Anderson
2013-05-09 18:12 ` [PATCH v3] ARM: exynos: Select PINCTRL_EXYNOS for exynos4/5 at chip level Doug Anderson
2013-05-14 12:07 ` Linus Walleij
2013-05-14 12:25 ` 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=1614776.P66h1VoFPp@amdc1227 \
--to=t.figa@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox