[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaJO6noUd_a5d122G3EiO6-u9bu_gZMg1Tky=PS9O5yUA@mail.gmail.com>
Date: Mon, 30 Nov 2015 14:05:35 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Robert Jarzmik <robert.jarzmik@...e.fr>,
Haojian Zhuang <haojian.zhuang@...il.com>
Cc: Daniel Mack <daniel@...que.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 0/6] pinctrl: pxa: add pxa27x pin control support
On Sat, Nov 21, 2015 at 7:04 PM, Robert Jarzmik <robert.jarzmik@...e.fr> wrote:
> I've been working on this for some time now, it's time pxa archtecture gets a
> proper pin control support.
>
> This serie provides support for pxa27x architecture, and paves the way to pxa2xx
> one. I've tested this on my pxa27x board, in both device-tree and non
> device-tree builds.
So in 2013 Haojian removed PXA3xx, MMP2, PXA168 and PXA910 in favor
of using pinctrl-single.c shared with OMAP.
See
commit 62194200e5e383af2085faf35b6f009364446069
"pinctrl: remove pxa pinctrl driver"
What makes the PXA27x so different from its siblings that it still
warrants its own driver? Why can this one not use pinctrl-single
as well?
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists