public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 07/11] ARM: tegra: pinmux naming consistency fixes
Date: Thu, 20 Mar 2014 13:08:26 -0600	[thread overview]
Message-ID: <532B3CAA.9060802@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ11Ao+gqRUpamNjicupqUwSLztbph94yV5Dy=283SDBhQ@mail.gmail.com>

On 03/14/2014 02:15 PM, Simon Glass wrote:
> Hi Stephen,
> 
> On 13 March 2014 11:42, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Clean up the naming of pinmux-related objects:
>> * Refer to drive groups rather than pad groups to match the Linux kernel.
>> * Ensure all pinmux API types are prefixed with pmux_, values (defines)
>>   are prefixed with PMUX_, and functions prefixed with pinmux_.
>> * Modify a few type names to make their content clearer.
>> * Minimal changes to SoC-specific .h/.c files are made so the code still
>>   compiles. A separate per-SoC change will be made immediately following,
>>   in order to keep individual patch size down.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> 
> Acked-by: Simon Glass <sjg@chromium.org>
> 
> A few comments below.

>> diff --git a/arch/arm/cpu/tegra114-common/pinmux.c b/arch/arm/cpu/tegra114-common/pinmux.c
>> index af8b7ca5fc79..efe5163084c1 100644
>> --- a/arch/arm/cpu/tegra114-common/pinmux.c
>> +++ b/arch/arm/cpu/tegra114-common/pinmux.c
>> @@ -41,7 +41,7 @@
>>  #define PIN_RESERVED \
>>         PIN(NONE, NONE, INVALID, INVALID, INVALID, INVALID, NONE)
>>
>> -const struct tegra_pingroup_desc tegra114_pingroups[PINGRP_COUNT] = {
>> +const struct pmux_pingrp_desc tegra114_pingroups[PMUX_PINGRP_COUNT] = {
> 
> Can some of these be static?

Yes. I'll actually fix this in patch 5, since that patch is what introduced:

const struct tegra_pingroup_desc *tegra_soc_pingroups \
					= tegra114_pingroups;

... which is what allows this table to be static.

  parent reply	other threads:[~2014-03-20 19:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 17:41 [U-Boot] [PATCH 00/11] ARM: tegra: pinmux driver cleanup Stephen Warren
2014-03-13 17:41 ` [U-Boot] [PATCH 01/11] ARM: tegra: pinctrl: remove func_safe Stephen Warren
2014-03-14 18:22   ` Simon Glass
2014-03-14 18:45     ` Stephen Warren
2014-03-13 17:41 ` [U-Boot] [PATCH 02/11] ARM: tegra: pinctrl: remove vddio Stephen Warren
2014-03-14 18:23   ` Simon Glass
2014-03-13 17:41 ` [U-Boot] [PATCH 03/11] ARM: tegra: pinctrl: make pmux_func values consistent on Tegra20 Stephen Warren
2014-03-14 18:25   ` Simon Glass
2014-03-13 17:42 ` [U-Boot] [PATCH 04/11] ARM: tegra: prototype pinmux_init() in board.h Stephen Warren
2014-03-14 18:26   ` Simon Glass
2014-03-13 17:42 ` [U-Boot] [PATCH 05/11] ARM: tegra: pinctrl: remove duplication Stephen Warren
2014-03-14 19:37   ` Simon Glass
2014-03-20 19:57     ` Stephen Warren
2014-03-21  1:25       ` Simon Glass
2014-03-21  4:07         ` Stephen Warren
2014-03-13 17:42 ` [U-Boot] [PATCH 06/11] ARM: tegra: reduce public pinmux API Stephen Warren
2014-03-14 19:39   ` Simon Glass
2014-03-13 17:42 ` [U-Boot] [PATCH 07/11] ARM: tegra: pinmux naming consistency fixes Stephen Warren
2014-03-14 20:15   ` Simon Glass
2014-03-14 23:43     ` Stephen Warren
2014-03-20 19:08     ` Stephen Warren [this message]
2014-03-13 17:42 ` [U-Boot] [PATCH 08/11] ARM: tegra: Tegra20 pinmux cleanup Stephen Warren
2014-03-13 17:42 ` [U-Boot] [PATCH 09/11] ARM: tegra: Tegra30 " Stephen Warren
2014-03-13 17:42 ` [U-Boot] [PATCH 10/11] ARM: tegra: Tegra114 " Stephen Warren
2014-03-13 17:42 ` [U-Boot] [PATCH 11/11] ARM: tegra: Tegra124 " Stephen Warren

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=532B3CAA.9060802@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox