From: Murali Karicheri <m-karicheri2@ti.com>
To: santosh shilimkar <santosh.shilimkar@oracle.com>,
Franklin S Cooper Jr <fcooper@ti.com>,
linux@arm.linux.org.uk, ssantosh@kernel.org,
ulf.hansson@linaro.org, grygorii.strashko@ti.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH 1/5] ARM: Keystone: Enable PINCTRL for Keystone ARCH
Date: Thu, 22 Oct 2015 10:18:48 -0400 [thread overview]
Message-ID: <5628F048.3000501@ti.com> (raw)
In-Reply-To: <5626E9BC.40300@oracle.com>
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@ti.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@ti.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
WARNING: multiple messages have this Message-ID (diff)
From: m-karicheri2@ti.com (Murali Karicheri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ARM: Keystone: Enable PINCTRL for Keystone ARCH
Date: Thu, 22 Oct 2015 10:18:48 -0400 [thread overview]
Message-ID: <5628F048.3000501@ti.com> (raw)
In-Reply-To: <5626E9BC.40300@oracle.com>
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@ti.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@ti.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
WARNING: multiple messages have this Message-ID (diff)
From: Murali Karicheri <m-karicheri2@ti.com>
To: santosh shilimkar <santosh.shilimkar@oracle.com>,
Franklin S Cooper Jr <fcooper@ti.com>, <linux@arm.linux.org.uk>,
<ssantosh@kernel.org>, <ulf.hansson@linaro.org>,
<grygorii.strashko@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 1/5] ARM: Keystone: Enable PINCTRL for Keystone ARCH
Date: Thu, 22 Oct 2015 10:18:48 -0400 [thread overview]
Message-ID: <5628F048.3000501@ti.com> (raw)
In-Reply-To: <5626E9BC.40300@oracle.com>
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@ti.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@ti.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
next prev parent reply other threads:[~2015-10-22 14:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 21:50 [PATCH 1/5] ARM: Keystone: Enable PINCTRL for Keystone ARCH Franklin S Cooper Jr
2015-10-20 21:50 ` Franklin S Cooper Jr
2015-10-20 21:50 ` [PATCH 2/5] mmc: omap_hsmmc: Enable omap_hsmmc for Keystone 2 Franklin S Cooper Jr
2015-10-20 21:50 ` Franklin S Cooper Jr
2015-10-21 1:25 ` santosh shilimkar
2015-10-21 1:25 ` santosh shilimkar
2015-10-22 9:28 ` Ulf Hansson
2015-10-22 9:28 ` Ulf Hansson
2015-10-22 10:58 ` Russell King - ARM Linux
2015-10-22 10:58 ` Russell King - ARM Linux
2015-10-22 13:32 ` Ulf Hansson
2015-10-22 13:32 ` Ulf Hansson
2015-10-20 21:50 ` [PATCH 3/5] ARM: keystone: defconfig: Enable PINCTRL SINGLE " Franklin S Cooper Jr
2015-10-20 21:50 ` Franklin S Cooper Jr
2015-10-20 21:50 ` [PATCH 4/5] ARM: keystone: defconfig: Enable MMC support Franklin S Cooper Jr
2015-10-20 21:50 ` Franklin S Cooper Jr
2015-10-21 1:27 ` santosh shilimkar
2015-10-21 1:27 ` santosh shilimkar
2015-10-20 21:50 ` [PATCH 5/5] ARM: keystone: defconfig: Enable CAN support Franklin S Cooper Jr
2015-10-20 21:50 ` Franklin S Cooper Jr
2015-10-21 1:28 ` santosh shilimkar
2015-10-21 1:28 ` santosh shilimkar
2015-10-21 1:26 ` [PATCH 1/5] ARM: Keystone: Enable PINCTRL for Keystone ARCH santosh shilimkar
2015-10-21 1:26 ` santosh shilimkar
2015-10-22 14:18 ` Murali Karicheri [this message]
2015-10-22 14:18 ` Murali Karicheri
2015-10-22 14:18 ` Murali Karicheri
2015-10-22 14:20 ` Murali Karicheri
2015-10-22 14:20 ` Murali Karicheri
2015-10-22 14:20 ` Murali Karicheri
-- strict thread matches above, loose matches on Subject: below --
2016-04-27 14:11 [PATCH 0/5] ARM:Keystone: Add pinmuxing support Franklin S Cooper Jr
2016-04-27 14:11 ` [PATCH 1/5] ARM: Keystone: Enable PINCTRL for Keystone ARCH Franklin S Cooper Jr
2016-04-27 14:11 ` Franklin S Cooper Jr
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=5628F048.3000501@ti.com \
--to=m-karicheri2@ti.com \
--cc=fcooper@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.org \
--cc=ulf.hansson@linaro.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 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.