From: Benoit Cousson <bcousson@baylibre.com>
To: Joel Fernandes <joelf@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
Devicetree Discuss <devicetree@vger.kernel.org>,
Linux OMAP List <linux-omap@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation List <linux-doc@vger.kernel.org>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Linux SPI Devel List <spi-devel-general@lists.sourceforge.net>
Subject: Re: [PATCH 0/3] ARM: dts: Enable EDMA, MMC and SPI on AM33XX for v3.13
Date: Tue, 10 Sep 2013 21:40:01 +0200 [thread overview]
Message-ID: <522F7591.6010409@baylibre.com> (raw)
In-Reply-To: <1378841079-15796-1-git-send-email-joelf@ti.com>
Hi Joel,
Thanks for the repost.
I'll applied that one now.
Regards,
Benoit
On 10/09/2013 21:24, Joel Fernandes wrote:
> Here are last few patches required to add EDMA and MMC/SPI support for AM33xx.
>
> Now that all dependent DMA patches and fixes are in linux next or mainline, except
> for [1] which should go in for 3.12 -rc cycle, it is safe to enable MMC and SPI support
> and this patch series enables it. These are originally Matt Porter's patches with
> changes to make it work with recent kernels, addition of irq, memory resources and
> enable other extra properties.
>
> These patches should cleanly apply on master branch after Koen's patch [2] for basic
> BBB DT support is applied.
>
> MMC support is enabled for: Beaglebone, AM335x EVM and EVM-SK boards. MMC support
> for BBB is intentionally not added due to custom fixes and other patches that are
> in Koen's tree and which will be separately submitted by him.
>
> [1] http://marc.info/?l=linux-omap&m=137883926226451&w=2
> [2] http://comments.gmane.org/gmane.linux.kernel.stable/63648
>
> Matt Porter (3):
> ARM: dts: add AM33XX EDMA support
> ARM: dts: add AM33XX SPI DMA support
> ARM: dts: add AM33XX MMC support and documentation
>
> .../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 26 +++++++++-
> arch/arm/boot/dts/am335x-bone.dts | 11 ++++
> arch/arm/boot/dts/am335x-evm.dts | 7 +++
> arch/arm/boot/dts/am335x-evmsk.dts | 7 +++
> arch/arm/boot/dts/am33xx.dtsi | 60 ++++++++++++++++++++++
> 5 files changed, 110 insertions(+), 1 deletion(-)
>
next prev parent reply other threads:[~2013-09-10 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 19:24 [PATCH 0/3] ARM: dts: Enable EDMA, MMC and SPI on AM33XX for v3.13 Joel Fernandes
2013-09-10 19:24 ` [PATCH 2/3] ARM: dts: add AM33XX SPI DMA support Joel Fernandes
[not found] ` <1378841079-15796-1-git-send-email-joelf-l0cyMroinI0@public.gmane.org>
2013-09-10 19:24 ` [PATCH 1/3] ARM: dts: add AM33XX EDMA support Joel Fernandes
2013-09-10 19:24 ` [PATCH 3/3] ARM: dts: add AM33XX MMC support and documentation Joel Fernandes
2013-09-10 19:39 ` [PATCH 0/3] ARM: dts: Enable EDMA, MMC and SPI on AM33XX for v3.13 Koen Kooi
2013-09-10 20:14 ` Joel Fernandes
2013-09-11 5:18 ` Koen Kooi
2013-09-11 6:00 ` Joel Fernandes
2013-09-11 6:06 ` Koen Kooi
2013-09-10 19:40 ` Benoit Cousson [this message]
2013-09-12 10:00 ` Mark Jackson
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=522F7591.6010409@baylibre.com \
--to=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=joelf@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=spi-devel-general@lists.sourceforge.net \
/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).