linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] soc/tegra: fuse: Add Tegra132 support
Date: Thu, 8 Jan 2015 09:50:20 +0100	[thread overview]
Message-ID: <20150108085019.GB1987@ulmo.nvidia.com> (raw)
In-Reply-To: <54AE34D6.5090507@nvidia.com>

On Thu, Jan 08, 2015 at 03:42:14PM +0800, Vince Hsu wrote:
> 
> On 01/08/2015 03:24 PM, Thierry Reding wrote:
> >From: Thierry Reding <treding@nvidia.com>
> >
> >Tegra132 is very similar to Tegra124 from a peripheral point of view and
> >uses the same fuse controller.
> >
> >Signed-off-by: Thierry Reding <treding@nvidia.com>
> >---
> >  drivers/soc/tegra/fuse/fuse-tegra.c   | 1 +
> >  drivers/soc/tegra/fuse/fuse-tegra30.c | 2 ++
> >  2 files changed, 3 insertions(+)
> >
> >diff --git a/drivers/soc/tegra/fuse/fuse-tegra.c b/drivers/soc/tegra/fuse/fuse-tegra.c
> >index 011a3363c265..c0d660f1aaac 100644
> >--- a/drivers/soc/tegra/fuse/fuse-tegra.c
> >+++ b/drivers/soc/tegra/fuse/fuse-tegra.c
> >@@ -81,6 +81,7 @@ static const struct of_device_id car_match[] __initconst = {
> >  	{ .compatible = "nvidia,tegra30-car", },
> >  	{ .compatible = "nvidia,tegra114-car", },
> >  	{ .compatible = "nvidia,tegra124-car", },
> >+	{ .compatible = "nvidia,tegra132-car", },
> >  	{},
> >  };
> >diff --git a/drivers/soc/tegra/fuse/fuse-tegra30.c b/drivers/soc/tegra/fuse/fuse-tegra30.c
> >index d1a4290cda5c..11fe22e0de73 100644
> >--- a/drivers/soc/tegra/fuse/fuse-tegra30.c
> >+++ b/drivers/soc/tegra/fuse/fuse-tegra30.c
> >@@ -184,6 +184,8 @@ static void __init legacy_fuse_init(void)
> >  	case TEGRA124:
> >  		fuse_info = &tegra124_info;
> >  		break;
> >+	case TEGRA132:
> >+		fuse_info = &tegra124_info;
> Fall through intentionally?

Nope, good catch.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150108/fb1c0a7e/attachment.sig>

  reply	other threads:[~2015-01-08  8:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  7:24 [PATCH 1/3] soc/tegra: Add Tegra132 support Thierry Reding
2015-01-08  7:24 ` [PATCH 2/3] soc/tegra: fuse: Constify tegra_fuse_info structures Thierry Reding
2015-01-08  7:24 ` [PATCH 3/3] soc/tegra: fuse: Add Tegra132 support Thierry Reding
2015-01-08  7:42   ` Vince Hsu
2015-01-08  8:50     ` Thierry Reding [this message]
2015-01-08  8:55   ` [PATCH v2 " Thierry Reding
2015-01-09  3:49     ` Alexandre Courbot
2015-01-09 10:05       ` Thierry Reding
2015-01-09 10:49     ` [PATCH v3 " 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=20150108085019.GB1987@ulmo.nvidia.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).