From: Igor Grinberg <grinberg@compulab.co.il>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Ilya Yanok <yanok@emcraft.com>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, sasha_d@emcraft.com
Subject: Re: [PATCH 1/2] mt_ventoux: very basic support for TeeJet Mt.Ventoux board
Date: Thu, 05 Jan 2012 10:40:21 +0200 [thread overview]
Message-ID: <4F0561F5.4020700@compulab.co.il> (raw)
In-Reply-To: <20120104195412.GG15503@ponder.secretlab.ca>
Hi Grant,
On 01/04/12 21:54, Grant Likely wrote:
> On Tue, Dec 27, 2011 at 12:08:31AM +0100, Ilya Yanok wrote:
>> Very basic support for TeeJet Mt.Ventoux board. Able to boot via
>> board-generic and ramdisk/initramfs, however most of peripherals are
>> not supported. Produces tons of twl4030 related errors as this board
>> doesn't have twl4030 installed.
>>
>> Signed-off-by: Ilya Yanok <yanok@emcraft.com>
>
> Comment below, but otherwise:
>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
Though nothing fundamentally different in regard to DT, but
there is a v3 of this patch set available at [1]
>
>> ---
>> arch/arm/boot/dts/am3517_mt_ventoux.dts | 27 +++++++++++++++++++++++++++
>> 1 files changed, 27 insertions(+), 0 deletions(-)
>> create mode 100644 arch/arm/boot/dts/am3517_mt_ventoux.dts
>>
>> diff --git a/arch/arm/boot/dts/am3517_mt_ventoux.dts b/arch/arm/boot/dts/am3517_mt_ventoux.dts
>> new file mode 100644
>> index 0000000..5eb26d7
>> --- /dev/null
>> +++ b/arch/arm/boot/dts/am3517_mt_ventoux.dts
>> @@ -0,0 +1,27 @@
>> +/*
>> + * Copyright (C) 2011 Ilya Yanok, EmCraft Systems
>> + *
>> + * This program is free software; you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public License version 2 as
>> + * published by the Free Software Foundation.
>> + */
>> +/dts-v1/;
>> +
>> +/include/ "omap3.dtsi"
>> +
>> +/ {
>> + model = "TeeJet Mt.Ventoux";
>> + compatible = "teejet,mt_ventoux", "ti,omap3";
>> +
>> + memory {
>> + device_type = "memory";
>> + reg = <0x80000000 0x10000000>; /* 256 MB */
>> + };
>> +
>> + /* AM35xx doesn't have IVA */
>
> Perhaps the AM35xx should have a separate .dtsi file?
In that case there is a possibility you will get multiple
<SoC>.dtsi files with the same copy/pasted "disable" stuff.
Of course this is better than having multiple board files doing this.
What do you think on splitting the whole thing into <IP>.dtsi files,
Like I have explained here [2]?
>
>> + soc {
>> + iva {
>> + status = "disabled";
>> + };
>> + };
>> +};
[1] http://www.spinics.net/lists/linux-omap/msg62185.html
[2] http://www.spinics.net/lists/linux-omap/msg61975.html
--
Regards,
Igor.
next prev parent reply other threads:[~2012-01-05 8:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 23:08 [PATCH 0/2] Support for TeeJet Mt.Ventoux Ilya Yanok
2011-12-26 23:08 ` [PATCH 1/2] mt_ventoux: very basic support for TeeJet Mt.Ventoux board Ilya Yanok
2012-01-04 19:54 ` Grant Likely
2012-01-05 8:40 ` Igor Grinberg [this message]
2011-12-26 23:08 ` [PATCH 2/2] mt_ventoux: " Ilya Yanok
2011-12-27 7:56 ` Igor Grinberg
2011-12-27 23:02 ` Ilya Yanok
2012-01-03 9:48 ` Igor Grinberg
2012-01-11 20:04 ` Ilya Yanok
2011-12-27 23:09 ` [PATCH V2] " Ilya Yanok
2012-02-01 10:51 ` Stefano Babic
2012-03-05 21:46 ` Tony Lindgren
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=4F0561F5.4020700@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=sasha_d@emcraft.com \
--cc=yanok@emcraft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).