From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/8] soc/tegra: Add Tegra210 support
Date: Mon, 4 May 2015 13:46:42 +0200 [thread overview]
Message-ID: <1430740006-29539-5-git-send-email-thierry.reding@gmail.com> (raw)
In-Reply-To: <1430740006-29539-1-git-send-email-thierry.reding@gmail.com>
From: Thierry Reding <treding@nvidia.com>
Add Tegra210 to the matching table for NVIDIA Tegra SoCs.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
drivers/soc/tegra/common.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soc/tegra/common.c b/drivers/soc/tegra/common.c
index a952986a14b7..cd8f41351add 100644
--- a/drivers/soc/tegra/common.c
+++ b/drivers/soc/tegra/common.c
@@ -16,6 +16,7 @@ static const struct of_device_id tegra_machine_match[] = {
{ .compatible = "nvidia,tegra114", },
{ .compatible = "nvidia,tegra124", },
{ .compatible = "nvidia,tegra132", },
+ { .compatible = "nvidia,tegra210", },
{ }
};
--
2.3.5
next prev parent reply other threads:[~2015-05-04 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 11:46 [PATCH 0/8] soc/tegra: More unification and cleanup for 64-bit Thierry Reding
2015-05-04 11:46 ` [PATCH 1/8] soc/tegra: pmc: Restrict legacy code to 32-bit ARM Thierry Reding
2015-05-04 11:46 ` [PATCH 2/8] soc/tegra: pmc: Add Tegra210 support Thierry Reding
2015-05-04 11:46 ` [PATCH 3/8] soc/tegra: Add Tegra132 support Thierry Reding
2015-05-04 11:46 ` Thierry Reding [this message]
2015-05-04 11:46 ` [PATCH 5/8] soc/tegra: fuse: Restrict legacy code to 32-bit ARM Thierry Reding
2015-05-04 11:46 ` [PATCH 6/8] soc/tegra: fuse: Unify Tegra20 and Tegra30 drivers Thierry Reding
2015-05-04 11:46 ` [PATCH 7/8] soc/tegra: fuse: Add Tegra210 support Thierry Reding
2015-05-04 11:46 ` [PATCH 8/8] soc/tegra: fuse: Rename core_* to soc_* Thierry Reding
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=1430740006-29539-5-git-send-email-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--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).