All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@aj.id.au>
To: linux-mmc@vger.kernel.org
Cc: Andrew Jeffery <andrew@aj.id.au>,
	ulf.hansson@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com,
	joel@jms.id.au, adrian.hunter@intel.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	ryanchen.aspeed@gmail.com
Subject: [PATCH v2 0/2] mmc: Add support for the ASPEED SD controller
Date: Fri, 12 Jul 2019 13:02:12 +0930	[thread overview]
Message-ID: <20190712033214.24713-1-andrew@aj.id.au> (raw)

Hello,

This is v2 of the ASPEED SD controller driver. v2 primarily addresses Rob's
comments on the bindings in v1. The v1 series can be found here:

https://lists.ozlabs.org/pipermail/linux-aspeed/2019-July/001988.html

Please review!

Andrew

Andrew Jeffery (2):
  dt-bindings: mmc: Document Aspeed SD controller
  mmc: Add support for the ASPEED SD controller

 .../devicetree/bindings/mmc/aspeed,sdhci.yaml |  90 +++++
 drivers/mmc/host/Kconfig                      |  12 +
 drivers/mmc/host/Makefile                     |   1 +
 drivers/mmc/host/sdhci-of-aspeed.c            | 326 ++++++++++++++++++
 4 files changed, 429 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml
 create mode 100644 drivers/mmc/host/sdhci-of-aspeed.c

-- 
2.20.1


WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jeffery <andrew@aj.id.au>
To: linux-mmc@vger.kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	ulf.hansson@linaro.org, linux-aspeed@lists.ozlabs.org,
	Andrew Jeffery <andrew@aj.id.au>,
	ryanchen.aspeed@gmail.com, adrian.hunter@intel.com,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org, joel@jms.id.au,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] mmc: Add support for the ASPEED SD controller
Date: Fri, 12 Jul 2019 13:02:12 +0930	[thread overview]
Message-ID: <20190712033214.24713-1-andrew@aj.id.au> (raw)

Hello,

This is v2 of the ASPEED SD controller driver. v2 primarily addresses Rob's
comments on the bindings in v1. The v1 series can be found here:

https://lists.ozlabs.org/pipermail/linux-aspeed/2019-July/001988.html

Please review!

Andrew

Andrew Jeffery (2):
  dt-bindings: mmc: Document Aspeed SD controller
  mmc: Add support for the ASPEED SD controller

 .../devicetree/bindings/mmc/aspeed,sdhci.yaml |  90 +++++
 drivers/mmc/host/Kconfig                      |  12 +
 drivers/mmc/host/Makefile                     |   1 +
 drivers/mmc/host/sdhci-of-aspeed.c            | 326 ++++++++++++++++++
 4 files changed, 429 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml
 create mode 100644 drivers/mmc/host/sdhci-of-aspeed.c

-- 
2.20.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-07-12  3:32 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  3:32 Andrew Jeffery [this message]
2019-07-12  3:32 ` [PATCH v2 0/2] mmc: Add support for the ASPEED SD controller Andrew Jeffery
2019-07-12  3:32 ` [PATCH v2 1/2] dt-bindings: mmc: Document Aspeed " Andrew Jeffery
2019-07-12  3:32   ` Andrew Jeffery
2019-07-12 13:03   ` Rob Herring
2019-07-12 13:03     ` Rob Herring
2019-07-12 13:03     ` Rob Herring
2019-07-12 13:10   ` Maxime Ripard
2019-07-12 13:10     ` Maxime Ripard
2019-07-15  2:30     ` Andrew Jeffery
2019-07-15  2:30       ` Andrew Jeffery
2019-07-15 13:26       ` Rob Herring
2019-07-15 13:26         ` Rob Herring
2019-07-15 13:26         ` Rob Herring
2019-07-15 22:16   ` Rob Herring
2019-07-15 22:16     ` Rob Herring
2019-07-15 22:16     ` Rob Herring
2019-07-16  0:36     ` Andrew Jeffery
2019-07-16  0:36       ` Andrew Jeffery
2019-07-16  0:36       ` Andrew Jeffery
2019-07-16 14:57       ` Rob Herring
2019-07-16 14:57         ` Rob Herring
2019-07-16 14:57         ` Rob Herring
2019-07-17  3:57         ` Andrew Jeffery
2019-07-17  3:57           ` Andrew Jeffery
2019-07-17  3:57           ` Andrew Jeffery
2019-07-17 13:43           ` Rob Herring
2019-07-17 13:43             ` Rob Herring
2019-07-17 13:43             ` Rob Herring
2019-07-18  1:49             ` Andrew Jeffery
2019-07-18  1:49               ` Andrew Jeffery
2019-07-18  1:49               ` Andrew Jeffery
2019-07-12  3:32 ` [PATCH v2 2/2] mmc: Add support for the ASPEED " Andrew Jeffery
2019-07-12  3:32   ` Andrew Jeffery
2019-07-25 13:18   ` Adrian Hunter
2019-07-25 13:18     ` Adrian Hunter
2019-07-25 13:18     ` Adrian Hunter
2019-07-26  0:52     ` Andrew Jeffery
2019-07-26  0:52       ` Andrew Jeffery
2019-07-26  0:52       ` Andrew Jeffery
2019-07-26  5:56       ` Adrian Hunter
2019-07-26  5:56         ` Adrian Hunter
2019-07-26  6:47         ` Andrew Jeffery
2019-07-26  6:47           ` Andrew Jeffery
2019-07-26  6:47           ` Andrew Jeffery

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=20190712033214.24713-1-andrew@aj.id.au \
    --to=andrew@aj.id.au \
    --cc=adrian.hunter@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=ryanchen.aspeed@gmail.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 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.