From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] misc/at24: Add at24c512b eeprom support
Date: Wed, 23 Jan 2013 15:14:45 +0100 [thread overview]
Message-ID: <20130123141445.GA2758@pengutronix.de> (raw)
In-Reply-To: <CA+8Hj83n+pC+a6bYOOH1b61DTqSjpKsxyKDgDL2pCRKxTq4EXg@mail.gmail.com>
> The names of the two entries are not the same, one is "24c512", the
> other is "24c512b".
I do understand that. There are TONS of 24c512 variants out there.
> My original idea to add the new entry is to count on the name
> difference to do different system reset operations.
Your devicetree may have both names, but at24 doesn't need it since
there is no code involved handling the difference.
> The commit message of the patch which adds 24c32 support for MX28EVK
> tells that "mx28evk has a free slot U50 that can be used to populate
> an I2C EEPROM.".
I do know that, too. You can put other things there, too. But well, not
worth the hazzle...
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130123/f1167045/attachment.sig>
next prev parent reply other threads:[~2013-01-23 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 6:32 [PATCH 1/2] misc/at24: Add at24c512b eeprom support Liu Ying
2013-01-23 6:32 ` [PATCH 2/2] ARM: dts: imx51-babbage: " Liu Ying
2013-01-23 7:30 ` Sascha Hauer
2013-01-23 7:51 ` Liu Ying
2013-01-23 7:55 ` Sascha Hauer
2013-01-23 7:59 ` Liu Ying
2013-01-23 12:24 ` [PATCH 1/2] misc/at24: " Linus Walleij
2013-01-23 12:50 ` Wolfram Sang
2013-01-23 13:40 ` Liu Ying
2013-01-23 13:49 ` Wolfram Sang
2013-01-23 14:08 ` Liu Ying
2013-01-23 14:14 ` Wolfram Sang [this message]
2013-01-23 14:23 ` Liu Ying
2013-01-24 14:41 ` Linus Walleij
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=20130123141445.GA2758@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).