From: Joel Fernandes <joelf@ti.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Benoit Cousson <bcousson@baylibre.com>,
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 15:14:56 -0500 [thread overview]
Message-ID: <522F7DC0.7030603@ti.com> (raw)
In-Reply-To: <5EB8AE91-A996-4CF1-86B7-C8FDEC177E89@dominion.thruhere.net>
On 09/10/2013 02:39 PM, Koen Kooi wrote:
>
> Op 10 sep. 2013, om 21:24 heeft Joel Fernandes <joelf@ti.com> het volgende geschreven:
>
>> 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.
>
> Correct, but your patches for MMC support on BBW are missing the card detect entries to make it hotplug work.
I thought it was determined that this would be submitted by you separately after
rebasing as we discussed [1] and [2].
[1] https://lkml.org/lkml/2013/9/6/183
[2] http://marc.info/?l=linux-omap&m=137879246709612&w=2
Regards,
-Joel
WARNING: multiple messages have this Message-ID (diff)
From: joelf@ti.com (Joel Fernandes)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: dts: Enable EDMA, MMC and SPI on AM33XX for v3.13
Date: Tue, 10 Sep 2013 15:14:56 -0500 [thread overview]
Message-ID: <522F7DC0.7030603@ti.com> (raw)
In-Reply-To: <5EB8AE91-A996-4CF1-86B7-C8FDEC177E89@dominion.thruhere.net>
On 09/10/2013 02:39 PM, Koen Kooi wrote:
>
> Op 10 sep. 2013, om 21:24 heeft Joel Fernandes <joelf@ti.com> het volgende geschreven:
>
>> 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.
>
> Correct, but your patches for MMC support on BBW are missing the card detect entries to make it hotplug work.
I thought it was determined that this would be submitted by you separately after
rebasing as we discussed [1] and [2].
[1] https://lkml.org/lkml/2013/9/6/183
[2] http://marc.info/?l=linux-omap&m=137879246709612&w=2
Regards,
-Joel
next prev parent reply other threads:[~2013-09-10 20:14 UTC|newest]
Thread overview: 27+ 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 ` 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 ` Joel Fernandes
2013-09-10 19:24 ` Joel Fernandes
2013-09-10 19:24 ` Joel Fernandes
2013-09-10 19:24 ` [PATCH 3/3] ARM: dts: add AM33XX MMC support and documentation Joel Fernandes
2013-09-10 19:24 ` Joel Fernandes
2013-09-10 19:24 ` Joel Fernandes
2013-09-10 19:24 ` Joel Fernandes
2013-09-10 19:24 ` [PATCH 2/3] ARM: dts: add AM33XX SPI DMA support Joel Fernandes
2013-09-10 19:24 ` 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 19:39 ` Koen Kooi
2013-09-10 20:14 ` Joel Fernandes [this message]
2013-09-10 20:14 ` Joel Fernandes
2013-09-11 5:18 ` Koen Kooi
2013-09-11 5:18 ` Koen Kooi
2013-09-11 6:00 ` Joel Fernandes
2013-09-11 6:00 ` Joel Fernandes
2013-09-11 6:00 ` Joel Fernandes
2013-09-11 6:06 ` Koen Kooi
2013-09-11 6:06 ` Koen Kooi
2013-09-10 19:40 ` Benoit Cousson
2013-09-10 19:40 ` Benoit Cousson
2013-09-12 10:00 ` Mark Jackson
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=522F7DC0.7030603@ti.com \
--to=joelf@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=koen@dominion.thruhere.net \
--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 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.