All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: kernel@pengutronix.de, Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-arm-kernel@lists.infradead.org,
	patchwork-lst@pengutronix.de
Subject: Re: [PATCH] soc: imx8: print SoC type and revision
Date: Mon, 9 Dec 2019 15:24:56 +0800	[thread overview]
Message-ID: <20191209072455.GF3365@dragon> (raw)
In-Reply-To: <20191127110556.3950-1-l.stach@pengutronix.de>

On Wed, Nov 27, 2019 at 12:05:56PM +0100, Lucas Stach wrote:
> This is useful information to have when looking through system logs,
> so add it to the output.
> 
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>

It doesn't apply to v5.5-rc1.  I applied it manually.  Please check
imx/drivers branch to make sure it's done correctly.

Shawn

> ---
>  drivers/soc/imx/soc-imx8.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/soc/imx/soc-imx8.c b/drivers/soc/imx/soc-imx8.c
> index dbf57203e9ee..cafec82b2e7b 100644
> --- a/drivers/soc/imx/soc-imx8.c
> +++ b/drivers/soc/imx/soc-imx8.c
> @@ -211,6 +211,9 @@ static int __init imx8_soc_init(void)
>  	if (ret)
>  		goto free_rev;
>  
> +	pr_info("SoC: %s revision %s\n", soc_dev_attr->soc_id,
> +		soc_dev_attr->revision);
> +
>  	if (IS_ENABLED(CONFIG_ARM_IMX_CPUFREQ_DT))
>  		platform_device_register_simple("imx-cpufreq-dt", -1, NULL, 0);
>  
> -- 
> 2.20.1
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-12-09  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 11:05 [PATCH] soc: imx8: print SoC type and revision Lucas Stach
2019-12-09  7:24 ` Shawn Guo [this message]

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=20191209072455.GF3365@dragon \
    --to=shawnguo@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=patchwork-lst@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.