[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4132795.KBVIQFTevx@wuerfel>
Date: Thu, 27 Nov 2014 13:36:36 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Tomasz Figa <tomasz.figa@...il.com>
Cc: Chanwoo Choi <cw00.choi@...sung.com>,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Kukjin Kim <kgene.kim@...sung.com>,
Mark Rutland <mark.rutland@....com>,
Olof Johansson <olof@...om.net>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Thomas Abraham <thomas.abraham@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
Kyungmin Park <kyungmin.park@...sung.com>,
InKi Dae <inki.dae@...sung.com>,
Chanho Park <chanho61.park@...sung.com>,
geunsik.lim@...sung.com, "sw0312.kim" <sw0312.kim@...sung.com>,
Jaehoon Chung <jh80.chung@...sung.com>,
Abhilash Kesavan <a.kesavan@...sung.com>,
devicetree <devicetree@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 01/19] pinctrl: exynos: Add support for Exynos5433
On Thursday 27 November 2014 21:14:59 Tomasz Figa wrote:
> > my impression is that with the
> > move to arm64, you should come up with a new binding that can fully
> > describe each controller so you don't have to add new code and bindings
> > for each future SoC that uses the same scheme.
>
> Still, this is exactly the same thing I thought when initially refactoring this
> driver 2 years ago and what was dismissed at that time due to people
> supposedly not wanting that much data in DT. If this point of view has changed,
> then I fully support your view, though.
I guess people were at the time underestimating the rate at which Samsung
comes out with new SoC variants that are all slightly different.
Arnd
--
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