mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: at91: remove unused soc type/subtype getter functions
Date: Thu, 19 Jun 2025 19:13:58 +0200	[thread overview]
Message-ID: <20250619171358.GA1859740@ravnborg.org> (raw)
In-Reply-To: <20250619103440.76796-1-eagle.alexander923@gmail.com>

Hi Alexander.

On Thu, Jun 19, 2025 at 01:34:40PM +0300, Alexander Shiyan wrote:
> The functions at91_get_soc_type() and at91_get_soc_subtype() were
> used only within the setup.c file. They provided simple access to
> string arrays but added an unnecessary layer of abstraction.
> Since they are not used elsewhere, we can safely remove them and
> access the string arrays directly.
> 
> Signed-off-by: Alexander Shiyan <eagle.alexander923@gmail.com>
> ---
>  arch/arm/mach-at91/setup.c | 22 ++++++----------------
>  include/mach/at91/cpu.h    |  2 --
>  2 files changed, 6 insertions(+), 18 deletions(-)
> 
> diff --git a/arch/arm/mach-at91/setup.c b/arch/arm/mach-at91/setup.c
> index e726495726..5969c32e54 100644
> --- a/arch/arm/mach-at91/setup.c
> +++ b/arch/arm/mach-at91/setup.c
> @@ -281,12 +281,6 @@ static const char *soc_name[] = {
>  	[AT91_SOC_NONE]		= "Unknown"
>  };
>  
> -const char *at91_get_soc_type(struct at91_socinfo *c)
> -{
> -	return soc_name[c->type];
> -}
> -EXPORT_SYMBOL(at91_get_soc_type);
> -
>  static const char *soc_subtype_name[] = {
>  	[AT91_SOC_RM9200_BGA]	= "at91rm9200 BGA",
>  	[AT91_SOC_RM9200_PQFP]	= "at91rm9200 PQFP",
> @@ -330,12 +324,6 @@ static const char *soc_subtype_name[] = {
>  	[AT91_SOC_SUBTYPE_NONE]	= "Unknown"
>  };
>  
> -const char *at91_get_soc_subtype(struct at91_socinfo *c)
> -{
> -	return soc_subtype_name[c->subtype];
> -}
> -EXPORT_SYMBOL(at91_get_soc_subtype);
> -
>  static int at91_detect(void)
>  {
>  	at91_soc_initdata.type = AT91_SOC_NONE;
> @@ -353,9 +341,9 @@ static int at91_detect(void)
>  		panic("AT91: Impossible to detect the SOC type");
>  
>  	pr_info("AT91: Detected soc type: %s\n",
> -		at91_get_soc_type(&at91_soc_initdata));
> +		soc_name[at91_soc_initdata.type]);
>  	pr_info("AT91: Detected soc subtype: %s\n",
> -		at91_get_soc_subtype(&at91_soc_initdata));
> +		soc_subtype_name[at91_soc_initdata.subtype]);
>  
>  	/* Init clock subsystem */
>  	at91_clock_init();
> @@ -372,8 +360,10 @@ static int at91_soc_device(void)
>  	struct device *dev;
>  
>  	dev = add_generic_device_res("soc", DEVICE_ID_SINGLE, NULL, 0, NULL);
> -	dev_add_param_fixed(dev, "name", (char*)at91_get_soc_type(&at91_soc_initdata));
> -	dev_add_param_fixed(dev, "subname", (char*)at91_get_soc_subtype(&at91_soc_initdata));
> +	dev_add_param_fixed(dev, "name",
> +			    (char*)soc_name[at91_soc_initdata.type]);
> +	dev_add_param_fixed(dev, "subname",
> +			    (char*)soc_subtype_name[at91_soc_initdata.subtype]);
The cast can go, as dev_add_param_fixed() take a const already.
Otherwise looks good.
It is good to see at91 gets some attention, despite the age.

	Sam



  reply	other threads:[~2025-06-19 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 10:34 Alexander Shiyan
2025-06-19 17:13 ` Sam Ravnborg [this message]
2025-06-20  5:48   ` Alexander Shiyan

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=20250619171358.GA1859740@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=barebox@lists.infradead.org \
    --cc=eagle.alexander923@gmail.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