linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/8] ARM: dts: imx: imx6sl/qdl-pingrp: reorganize USDHCx pad groups
Date: Fri, 15 Nov 2013 12:04:17 +0000	[thread overview]
Message-ID: <20131115120417.GJ16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1384462934-17390-4-git-send-email-troy.kisky@boundarydevices.com>

On Thu, Nov 14, 2013 at 02:02:09PM -0700, Troy Kisky wrote:
> +#define MX6QDL_USDHC1_D4(pad, pad_clk) \
> +	MX6QDL_PAD_SD1_CMD__SD1_CMD			pad \
> +	MX6QDL_PAD_SD1_CLK__SD1_CLK			pad_clk \
> +	MX6QDL_PAD_SD1_DAT0__SD1_DATA0			pad \
> +	MX6QDL_PAD_SD1_DAT1__SD1_DATA1			pad \
> +	MX6QDL_PAD_SD1_DAT2__SD1_DATA2			pad \
> +	MX6QDL_PAD_SD1_DAT3__SD1_DATA3			pad

DATA3 should be specified separately as you may want that to have a
different pull direction due to the workarounds in the driver interfering
with the card present detection.

  reply	other threads:[~2013-11-15 12:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 21:02 [PATCH 0/8] imx6 dts cleanup series Troy Kisky
2013-11-14 21:02 ` [PATCH 1/8] ARM: dts: imx: pinfunc: add MX6QDL_PAD_SD1_CLK__OSC32K_32K_OUT Troy Kisky
2013-11-14 21:02 ` [PATCH 2/8] ARM: dts: imx: imx6qdl.dtsi: add mipi_csi tag Troy Kisky
2013-11-14 21:02 ` [PATCH 3/8] ARM: dts: imx: imx6sl/qdl-pingrp: reorganize USDHCx pad groups Troy Kisky
2013-11-15 12:04   ` Russell King - ARM Linux [this message]
2013-11-15 17:07     ` Troy Kisky
2013-11-14 21:02 ` [PATCH 4/8] ARM: dts: imx: imx6q.dtsi: use IRQ_TYPE_LEVEL_HIGH Troy Kisky
2013-11-14 21:02 ` [PATCH 5/8] ARM: dts: imx: imx6dl.dtsi: " Troy Kisky
2013-11-14 21:02 ` [PATCH 6/8] ARM: dts: imx: imx6sl.dtsi: " Troy Kisky
2013-11-14 21:02 ` [PATCH 7/8] ARM: dts: imx: imx6qdl.dtsi: " Troy Kisky
2013-11-14 21:02 ` [PATCH 8/8] ARM: dts: imx: sabrelite: add dualLite support Troy Kisky
2013-11-18  1:25 ` [PATCH 0/8] imx6 dts cleanup series Shawn Guo

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=20131115120417.GJ16735@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).