[pinmux,scripts] board-to-kernel-dt: don't generate outer state node

From: Stephen Warren <swarren@nvidia.com>

The important thing for board-to-kernel-dt to generate is the content of
the pinmux "state" node in DT. The name and label of the node that
contains this information is essentially irrelevant. Since this
irrelevant name and label varies between boards in existing DTs, update
board-to-kernel-dt so it doesn't generate it. This makes it obvious that
the name and label shouldn't be modified when importing new versions of
board-to-kernel-dt's output.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
---
 board-to-kernel-dt.py | 4 ----
 1 file changed, 4 deletions(-)

On 14 May 2015 at 08:20, Stephen Warren <swarren@wwwdotorg.org> wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> The important thing for board-to-kernel-dt to generate is the content of
> the pinmux "state" node in DT. The name and label of the node that
> contains this information is essentially irrelevant. Since this
> irrelevant name and label varies between boards in existing DTs, update
> board-to-kernel-dt so it doesn't generate it. This makes it obvious that
> the name and label shouldn't be modified when importing new versions of
> board-to-kernel-dt's output.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
>  board-to-kernel-dt.py | 4 ----
>  1 file changed, 4 deletions(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

I don't suppose this stuff can go in a separate .dtsi include?

>
> diff --git a/board-to-kernel-dt.py b/board-to-kernel-dt.py
> index 273f74125fa6..55e556cea98b 100755
> --- a/board-to-kernel-dt.py
> +++ b/board-to-kernel-dt.py
> @@ -44,8 +44,6 @@ def mapper_pull(val):
>  def mapper_bool(val):
>      return 'TEGRA_PIN_' + {False: 'DISABLE', True: 'ENABLE'}[val]
>
> -print('                state_default: pinmux {')
> -
>  for pincfg in board.pincfgs_by_num():
>      print('                    ' + pincfg.fullname + ' {')
>      print('                            nvidia,pins = "' + pincfg.fullname + '";')
> @@ -70,6 +68,4 @@ for cfg in board.mipipadctrlcfgs_by_num():
>      print('                            nvidia,function = "' + cfg.mux + '";')
>      print('                    };')
>
> -print('                };')
> -
>  board.warn_about_unconfigured_pins()
> --
> 1.9.1
>

Regards,
Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On 05/14/2015 08:29 AM, Simon Glass wrote:
> On 14 May 2015 at 08:20, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> The important thing for board-to-kernel-dt to generate is the content of
>> the pinmux "state" node in DT. The name and label of the node that
>> contains this information is essentially irrelevant. Since this
>> irrelevant name and label varies between boards in existing DTs, update
>> board-to-kernel-dt so it doesn't generate it. This makes it obvious that
>> the name and label shouldn't be modified when importing new versions of
>> board-to-kernel-dt's output.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>>   board-to-kernel-dt.py | 4 ----
>>   1 file changed, 4 deletions(-)
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> I don't suppose this stuff can go in a separate .dtsi include?

That might make sense. I guess send a patch and see if Thierry takes it:-)
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On 05/14/2015 08:29 AM, Simon Glass wrote:
> On 14 May 2015 at 08:20, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> The important thing for board-to-kernel-dt to generate is the content of
>> the pinmux "state" node in DT. The name and label of the node that
>> contains this information is essentially irrelevant. Since this
>> irrelevant name and label varies between boards in existing DTs, update
>> board-to-kernel-dt so it doesn't generate it. This makes it obvious that
>> the name and label shouldn't be modified when importing new versions of
>> board-to-kernel-dt's output.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>>   board-to-kernel-dt.py | 4 ----
>>   1 file changed, 4 deletions(-)
>
> Reviewed-by: Simon Glass <sjg@chromium.org>

I've applied this.

--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html