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 3/5] ARM: omap-common: Add standard access for board description EEPROM
Date: Tue, 3 Nov 2015 10:11:21 -0600	[thread overview]
Message-ID: <5638DCA9.7030501@ti.com> (raw)
In-Reply-To: <20151103160721.GD8499@bill-the-cat>

On 11/03/2015 10:07 AM, Tom Rini wrote:
[...]
>>>>> > >>> +obj-$(CONFIG_I2C) += ti-i2c-eeprom.o
>>>> > >>
>>>> > >> This makes this module compile on all TI SoC based boards enabling I2C.
>>>> > >> AFAIU, this is a separate chip (not inside the SoC), so this module will
>>>> > >> also compile on non-TI boards that do not have this EEPROM.
>>>> > >> I think, it should be more fine grained (e.g. have its own symbol).
>>>> > >>
>>> > > Can you give a suggestion?
>> > 
>> > Are you sure this will be built into non-ti SoCs with I2C enabled if you
>> > are not using the function? I assume  __maybe_unused should take care of
>> > that, no - let the compiler do the gc anyways?
> The gc should work, yes.  But this is also TI-centric code and should
> end up in board/ti/ similar to how the Siemens AM335x EEPROM code is
> under board/siemens/ because they didn't re-use the TI format :)

aaah - Nice! a board/ti/common folder for generic stuff like these does
indeed sound like the right solution to me. at least that should prevent
cruft that crept into am437x basically duplicating am335x eeprom data
all over again.


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2015-11-03 16:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 12:22 [U-Boot] [PATCH v2 0/5] ARM: omap-common: Add board detection support for TI EVMs Steve Kipisz
2015-11-03 12:22 ` [U-Boot] [PATCH v2 1/5] ARM: OMAP4/5: Centralize early clock initialization Steve Kipisz
2015-11-03 16:07   ` Tom Rini
2015-11-04  8:32   ` Lokesh Vutla
2015-11-04 14:54     ` Steven Kipisz
2015-11-03 12:22 ` [U-Boot] [PATCH v2 2/5] ARM: OMAP4/5: Centralize gpi2c_init Steve Kipisz
2015-11-03 16:07   ` Tom Rini
2015-11-03 12:22 ` [U-Boot] [PATCH v2 3/5] ARM: omap-common: Add standard access for board description EEPROM Steve Kipisz
2015-11-03 13:16   ` Igor Grinberg
2015-11-03 15:13     ` Steven Kipisz
2015-11-03 15:26       ` Nishanth Menon
2015-11-03 16:07         ` Tom Rini
2015-11-03 16:11           ` Nishanth Menon [this message]
2015-11-03 17:02         ` Igor Grinberg
2015-11-03 17:45           ` Nishanth Menon
2015-11-03 21:07             ` Igor Grinberg
2015-11-03 21:13               ` Nishanth Menon
2015-11-03 12:22 ` [U-Boot] [PATCH v2 4/5] ARM: OMAP4/5: Add generic board detection hook Steve Kipisz
2015-11-03 16:07   ` Tom Rini
2015-11-03 12:22 ` [U-Boot] [PATCH v2 5/5] board: ti: AM57xx: Add detection logic for AM57xx-evm Steve Kipisz
2015-11-03 13:29   ` Igor Grinberg
2015-11-03 15:09     ` Steven Kipisz
2015-11-03 17:04       ` Igor Grinberg
2015-11-03 15:31   ` Nishanth Menon
2015-11-03 15:36     ` Steven Kipisz

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=5638DCA9.7030501@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