From: Sekhar Nori <nsekhar@ti.com>
To: Faiz Abbas <faiz_abbas@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-mmc@vger.kernel.org>
Cc: nm@ti.com, ulf.hansson@linaro.org, robh+dt@kernel.org,
adrian.hunter@intel.com
Subject: Re: [PATCH 0/4] Add Support for MMC in J721E
Date: Tue, 4 Jun 2019 11:48:55 +0530 [thread overview]
Message-ID: <2f45cef2-c4ca-0404-b205-fabbb92a40fb@ti.com> (raw)
In-Reply-To: <20190604060914.10886-1-faiz_abbas@ti.com>
On 04/06/19 11:39 AM, Faiz Abbas wrote:
> The following patches add driver support for MMC SDHCI interfaces on
> TI's J721E devices. The 8 bit and 4 bit instances have phys which are
> different from the am65x interfaces as well as different from each
> other which leads to 3 different compatibles and a bunch of flags for
> indicating the differences.
>
> Depends on Nishanth's initial J721E patches here:
> https://lore.kernel.org/patchwork/cover/1077382/
This dependency is only for testing, not for applying these, right?
Thanks,
Sekhar
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-04 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 6:09 [PATCH 0/4] Add Support for MMC in J721E Faiz Abbas
2019-06-04 6:09 ` [PATCH 1/4] dt-bindings: mmc: sdhci-am654: Document bindings for the host controllers on TI's J721E devices Faiz Abbas
2019-06-04 6:09 ` [PATCH 2/4] mmc: sdhci_am654: Add Support for 8 bit IP on J721E Faiz Abbas
2019-06-12 12:07 ` Adrian Hunter
2019-06-04 6:09 ` [PATCH 3/4] mmc: sdhci_am654: Add Support for 4 " Faiz Abbas
2019-06-12 12:09 ` Adrian Hunter
2019-06-04 6:09 ` [PATCH 4/4] arm64: defconfig: Add config for MMC on AM65x and J721E devices Faiz Abbas
2019-06-04 6:18 ` Sekhar Nori [this message]
2019-06-04 6:31 ` [PATCH 0/4] Add Support for MMC in J721E Faiz Abbas
2019-06-17 11:35 ` Ulf Hansson
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=2f45cef2-c4ca-0404-b205-fabbb92a40fb@ti.com \
--to=nsekhar@ti.com \
--cc=adrian.hunter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@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).