All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew F. Davis" <afd@ti.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: "Tony Lindgren" <tony@atomide.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: am335x-boneblack: Use pinctrl constants
Date: Fri, 23 Oct 2015 09:36:12 -0500	[thread overview]
Message-ID: <562A45DC.1090501@ti.com> (raw)
In-Reply-To: <CABxcv=kDXK3CR=YfS-P9VaaXY-rmT2KpuKsAs_BdfZMVtfwzDQ@mail.gmail.com>

On 10/23/2015 09:29 AM, Javier Martinez Canillas wrote:
> Hello Andrew,
>
> On Fri, Oct 23, 2015 at 3:08 PM, Andrew F. Davis <afd@ti.com> wrote:
>> On 10/22/2015 04:23 PM, Tony Lindgren wrote:
>>>
>>> * Andrew F. Davis <afd@ti.com> [151022 09:21]:
>>>>
>>>> Using constants for pinctrl allows better readability and removes
>>>> redundancy with comments.
>>>
>>>
>>> You should use the include/dt-bindings/pinctrl/omap.h macro
>>> AM33XX_IOPAD(pa, val) while at it. Otherwise we'll end up patching
>>> the same things again later on.
>>>
>>
>> Hmm, I haven't really been following this change, it kind of seems to add
>> some unnecessary abstraction by using physical hardware addresses instead
>> of offsets, then just converting them back to offsets. The offset style DT
>> nodes are already auto-generated with existing tools anyway:
>> https://dev.ti.com/pinmux
>>
>> I'm sure this has been discussed already so if this is a blocker I'll
>> re-spin this.
>>
>
> The good thing about the IOPAD pinmux macros is that matches what is
> in the TRM so it is easier to read the DTS and verify that is correct.
>
> I've on my queue to migrate all the remaining DTS for TI SoCs to use
> the IOPAD macros but is just that I didn't have time to do it this
> week. Probably I'll do it at the end of the next week.
>

Then this patch can probably be dropped, hopefully the converted constants
in this patch can be of some help for you though.

Andrew

>> Andrew
>>
>>
>>> Regards,
>>>
>
> Best regards,
> Javier
>

  reply	other threads:[~2015-10-23 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 16:20 [PATCH] ARM: dts: am335x-boneblack: Use pinctrl constants Andrew F. Davis
2015-10-22 16:20 ` Andrew F. Davis
     [not found] ` <1445530847-25217-1-git-send-email-afd-l0cyMroinI0@public.gmane.org>
2015-10-22 21:23   ` Tony Lindgren
2015-10-22 21:23     ` Tony Lindgren
2015-10-23 13:08     ` Andrew F. Davis
2015-10-23 14:29       ` Javier Martinez Canillas
2015-10-23 14:36         ` Andrew F. Davis [this message]
     [not found]           ` <562A45DC.1090501-l0cyMroinI0@public.gmane.org>
2015-10-23 14:47             ` Javier Martinez Canillas
2015-10-23 14:47               ` Javier Martinez Canillas

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=562A45DC.1090501@ti.com \
    --to=afd@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=javier@dowhile0.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 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.