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] [PATCHv3] pca953x: support 16-pin devices
Date: Thu, 09 Dec 2010 11:08:25 -0600	[thread overview]
Message-ID: <1291914505.20072.911.camel@petert> (raw)
In-Reply-To: <AANLkTikUnaZ=hXiwW4QnGQCQy-m5=86DrMPGq=eWy22G@mail.gmail.com>

On Thu, 2010-12-09 at 22:11 +1300, Chris Packham wrote:
> This adds support for for the PCA9535/PCA9539 family of gpio devices which
> have 16 output pins.
> 
> To let the driver know which devices are 16-pin it is necessary to define
> CONFIG_SYS_I2C_PCA953X_WIDTH in your board config file. This is used to
> create an array of {chip, ngpio} tuples that are used to determine the
> width of a particular chip. For backwards compatibility it is assumed that
> any chip not defined in CONFIG_SYS_I2C_PCA953X_WIDTH has 8 pins.
> 
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>

Looks good to me and works as advertised.

Acked-by: Peter Tyser <ptyser@xes-inc.com>
Tested-by: Peter Tyser <ptyser@xes-inc.com>

  reply	other threads:[~2010-12-09 17:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 22:00 [U-Boot] [PATCHv2] pca953x: support 16-pin devices Chris Packham
2010-12-09  0:08 ` Peter Tyser
2010-12-09  4:40   ` Chris Packham
2010-12-09  9:11     ` [U-Boot] [PATCHv3] " Chris Packham
2010-12-09 17:08       ` Peter Tyser [this message]
2010-12-15  2:49         ` Chris Packham
2010-12-18 23:26           ` Wolfgang Denk
2010-12-19 20:12             ` [U-Boot] [PATCHv4] " Chris Packham
2011-01-10  7:02               ` [U-Boot] [U-Boot,PATCHv4] " Heiko Schocher
2011-01-13  4:02                 ` Chris Packham
2011-01-13  6:08                   ` Peter Tyser

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=1291914505.20072.911.camel@petert \
    --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