All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Viresh Kumar <viresh.kumar@st.com>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Tony Lindgren <tony@atomide.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Haojian Zhuang <haojian.zhuang@marvell.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	linux-i2c@vger.kernel.org, Kukjin Kim <kgene.kim@samsung.com>,
	Stephen Warren <swarren@nvidia.com>,
	Olof Johansson <olof@lixom.net>, Barry Song <21cnbao@gmail.com>,
	Jochen Friedrich <jochen@scram.de>,
	Deepak Sikri <deepak.sikri@st.com>, Li Yang <leoli@freescale.com>,
	Haavard Skinnemoen <hskinnemoen@gmail.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Vitaly Wool <vitalywool@gmail.com>,
	Wolfram Sang <wolfram@the-dreams.de>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Tang Yuantian <B29983@freescale.com>,
	"Jean Delvare (PC drivers, core)" <khali@linux-fr.org>,
	Magnus
Subject: Re: [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

WARNING: multiple messages have this Message-ID (diff)
From: Peter Korsgaard <jacmet@sunsite.dk>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Viresh Kumar <viresh.kumar@st.com>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Tony Lindgren <tony@atomide.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Haojian Zhuang <haojian.zhuang@marvell.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	linux-i2c@vger.kernel.org, Kukjin Kim <kgene.kim@samsung.com>,
	Stephen Warren <swarren@nvidia.com>,
	Olof Johansson <olof@lixom.net>, Barry Song <21cnbao@gmail.com>,
	Deepak Sikri <deepak.sikri@st.com>,
	Haavard Skinnemoen <hskinnemoen@gmail.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Wolfram Sang <wolfram@the-dreams.de>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Tang Yuantian <B29983@freescale.com>,
	"Jean Delvare \(PC drivers, core\)" <khali@linux-fr.org>,
	Magnus Damm <damm@opensource.se>,
	Lars-Peter Clausen <lars@metafoo.de>,
	"Ben Dooks \(embedded platforms\)" <ben-linux@fluff.org>,
	linux-arm-kernel@lists.infradead.org,
	Jiri Kosina <jkosina@suse.cz>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Karol Lewandowski <k.lewandowsk@samsung.com>,
	Dirk Brandewie <dirk.brandewie@gmail.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [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

WARNING: multiple messages have this Message-ID (diff)
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: 36+ 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:12 ` Wolfram Sang
2012-06-13 21:12 ` Wolfram Sang
2012-06-13 21:33 ` Benjamin Herrenschmidt
2012-06-13 21:33   ` Benjamin Herrenschmidt
2012-06-13 21:33   ` Benjamin Herrenschmidt
2012-06-14  9:14   ` Wolfram Sang
2012-06-14  9:14     ` Wolfram Sang
2012-06-14  9:14     ` Wolfram Sang
2012-06-14 11:35     ` Benjamin Herrenschmidt
2012-06-14 11:35       ` Benjamin Herrenschmidt
2012-06-14 11:35       ` Benjamin Herrenschmidt
2012-06-13 22:03 ` Stephen Warren
2012-06-13 22:03   ` Stephen Warren
2012-06-13 22:03   ` Stephen Warren
2012-06-14  4:40 ` Grant Likely
2012-06-14  4:40   ` Grant Likely
2012-06-14  4:40   ` Grant Likely
2012-06-14  7:31 ` Peter Korsgaard [this message]
2012-06-14  7:31   ` Peter Korsgaard
2012-06-14  7:31   ` Peter Korsgaard
2012-06-14  7:53 ` viresh kumar
2012-06-14  7:53   ` viresh kumar
2012-06-14  7:53   ` viresh kumar
2012-06-14 10:28 ` Pawel Moll
2012-06-14 10:28   ` Pawel Moll
2012-06-14 10:28   ` Pawel Moll
2012-06-14 10:42 ` Jean Delvare
2012-06-14 10:42   ` Jean Delvare
2012-06-14 10:42   ` Jean Delvare
2012-06-14 17:29 ` Linus Walleij
2012-06-14 17:29   ` Linus Walleij
2012-06-14 17:29   ` Linus Walleij
2012-06-21  1:16 ` Barry Song
2012-06-21  1:16   ` Barry Song
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=21cnbao@gmail.com \
    --cc=B29983@freescale.com \
    --cc=deepak.sikri@st.com \
    --cc=grant.likely@secretlab.ca \
    --cc=haojian.zhuang@marvell.com \
    --cc=hskinnemoen@gmail.com \
    --cc=jochen@scram.de \
    --cc=kgene.kim@samsung.com \
    --cc=khali@linux-fr.org \
    --cc=ldewangan@nvidia.com \
    --cc=leoli@freescale.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rusty@rustcorp.com.au \
    --cc=s.hauer@pengutronix.de \
    --cc=swarren@nvidia.com \
    --cc=tony@atomide.com \
    --cc=viresh.kumar@st.com \
    --cc=vitalywool@gmail.com \
    --cc=w.sang@pengutronix.de \
    --cc=wolfram@the-dreams.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 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.