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 v2 3/3] soc/tegra: fuse: Add Tegra132 support
Date: Fri, 9 Jan 2015 11:05:12 +0100	[thread overview]
Message-ID: <20150109100510.GF27845@ulmo> (raw)
In-Reply-To: <CAAVeFuKbnquF0iBp4L8Sv4tp-F3YevKjaSkVtyT2LJnDDvXCbg@mail.gmail.com>

On Fri, Jan 09, 2015 at 12:49:25PM +0900, Alexandre Courbot wrote:
> On Thu, Jan 8, 2015 at 5:55 PM, Thierry Reding <thierry.reding@gmail.com> 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>
> > ---
> > Changes in v2:
> > - add missing break in Tegra132 case for legacy fuse init (Vince Hsu)
> >
> >  drivers/soc/tegra/fuse/fuse-tegra.c   | 1 +
> >  drivers/soc/tegra/fuse/fuse-tegra30.c | 3 +++
> >  2 files changed, 4 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..9e3679594259 100644
> > --- a/drivers/soc/tegra/fuse/fuse-tegra30.c
> > +++ b/drivers/soc/tegra/fuse/fuse-tegra30.c
> > @@ -184,6 +184,9 @@ static void __init legacy_fuse_init(void)
> >         case TEGRA124:
> >                 fuse_info = &tegra124_info;
> >                 break;
> > +       case TEGRA132:
> > +               fuse_info = &tegra124_info;
> > +               break;
> 
> Nit, but why not
> 
>         case TEGRA124:
> +       case TEGRA132:
>                 fuse_info = &tegra124_info;
>                 break;

Yes, that's even better.

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/20150109/a8f08b0d/attachment.sig>

  reply	other threads:[~2015-01-09 10:05 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
2015-01-08  8:55   ` [PATCH v2 " Thierry Reding
2015-01-09  3:49     ` Alexandre Courbot
2015-01-09 10:05       ` Thierry Reding [this message]
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=20150109100510.GF27845@ulmo \
    --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).