From: Stephen Warren <swarren@nvidia.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
Stephen Warren <swarren@nvidia.com>
Subject: [PATCH 1/3] mmc/tegra: Use engineering names in DT compatible property
Date: Tue, 5 Jul 2011 14:29:20 -0600 [thread overview]
Message-ID: <1309897762-23564-2-git-send-email-swarren@nvidia.com> (raw)
In-Reply-To: <1309897762-23564-1-git-send-email-swarren@nvidia.com>
Engineering names are more stable than marketing names. Hence, use them
for Device Tree compatible properties instead.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
---
drivers/mmc/host/sdhci-pltfm.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/sdhci-pltfm.c b/drivers/mmc/host/sdhci-pltfm.c
index 9cc92b0..0cf16bb 100644
--- a/drivers/mmc/host/sdhci-pltfm.c
+++ b/drivers/mmc/host/sdhci-pltfm.c
@@ -52,7 +52,7 @@ static struct sdhci_ops sdhci_pltfm_ops = {
#if defined(CONFIG_OF)
#include <linux/of_device.h>
static const struct of_device_id sdhci_dt_ids[] = {
- { .compatible = "nvidia,tegra250-sdhci", .data = &sdhci_tegra_dt_pdata },
+ { .compatible = "nvidia,tegra20-sdhci", .data = &sdhci_tegra_dt_pdata },
{ }
};
MODULE_DEVICE_TABLE(platform, sdhci_dt_ids);
--
1.7.0.4
next prev parent reply other threads:[~2011-07-05 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 20:29 [PATCH 0/3] tegra: Use engineering names in DT compatible properties Stephen Warren
2011-07-05 20:29 ` Stephen Warren [this message]
[not found] ` <1309897762-23564-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-07-05 20:29 ` [PATCH 2/3] ARM: tegra: Use engineering names in DT compatible property Stephen Warren
2011-07-05 20:29 ` [PATCH 3/3] dt: docs: " Stephen Warren
2011-07-06 5:55 ` [PATCH 0/3] tegra: Use engineering names in DT compatible properties Grant Likely
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=1309897762-23564-2-git-send-email-swarren@nvidia.com \
--to=swarren@nvidia.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.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).