From: Nishanth Menon <nm@ti.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: b-cousson@ti.com, tony@atomide.com, benoit.cousson@linaro.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH v2] ARM: DTS: OMAP4: Add OMAP4 Blaze Tablet support
Date: Tue, 25 Jun 2013 07:43:02 -0500 [thread overview]
Message-ID: <51C99056.5090104@ti.com> (raw)
In-Reply-To: <51C9867C.80206@ti.com>
On 06/25/2013 07:01 AM, Nishanth Menon wrote:
> On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
>> The OMAP4 Blaze Tablet is TI OMAP4 processor-based
>> development platform in a tablet formfactor.
>> The platform contains many of the features found in
>> present-day handsets (such as audio, video, wireless
>> functions and user interfaces) and in addition
>> contains features for software development and test.
>>
>> This patch adds initial support for the OMAP4 Blaze
>> Tablet development platform. Additional functionality
>> depends on different drivers and code modifications that
>> are not upstreamed yet or do not support DT yet, so will
>> be added later.
>
> http://svtronics.com/omap/sevm4460,blaze,omap might help too :)
> [...]
>> +
>> +#include "twl6030.dtsi"
>> +
> Might be good to see the TWL interrupt pin information made available as
> well?
Allow me to rephrase a comment a little bit more :)
Similar to twl4030_omap3.dtsi, we could introduce twl6030_omap4.dtsi.
this could contain the common pins used for 6030.
&omap4_pmx_wkup {
pinctrl-names = "default";
pinctrl-0 = <
&twl6030_wkup_pins
>;
twl6030_wkup_pins: pinmux_twl6030_wkup_pins {
pinctrl-single,pins = <
0x14 (PIN_OUTPUT | MUX_MODE2)
>;
};
};
twl6030_pins: pinmux_twl6030_pins {
pinctrl-single,pins = <
0x15e (WAKEUP_EN | PIN_INPUT_PULLUP | MUX_MODE0) /*
sys_nirq1.sys_nirq1 */
>;
};
which is now already duplicated in 2 places (SDP and Panda), and in this
patch duplicated again.
just my 2 cents :(
---
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: <b-cousson@ti.com>, <tony@atomide.com>,
<benoit.cousson@linaro.org>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>,
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH v2] ARM: DTS: OMAP4: Add OMAP4 Blaze Tablet support
Date: Tue, 25 Jun 2013 07:43:02 -0500 [thread overview]
Message-ID: <51C99056.5090104@ti.com> (raw)
In-Reply-To: <51C9867C.80206@ti.com>
On 06/25/2013 07:01 AM, Nishanth Menon wrote:
> On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
>> The OMAP4 Blaze Tablet is TI OMAP4 processor-based
>> development platform in a tablet formfactor.
>> The platform contains many of the features found in
>> present-day handsets (such as audio, video, wireless
>> functions and user interfaces) and in addition
>> contains features for software development and test.
>>
>> This patch adds initial support for the OMAP4 Blaze
>> Tablet development platform. Additional functionality
>> depends on different drivers and code modifications that
>> are not upstreamed yet or do not support DT yet, so will
>> be added later.
>
> http://svtronics.com/omap/sevm4460,blaze,omap might help too :)
> [...]
>> +
>> +#include "twl6030.dtsi"
>> +
> Might be good to see the TWL interrupt pin information made available as
> well?
Allow me to rephrase a comment a little bit more :)
Similar to twl4030_omap3.dtsi, we could introduce twl6030_omap4.dtsi.
this could contain the common pins used for 6030.
&omap4_pmx_wkup {
pinctrl-names = "default";
pinctrl-0 = <
&twl6030_wkup_pins
>;
twl6030_wkup_pins: pinmux_twl6030_wkup_pins {
pinctrl-single,pins = <
0x14 (PIN_OUTPUT | MUX_MODE2)
>;
};
};
twl6030_pins: pinmux_twl6030_pins {
pinctrl-single,pins = <
0x15e (WAKEUP_EN | PIN_INPUT_PULLUP | MUX_MODE0) /*
sys_nirq1.sys_nirq1 */
>;
};
which is now already duplicated in 2 places (SDP and Panda), and in this
patch duplicated again.
just my 2 cents :(
---
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-06-25 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 11:32 [PATCH v2] ARM: DTS: OMAP4: Add OMAP4 Blaze Tablet support Ruslan Bilovol
2013-06-25 12:01 ` Nishanth Menon
2013-06-25 12:01 ` Nishanth Menon
2013-06-25 12:43 ` Nishanth Menon [this message]
2013-06-25 12:43 ` Nishanth Menon
2013-06-26 8:03 ` Ruslan Bilovol
2013-06-26 13:13 ` Nishanth Menon
2013-06-27 18:45 ` Ruslan Bilovol
2013-06-25 14:07 ` Dan Murphy
2013-06-25 14:07 ` Dan Murphy
2013-06-26 6:27 ` Tony Lindgren
2013-06-26 8:21 ` Ruslan Bilovol
2013-06-28 7:58 ` Tomi Valkeinen
2013-07-19 11:55 ` Ruslan Bilovol
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=51C99056.5090104@ti.com \
--to=nm@ti.com \
--cc=b-cousson@ti.com \
--cc=benoit.cousson@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ruslan.bilovol@ti.com \
--cc=tony@atomide.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.