public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] Add support for PCA953x I2C gpio devices
Date: Tue, 18 Nov 2008 15:51:15 -0600	[thread overview]
Message-ID: <1227045075.3065.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20081118213322.E5003832E89D@gemini.denx.de>

Hi Wolfgang,

On Tue, 2008-11-18 at 22:33 +0100, Wolfgang Denk wrote:
> Dear Peter Tyser,
> 
> In message <1224800639-31350-2-git-send-email-ptyser@xes-inc.com> you wrote:
> > Initial support for NXP's 4 and 8 bit I2C gpio expanders
> > (eg pca9537, pca9557, etc). The CONFIG_PCA953X define
> > enables support for the devices while the CONFIG_CMD_PCA953X
> > define enables the pca953x command.
> 
> I'm not sure if we need such a detailed  level  of  access  to  these
> chips.  We  already  have  a  couple of similar I/O expanders in some
> boards, for example implemente in some PICs. See for example the "pic
> read" / "pic write" conde in board/lwmon/lwmon.c etc.
> 
> I think we should generalize this - and more than read / write isn't
> really needed, or is it?

What do you mean by "we should generalize this"?

I view the read/write/invert commands as necessary to easily
configure/read/write the GPIO pins, and the info command is nice, but
not necessary.

The info command is nice to get an idea of what's going on at a high
level - eg is the input on pin 2 being inverted?  What pins are
currently being driven low? etc.  I've found the iopinfo command useful
for the 82xx boards and tried to replicate similar functionality in this
driver.  I like the info command but understand if others want it
removed.

Let me know if you'd like me to change it.

Thanks,
Peter

  reply	other threads:[~2008-11-18 21:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 22:23 [U-Boot] [PATCH 0/3] Support for XPedite5370 and misc GPIO Peter Tyser
2008-10-23 22:23 ` [U-Boot] [PATCH 1/3] Add support for PCA953x I2C gpio devices Peter Tyser
2008-10-23 22:23   ` [U-Boot] [PATCH 2/3] Add support for Maxim's DS4510 I2C device Peter Tyser
2008-10-23 22:23     ` [U-Boot] [PATCH 3/3] XPedite5370 board support Peter Tyser
2008-10-24 23:21       ` Andy Fleming
2008-10-25  0:30         ` Peter Tyser
2008-11-18 21:44       ` Wolfgang Denk
2008-11-18 22:13         ` Peter Tyser
2008-11-18 22:20           ` Wolfgang Denk
2008-11-18 22:39             ` Peter Tyser
2008-11-18 23:03               ` Wolfgang Denk
2008-11-19 17:29               ` Jon Loeliger
2008-11-19 18:00                 ` Peter Tyser
2008-11-18 21:37     ` [U-Boot] [PATCH 2/3] Add support for Maxim's DS4510 I2C device Wolfgang Denk
2008-11-18 21:57       ` Peter Tyser
2008-11-18 23:16         ` Wolfgang Denk
2008-11-18 21:33   ` [U-Boot] [PATCH 1/3] Add support for PCA953x I2C gpio devices Wolfgang Denk
2008-11-18 21:51     ` Peter Tyser [this message]
2008-11-18 23:11       ` Wolfgang Denk
2008-11-18 21:29 ` [U-Boot] [PATCH 0/3] Support for XPedite5370 and misc GPIO Wolfgang Denk

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=1227045075.3065.25.camel@localhost.localdomain \
    --to=ptyser@xes-inc.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