[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5628F048.3000501@ti.com>
Date: Thu, 22 Oct 2015 10:18:48 -0400
From: Murali Karicheri <m-karicheri2@...com>
To: santosh shilimkar <santosh.shilimkar@...cle.com>,
Franklin S Cooper Jr <fcooper@...com>,
<linux@....linux.org.uk>, <ssantosh@...nel.org>,
<ulf.hansson@...aro.org>, <grygorii.strashko@...com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-mmc@...r.kernel.org>
Subject: Re: [PATCH 1/5] ARM: Keystone: Enable PINCTRL for Keystone ARCH
On 10/20/2015 09:26 PM, santosh shilimkar wrote:
> On 10/20/2015 2:50 PM, Franklin S Cooper Jr wrote:
>> From: Franklin Cooper <fcooper@...com>
>>
>> Unlike other Keystone 2 devices, newer Keystone 2 SOCs may utilize
>> pinmuxing which requires PINCTRL to be enabled. Therefore, enable
>> PINCTRL for all Keystone 2 devices.
>>
>> Signed-off-by: Franklin S Cooper Jr <fcooper@...com>
>> ---
>> arch/arm/mach-keystone/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
> I would be happy to add this one when I see pin
> control data in DTS and its actually going to be
> used in upstream kernel. Till then I don't want
> to add this one.
>
Agree. It is too early to add the defconfig update and should be
deferred to when the DTS update is made. What if the newer keystone 2
SoC never end up in the tree?
Murali
> Regards,
> Santosh
>
--
Murali Karicheri
Linux Kernel, Keystone
--
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