From: "José Miguel Gonçalves" <jose.goncalves@inov.pt>
To: "Heiko Stübner" <heiko@sntech.de>,
"Linus Walleij" <linus.walleij@linaro.org>
Cc: Ben Dooks <ben-linux@fluff.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Tomasz Figa <t.figa@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: S3C24XX: Fix configuration of gpio port sizes on S3C24XX.
Date: Fri, 13 Dec 2013 09:38:35 +0000 [thread overview]
Message-ID: <52AAD59B.7070203@inov.pt> (raw)
In-Reply-To: <201312130942.03674.heiko@sntech.de>
Hi Heiko,
On 13-12-2013 08:42, Heiko Stübner wrote:
>
> But Jose, you should really really look into moving to devicetree with your
> platform, if you're not already doing so. Pinctrl support is already present,
> and I'm hopefull the move to the common clock framework I posted a few days
> ago might make it too.
>
I'm currently maintaining a deployed equipment whose development started
some time ago, so I still need to use a 3.9 kernel with the traditional
hardware initialization. But, of course, for any new developments based
on the same S3C24XX platform, I will look in migrating to the device tree.
Best regards,
José Gonçalves
next prev parent reply other threads:[~2013-12-13 9:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 8:46 [PATCH] ARM: S3C24XX: Fix configuration of gpio port sizes on S3C24XX José Miguel Gonçalves
2013-09-11 16:27 ` Heiko Stübner
2013-09-27 14:17 ` Linus Walleij
2013-12-13 1:55 ` José Miguel Gonçalves
2013-12-13 8:12 ` Linus Walleij
2013-12-13 8:42 ` Heiko Stübner
2013-12-13 8:42 ` Heiko Stübner
2013-12-13 9:38 ` José Miguel Gonçalves [this message]
2013-12-13 9:24 ` kgene
2013-12-13 9:29 ` Heiko Stübner
2013-12-13 9:29 ` Heiko Stübner
2013-12-13 9:37 ` Linus Walleij
2013-12-13 9:37 ` Linus Walleij
2013-12-20 9:12 ` Linus Walleij
2013-12-20 20:57 ` Kukjin Kim
2013-12-20 20:57 ` Kukjin Kim
2014-01-02 12:53 ` Linus Walleij
2014-01-02 12:53 ` Linus Walleij
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=52AAD59B.7070203@inov.pt \
--to=jose.goncalves@inov.pt \
--cc=ben-linux@fluff.org \
--cc=heiko@sntech.de \
--cc=kgene.kim@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=t.figa@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.