From: Alessandro Rubini <rubini@gnudd.com>
To: linux-kernel@vger.kernel.org
Cc: Giancarlo Asnaghi <giancarlo.asnaghi@st.com>,
Alan Cox <alan@linux.intel.com>,
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
STEricsson_nomadik_linux@list.st.com,
Linus Walleij <linus.walleij@stericsson.com>,
Russell King <linux@arm.linux.org.uk>,
Jean Delvare <khali@linux-fr.org>,
Wolfram Sang <w.sang@pengutronix.de>,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>
Subject: [PATCH V2 0/3] i2c-nomadik changes
Date: Thu, 7 Jun 2012 15:52:24 +0200 [thread overview]
Message-ID: <cover.1339076448.git.rubini@gnudd.com> (raw)
V2:
- use linux/platform_data/i2c-nomadik.h not linux/i2c-nomadik.h
- format patch with -M
- added lee jones to the Cc: list (for device tree support)
- minor rewording of the commit messages
Slightly edited for typos explanation, otherwise same as V1:
The patch set turns a platform device into an amba device. Its users,
i.e. mach-ux500, are converted too. The set has no external
dependencies, although is has no visible effect until other patches
are accepted.
Reasoning:
In the STA2X11 I/O hub we are exporting a number of AMBA peripherals
to the PCI world. By using a generic pci-amba driver there is no further
code for each device, provided they are already registered under the
AMBA bus. I already submitted the generic bridge and I'm waiting for
feedback on it (https://lkml.org/lkml/2012/5/28/194).
Status of this patch set:
The users of the driver (i.e. mach-ux500) compile properly, but I
couldn't test on any board. The driver, as is, works on x86 under the
PCI bridge, with the not-yet-upstream clock framework and platform
data for sta2x11 devices. However, this set is not introducing any
dead code as it only adds more flexibility. Most of the patch is
just two renames: s/platform_device/amba_device/ and s/pdev/adev/ .
Alessandro Rubini (3):
i2c-nomadik: move header to <linux/platform_data/i2c-nomadik.h>
i2c-nomadik: turn the platform driver to an amba driver
i2c-nomadik: depend on ARM_AMBA, not PLAT_NOMADIK
arch/arm/mach-ux500/board-mop500.c | 2 +-
arch/arm/mach-ux500/devices-common.h | 23 +---
drivers/i2c/busses/Kconfig | 5 +-
drivers/i2c/busses/i2c-nomadik.c | 140 ++++++++++----------
.../linux/platform_data/i2c-nomadik.h | 6 +-
5 files changed, 80 insertions(+), 96 deletions(-)
rename arch/arm/plat-nomadik/include/plat/i2c.h => include/linux/platform_data/i2c-nomadik.h (91%)
--
1.7.7.2
next reply other threads:[~2012-06-07 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 13:52 Alessandro Rubini [this message]
2012-06-07 13:52 ` [PATCH V2 1/3] i2c-nomadik: move header to <linux/platform_data/i2c-nomadik.h> Alessandro Rubini
2012-06-07 13:52 ` [PATCH V2 2/3] i2c-nomadik: turn the platform driver to an amba driver Alessandro Rubini
2012-06-08 17:09 ` Linus Walleij
2012-06-07 13:53 ` [PATCH V2 3/3] i2c-nomadik: depend on ARM_AMBA, not PLAT_NOMADIK Alessandro Rubini
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=cover.1339076448.git.rubini@gnudd.com \
--to=rubini@gnudd.com \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=alan@linux.intel.com \
--cc=giancarlo.asnaghi@st.com \
--cc=khali@linux-fr.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=srinidhi.kasagar@stericsson.com \
--cc=w.sang@pengutronix.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