From: <kostap@marvell.com>
To: <linux-mmc@vger.kernel.org>
Cc: <ulf.hansson@linaro.org>, <robh+dt@kernel.org>, <andrew@lunn.ch>,
<gregory.clement@bootlin.com>, <sebastian.hesselbarth@gmail.com>,
<adrian.hunter@intel.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <mw@semihalf.com>,
<jaz@semihalf.com>, <nadavh@marvell.com>, <bpeled@marvell.com>,
<stefanc@marvell.com>, Konstantin Porotchkin <kostap@marvell.com>
Subject: [PATCH v3 0/4] update xenon controller properties in CN913X
Date: Tue, 12 Jan 2021 11:46:51 +0200 [thread overview]
Message-ID: <20210112094655.12274-1-kostap@marvell.com> (raw)
From: Konstantin Porotchkin <kostap@marvell.com>
The following patches series updates Xenon SDHCI controller properties
for usage with Marvell Armada CN913X SoC family.
- v2:
* rebase on top of "next" branch of linux/kernel/git/ulfh/mmc.git
- v3:
* separate between driver and DTSI changes for new compatibility
string
* add my signed-off-by entry to all patches
Konstantin Porotchkin (1):
arm64: dts: change AP807 SDHCI compatibility string
Marcin Wojtas (3):
dt-bindings: mmc: xenon: add AP807 compatible string
mmc: xenon: add AP807 compatible string
arm64: dts: cn913x-db: enable MMC HS400
.../devicetree/bindings/mmc/marvell,xenon-sdhci.txt | 1 +
arch/arm64/boot/dts/marvell/armada-ap807.dtsi | 5 +++++
arch/arm64/boot/dts/marvell/cn9130-db.dts | 2 ++
drivers/mmc/host/sdhci-xenon.c | 1 +
4 files changed, 9 insertions(+)
--
2.17.1
next reply other threads:[~2021-01-12 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 9:46 kostap [this message]
2021-01-12 9:46 ` [PATCH v3 1/4] dt-bindings: mmc: xenon: add AP807 compatible string kostap
2021-01-12 9:46 ` [PATCH v3 2/4] " kostap
2021-01-12 9:46 ` [PATCH v3 3/4] arm64: dts: change AP807 SDHCI compatibility string kostap
2021-01-12 9:46 ` [PATCH v3 4/4] arm64: dts: cn913x-db: enable MMC HS400 kostap
2021-01-13 11:25 ` [PATCH v3 0/4] update xenon controller properties in CN913X 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=20210112094655.12274-1-kostap@marvell.com \
--to=kostap@marvell.com \
--cc=adrian.hunter@intel.com \
--cc=andrew@lunn.ch \
--cc=bpeled@marvell.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jaz@semihalf.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=stefanc@marvell.com \
--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).