public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mcp23s08: add i2c support
Date: Fri, 15 Jul 2011 09:03:29 +0200	[thread overview]
Message-ID: <8762n4auv2.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110715025355.GX2927@ponder.secretlab.ca> (Grant Likely's message of "Thu, 14 Jul 2011 20:53:55 -0600")

>>>>> "Grant" == Grant Likely <grant.likely@secretlab.ca> writes:

 Grant> On Thu, Jul 14, 2011 at 09:59:28PM +0200, Peter Korsgaard wrote:
 >> Add i2c bindings for the mcp230xx devices. This is quite a lot simpler
 >> than the spi ones as there's no funky sub addressing done (one struct
 >> i2c_client per struct gpio_chip).
 >> 
 >> The mcp23s08_platform_data structure is reused for i2c, even though
 >> only a single mcp23s08_chip_info structure is needed.
 >> 
 >> To make the platform data bus independent, the setup/teardown prototypes
 >> are slightly changed, so the bus specific struct (spi_device / i2c_client)
 >> is passed as a void pointer instead.
 >> 
 >> There's no in-tree users of these callbacks.

 Grant> Why don't we just remove them then?  The notifier mechanism is more
 Grant> generic anyway.

Ok, will do.

 Grant> [...]
 >> @@ -537,9 +705,13 @@ static int __init mcp23s08_init(void)
 >> return ret;
 >> #endif /* CONFIG_SPI_MASTER */
 >> 
 >> +#ifdef CONFIG_I2C
 >> +	ret = i2c_add_driver(&mcp230xx_driver);
 >> +#endif /* CONFIG_I2C */
 >> +

 Grant> Need to unwind on failure to register, or put the i2c driver into a
 Grant> separate module so that each module gets it's own init/exit hooks.

Ok, will unwind.

Thanks for the quick review, will send an updated patch series shortly.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2011-07-15  7:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 19:59 [PATCH 0/3] gpio/mcp23s08: add support for i2c variants Peter Korsgaard
2011-07-14 19:59 ` [PATCH 1/3] mcp23s08: remove unused work queue Peter Korsgaard
2011-07-15  2:53   ` Grant Likely
2011-07-15  6:54     ` Peter Korsgaard
2011-07-14 19:59 ` [PATCH 2/3] mcp23s08: isolate spi specific parts Peter Korsgaard
2011-07-15  2:53   ` Grant Likely
2011-07-15  6:57     ` Peter Korsgaard
2011-07-14 19:59 ` [PATCH 3/3] mcp23s08: add i2c support Peter Korsgaard
2011-07-15  2:53   ` Grant Likely
2011-07-15  7:03     ` Peter Korsgaard [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=8762n4auv2.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --cc=grant.likely@secretlab.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox