public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 1/4] configs: split ti_armv7_common into a omap generic header
Date: Fri, 17 Jul 2015 11:27:11 -0500	[thread overview]
Message-ID: <55A92CDF.9090708@ti.com> (raw)
In-Reply-To: <55A92182.1020501@ti.com>

On 07/17/2015 10:38 AM, Murali Karicheri wrote:
> On 07/16/2015 03:08 PM, Nishanth Menon wrote:

[...]

>>   /* MMC/SD IP block */
>>   #define CONFIG_MMC
>>   #define CONFIG_GENERIC_MMC
> 
> Why do we need MMC options in common? Only keystone device that uses MMC
> is Galileo. This should stay in individual device specific or
> board specific config file.

precisely why MMC is present in generic - lack of mmc is not consistent
in all ks2 devices as well - we can #undef if as necessary. I did miss
undefing it in patch #4 - I just did #undef CONFIG_SPL_MMC_SUPPORT

I can respin patch #4. with these added in.

> 
>> -#define CONFIG_OMAP_HSMMC
>>   #define CONFIG_CMD_MMC
> 
> Same here..
> 

ditto.

>>   /* GPIO block */
>> -#define CONFIG_OMAP_GPIO
>>   #define CONFIG_CMD_GPIO
> I believe currently keystone doesn't use GPIO, but this may change.
> Probably remove this as well for now and add it when GPIO is supported
> on K2.

patch #4:

+/* And no support for GPIO, yet.. */
+#undef CONFIG_SPL_GPIO_SUPPORT
+#undef CONFIG_CMD_GPIO


idea being to have as many common definitions as possible and undef the
ones we dont need as necessary. only thing i was careful here about was
to try and remove all OMAP specific defines out.

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2015-07-17 16:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 19:08 [U-Boot] [PATCH V2 0/4] configs: make keystone2 config to start using arm_v7_common header Nishanth Menon
2015-07-16 19:08 ` [U-Boot] [PATCH V2 1/4] configs: split ti_armv7_common into a omap generic header Nishanth Menon
2015-07-17 15:38   ` Murali Karicheri
2015-07-17 16:27     ` Nishanth Menon [this message]
2015-07-17 17:35       ` Murali Karicheri
2015-07-16 19:08 ` [U-Boot] [PATCH V2 2/4] board: ks2_evm: get rid of bogus CONFIG_LINUX_BOOT_PARAM_ADDR Nishanth Menon
2015-07-17 15:44   ` Murali Karicheri
2015-07-17 15:50     ` Vitaly Andrianov
2015-07-16 19:08 ` [U-Boot] [PATCH V2 3/4] configs: rename ks2_evm into ti_armv7_keystone2 Nishanth Menon
2015-07-17 15:42   ` Murali Karicheri
2015-07-17 15:49     ` Vitaly Andrianov
2015-07-16 19:08 ` [U-Boot] [PATCH V2 4/4] configs: ti_armv7_keystone2: start using armv7_common Nishanth Menon
2015-07-17 16:04   ` Murali Karicheri
2015-07-17 16:52     ` Nishanth Menon
2015-07-17 17:11       ` Murali Karicheri
2015-07-17 17:25         ` Nishanth Menon
2015-07-17 17:45           ` Murali Karicheri
2015-07-17 20:41             ` Tom Rini

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=55A92CDF.9090708@ti.com \
    --to=nm@ti.com \
    --cc=u-boot@lists.denx.de \
    /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