From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] common/i2c: Add i2c write command
Date: Mon, 17 Sep 2012 22:57:54 -0500 [thread overview]
Message-ID: <5057F142.80001@freescale.com> (raw)
In-Reply-To: <20120917233643.GC17195@bill-the-cat>
On 09/17/2012 06:36 PM, Tom Rini wrote:
> On Mon, Sep 17, 2012 at 11:29:00PM +0000, sun york-R58495 wrote:
>
>> Tom,
>>
>> It's like eeprom write but it writes to general devices, not specificly to system eeprom. I would have to use i2c mw command a lot without this.
>
> Right. I guess what I'm getting at is, are you writing to some sort
> of other device or writing bits to storage attached to i2c? Does it
> really not make sense to just use 'eeprom write' even if it's not
> technically for The System EEPROM but rather some storage (or a number
> of storage chips) attached via i2c?
>
> I'm not objecting to i2c write mind you, I was wishing for something
> like this when I stumbled on CONFIG_CMD_EEPROM which did what I needed.
>
Tom,
I have a case under debugging where I need to use i2c write to devices.
One device (EEPROM) has two-byte address length and most others
(including other EEPROMs) have one byte address length. I also have
other non-storage devices but I wouldn't use "i2c write" because "i2c
mw" will be sufficient. eeprom command has its limitation for the case
of variable device address and variable address length.
York
next prev parent reply other threads:[~2012-09-18 3:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 18:02 [U-Boot] [PATCH] common/i2c: Add i2c write command York Sun
2012-09-17 22:16 ` Tom Rini
2012-09-17 23:29 ` sun york-R58495
2012-09-17 23:36 ` Tom Rini
2012-09-18 3:57 ` York Sun [this message]
2012-09-25 19:59 ` York Sun
2012-09-25 20:21 ` Tom Rini
2012-09-27 5:47 ` Heiko Schocher
2012-10-16 3:57 ` Heiko Schocher
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=5057F142.80001@freescale.com \
--to=yorksun@freescale.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