linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jacmet@sunsite.dk (Peter Korsgaard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: let the core register devices from devicetree
Date: Thu, 14 Jun 2012 09:31:49 +0200	[thread overview]
Message-ID: <87ehpiwdqy.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1339622215-4733-1-git-send-email-w.sang@pengutronix.de> (Wolfram Sang's message of "Wed, 13 Jun 2012 23:12:10 +0200")

>>>>> "Wolfram" == Wolfram Sang <w.sang@pengutronix.de> writes:

 Wolfram> Currently, every driver has to do it on its own, but it should
 Wolfram> be done in the core, like we already do with board_info
 Wolfram> structs.

 Wolfram> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
 Wolfram> ---

 Wolfram> Based on v3.5-rc2. Only build tested, I don't have a OF based device
 Wolfram> around at the moment.

Neither have I, but it looks good.

Acked-by: Peter Korsgaard <jacmet@sunsite.dk>

 Wolfram> @Peter: Why does ocores do the device registration manually via
 Wolfram> platform_data instead of using board_info?

Because of dd14be4c274 (i2c-ocores: Can add I2C devices to the bus), a
patch I wasn't CC'ed on and haven't acked. I only noticed it later when
the I2C tree got merged into mainline.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2012-06-14  7:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 21:12 [PATCH] i2c: let the core register devices from devicetree Wolfram Sang
2012-06-13 21:33 ` Benjamin Herrenschmidt
2012-06-14  9:14   ` Wolfram Sang
2012-06-14 11:35     ` Benjamin Herrenschmidt
2012-06-13 22:03 ` Stephen Warren
2012-06-14  4:40 ` Grant Likely
2012-06-14  7:31 ` Peter Korsgaard [this message]
2012-06-14  7:53 ` viresh kumar
2012-06-14 10:28 ` Pawel Moll
2012-06-14 10:42 ` Jean Delvare
2012-06-14 17:29 ` Linus Walleij
2012-06-21  1:16 ` Barry Song

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=87ehpiwdqy.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).