mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikko Perttunen <cyndis@kapsi.fi>
To: Sandipan Patra <spatra@nvidia.com>,
	treding@nvidia.com, jonathanh@nvidia.com
Cc: bbasu@nvidia.com, kyarlagadda@nvidia.com,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc/tegra: Add Tegra Soc Version support
Date: Fri, 26 Jun 2020 13:50:13 +0300	[thread overview]
Message-ID: <64d65736-62c2-de17-5657-389475fff6e2@kapsi.fi> (raw)
In-Reply-To: <1593167369-25901-1-git-send-email-spatra@nvidia.com>

On 6/26/20 1:29 PM, Sandipan Patra wrote:
> Add the chip IDs for NVIDIA Tegra186, Tegra194 and Tegra234
> SoC family.

families

> 
> Signed-off-by: Sandipan Patra <spatra@nvidia.com>
> ---
>   include/soc/tegra/fuse.h | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/include/soc/tegra/fuse.h b/include/soc/tegra/fuse.h
> index 252ea20..4a5236b 100644
> --- a/include/soc/tegra/fuse.h
> +++ b/include/soc/tegra/fuse.h
> @@ -1,6 +1,6 @@
>   /* SPDX-License-Identifier: GPL-2.0-only */
>   /*
> - * Copyright (c) 2012, NVIDIA CORPORATION.  All rights reserved.
> + * Copyright (c) 2012-2020, NVIDIA CORPORATION.  All rights reserved.
>    */
>   
>   #ifndef __SOC_TEGRA_FUSE_H__
> @@ -12,6 +12,9 @@
>   #define TEGRA124	0x40
>   #define TEGRA132	0x13
>   #define TEGRA210	0x21
> +#define TEGRA186	0x18
> +#define TEGRA194	0x19
> +#define TEGRA234	0x23
>   
>   #define TEGRA_FUSE_SKU_CALIB_0	0xf0
>   #define TEGRA30_FUSE_SATA_CALIB	0x124
> 

Also, can you make the commit message something like "soc/tegra: Add 
defines for Tegra186+ chip IDs"?

thanks,
Mikko

  reply	other threads:[~2020-06-26 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 10:29 Sandipan Patra
2020-06-26 10:50 ` Mikko Perttunen [this message]
2020-06-26 10:58   ` Sandipan Patra

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=64d65736-62c2-de17-5657-389475fff6e2@kapsi.fi \
    --to=cyndis@kapsi.fi \
    --cc=bbasu@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=kyarlagadda@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=spatra@nvidia.com \
    --cc=treding@nvidia.com \
    /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
all inboxes | Powered by JetHome®