From: Anatolij Gustschin <agust@denx.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, dzu@denx.de
Subject: Re: [PATCH 1/2] misc/eeprom: add driver for 93xx46 EEPROMs over GPIO
Date: Mon, 6 Jun 2011 10:00:45 +0200 [thread overview]
Message-ID: <20110606100045.3accb6e8@wker> (raw)
In-Reply-To: <4DDCCC82.90604@cam.ac.uk>
On Wed, 25 May 2011 10:31:46 +0100
Jonathan Cameron <jic23@cam.ac.uk> wrote:
> On 05/24/11 17:02, Anatolij Gustschin wrote:
> > 93xx46 EEPROMs can be connected using GPIO lines. Add a generic
> > 93xx46 EEPROM driver using common GPIO API for such configurations.
> > A platform is supposed to register appropriate 93xx46 gpio device
> > providing GPIO interface description and using this driver
> > read/write/erase access to the EEPROM chip can be easily done
> > over sysfs files.
> Could you explain why this makes more sense than an spi driver and
> use of spi_gpio ?
>
> It's microwire compatible according to random google provided datasheet,
> which iirc is a particular form of spi (half duplex, spi mode 0 according
> to wikipedia)
>
> That would give us a more generally useful driver.
Reworked the driver to be an spi driver using spi_gpio so
it is more generally useful driver now. spi_gpio driver
needs some fixes, though. I'll submit the new driver soon.
prev parent reply other threads:[~2011-06-06 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 16:02 [PATCH 1/2] misc/eeprom: add driver for 93xx46 EEPROMs over GPIO Anatolij Gustschin
2011-05-24 16:02 ` [PATCH 2/2] misc/eeprom: add eeprom access driver for digsy_mtc board Anatolij Gustschin
2011-05-25 9:31 ` [PATCH 1/2] misc/eeprom: add driver for 93xx46 EEPROMs over GPIO Jonathan Cameron
2011-05-25 13:35 ` Anatolij Gustschin
2011-05-25 14:07 ` Jonathan Cameron
2011-06-06 8:00 ` Anatolij Gustschin [this message]
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=20110606100045.3accb6e8@wker \
--to=agust@denx.de \
--cc=akpm@linux-foundation.org \
--cc=dzu@denx.de \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.