From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Enric Balletbo i Serra <eballetbo@gmail.com>,
bcousson@baylibre.com, tomi.valkeinen@ti.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 03/11] ARM: dts: omap3-igep: Update to use the TI AM/DM37x processor.
Date: Sat, 16 Nov 2013 07:22:40 -0800 [thread overview]
Message-ID: <20131116152239.GK10317@atomide.com> (raw)
In-Reply-To: <52878D0F.7040204@collabora.co.uk>
* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [131116 07:21]:
> On 11/16/2013 03:44 PM, Tony Lindgren wrote:
> > * Javier Martinez Canillas <javier.martinez@collabora.co.uk> [131116 05:25]:
> >> From: Enric Balletbo i Serra <eballetbo@gmail.com>
> >>
> >> Most of the boards are using the TI AM/DM37x processor, there is only a small
> >> quantity of IGEP Processor Boards based on TI OMAP3530. So it's better use the
> >> omap36xx.dtsi include instead of omap34xx.dtsi include.
> >>
> >> To avoid confusion we have added to the model the (TI AM/DM37x) comment.
> >
> > You could have omap3-igep-common.dtsi that contains most configurations
> > and then files including that where only the SoC type and name is set.
> >
> > Regards,
> >
> > Tony
> >
>
> Hi Tony,
>
> We do have a common DTSI file for IGEP boards which is
> arch/arm/boot/dts/omap3-igep.dtsi. Maybe it should be renamed to -common to make
> it more clear?
No that's fine.
> Anyways, there are two models OMAP3 based IGEP boards that include this common
> DTSI: IGEPv2 (omap3-igep0020.dts) and IGEP COM Module (omap3-igep0030.dts).
>
> However there are different revisions for each model with variations of the SoC
> version used (AM/DM37x or OMAP3530), with wifi or not wifi, flash memory
> technology (NAND or OneNAND) and different flash memory sizes.
>
> So, we don't plan to support every single variation on mainline since this will
> unnecessary increase the complexity of DTS adding not much benefit.
>
> We just prefer to support the latter and most popular revision for each model
> which is AM/DM37x SoC, wifi, 512 MB NAND flash.
>
> Users that have a less popular revision can modify the reference DTS in mainline
> to reflect their board.
OK sounds fine to me and can be revisited if needed naturally.
Regards,
Tony
next prev parent reply other threads:[~2013-11-16 15:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 13:23 [PATCH 00/11]: add remaining support for IGEP boards Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 01/11] ARM: dts: omap3-igep: Fix bus-width for mmc1 Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 02/11] ARM: dts: omap3-igep: Add support for LBEE1USJYC WiFi connected to SDIO Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 03/11] ARM: dts: omap3-igep: Update to use the TI AM/DM37x processor Javier Martinez Canillas
2013-11-16 14:44 ` Tony Lindgren
2013-11-16 15:19 ` Javier Martinez Canillas
2013-11-16 15:22 ` Tony Lindgren [this message]
2013-11-16 13:23 ` [PATCH 04/11] ARM: dts: omap3-igep0020: Add pinmux setup for i2c devices Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 05/11] ARM: dts: omap3-igep0020: Add pinmuxing for DVI output Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 06/11] ARM: dts: AM33XX BASE0033: add pinmux and hdmi node to enable display Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 07/11] ARM: dts: AM33XX BASE0033: add pinmux and user led support Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 08/11] ARM: dts: AM33XX BASE0033: add 32KBit EEPROM support Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 09/11] ARM: dts: AM33XX IGEP0033: add USB support Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 10/11] ARM: OMAP: dss-common: change IGEP's DVI DDC i2c bus Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 11/11] OMAPDSS: DPI: use VPLL2 regulator if VDDS_DSI is not found Javier Martinez Canillas
2013-11-16 14:18 ` Tony Lindgren
2013-11-16 15:34 ` Javier Martinez Canillas
2013-11-16 15:45 ` Tony Lindgren
2013-11-16 16:02 ` Sebastian Reichel
2013-11-16 17:28 ` Javier Martinez Canillas
2013-11-17 0:26 ` Sebastian Reichel
2013-11-17 1:06 ` Javier Martinez Canillas
2013-11-16 14:16 ` [PATCH 00/11]: add remaining support for IGEP boards Tony Lindgren
2013-11-16 14:41 ` Javier Martinez Canillas
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=20131116152239.GK10317@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=eballetbo@gmail.com \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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).