From: Huang Shijie <b32955@freescale.com>
To: grant.likely@linaro.org
Cc: rob.herring@calxeda.com, arnd@arndb.de,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, shawn.guo@linaro.org,
Huang Shijie <b32955@freescale.com>
Subject: [PATCH 0/6] ARM: imx6q{dl}: add the WEIM driver
Date: Mon, 20 May 2013 16:48:56 +0800 [thread overview]
Message-ID: <1369039742-10893-1-git-send-email-b32955@freescale.com> (raw)
This patch set adds a new driver for WEIM in the imx6q{dl}-sabreauto boards.
The WEIM(Wireless External Interface Module) works like a bus.
You can attach many different devices on it, such as NOR, onenand.
In the case of i.MX6q-sabreauto, only the NOR is connected to WEIM.
Huang Shijie (6):
drivers: bus: add a new driver for WEIM
ARM: dts: imx6q{dl}: fix the pin conflict between SPI and WEIM
ARM: dts: imx6qdl: add more information for WEIM
ARM: dts: imx6q: add pinctrl for WEIM NOR
ARM: dts: imx6ql: add a pinctrl for WEIM NOR
ARM: dts: imx6qdl: enable the WEIM NOR
Documentation/devicetree/bindings/bus/imx-weim.txt | 69 +++++++++
arch/arm/boot/dts/imx6dl-sabreauto.dts | 9 +-
arch/arm/boot/dts/imx6dl.dtsi | 57 ++++++++
arch/arm/boot/dts/imx6q-sabreauto.dts | 9 +-
arch/arm/boot/dts/imx6q.dtsi | 58 ++++++++
arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 23 +++-
arch/arm/boot/dts/imx6qdl.dtsi | 4 +-
drivers/bus/Kconfig | 9 ++
drivers/bus/Makefile | 1 +
drivers/bus/imx-weim.c | 145 ++++++++++++++++++++
10 files changed, 380 insertions(+), 4 deletions(-)
create mode 100644 Documentation/devicetree/bindings/bus/imx-weim.txt
create mode 100644 drivers/bus/imx-weim.c
next reply other threads:[~2013-05-20 8:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 8:48 Huang Shijie [this message]
2013-05-20 8:48 ` [PATCH 1/6] drivers: bus: add a new driver for WEIM Huang Shijie
[not found] ` <1369039742-10893-2-git-send-email-b32955-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-05-20 13:18 ` Sascha Hauer
[not found] ` <20130520131827.GB32299-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-05-22 8:30 ` Huang Shijie
2013-05-21 5:43 ` Shawn Guo
2013-05-22 8:16 ` Huang Shijie
[not found] ` <519C7ED3.3030004-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-05-22 12:59 ` Arnd Bergmann
[not found] ` <201305221459.34859.arnd-r2nGTMty4D4@public.gmane.org>
2013-05-23 2:17 ` Huang Shijie
[not found] ` <1369039742-10893-1-git-send-email-b32955-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-05-20 8:48 ` [PATCH 2/6] ARM: dts: imx6q{dl}: fix the pin conflict between SPI and WEIM Huang Shijie
[not found] ` <1369039742-10893-3-git-send-email-b32955-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-05-21 5:49 ` Shawn Guo
2013-05-21 5:53 ` Huang Shijie
2013-05-20 8:48 ` [PATCH 3/6] ARM: dts: imx6qdl: add more information for WEIM Huang Shijie
2013-05-20 8:49 ` [PATCH 4/6] ARM: dts: imx6q: add pinctrl for WEIM NOR Huang Shijie
2013-05-20 8:49 ` [PATCH 5/6] ARM: dts: imx6ql: add a " Huang Shijie
2013-05-20 8:49 ` [PATCH 6/6] ARM: dts: imx6qdl: enable the " Huang Shijie
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=1369039742-10893-1-git-send-email-b32955@freescale.com \
--to=b32955@freescale.com \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.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).