From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V1 05/11] ARM: dts: imx6qdl-sabrelite: specify pad settings
Date: Fri, 13 Dec 2013 22:50:29 +0100 [thread overview]
Message-ID: <201312132250.29518.marex@denx.de> (raw)
In-Reply-To: <52AB5511.7040209@boundarydevices.com>
On Friday, December 13, 2013 at 07:42:25 PM, Troy Kisky wrote:
> On 12/13/2013 4:48 AM, Marek Vasut wrote:
> > On Friday, December 13, 2013 at 02:49:09 AM, Troy Kisky wrote:
> >> Don't use 0x80000000 to get default pad settings.
> >
> > What is the rationale behind this change please? Can you explain more in
> > detail?
>
> No real need, but I thought relying on what the boot loader did or did
> not do
> was discouraged?
Full ACK on this, we do not rely on bootloader configuration (though these two
should be in-line).
> What is the value in not explicitly setting the pad registers?
My question was in the direction of "why do you need to change the pin
configuration values from the current ones?". This is what I want to understand.
> Btw, I need to rebase series on your patch anyway so omitting this patch
> would be easy.
I am not saying to omit it, please do not misunderstand me. I am just wondering
why the change from 0x80000000 to 0x1b0b0 .
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-12-13 21:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 1:49 [PATCH V1 00/11] Update Sabre Lite Troy Kisky
2013-12-13 1:49 ` [PATCH V1 01/11] ARM: dts: imx: sabrelite: add Dual Lite/Solo support Troy Kisky
2013-12-13 11:46 ` Marek Vasut
2013-12-13 18:51 ` Troy Kisky
2013-12-13 21:51 ` Marek Vasut
2013-12-13 1:49 ` [PATCH V1 02/11] ARM: dts: imx6qdl-sabrelite: Add uart1 support Troy Kisky
2013-12-13 11:46 ` Marek Vasut
2013-12-13 1:49 ` [PATCH V1 03/11] ARM: dts: imx6qdl-sabrelite: remove usdhc4 wp-gpio Troy Kisky
2013-12-13 11:46 ` Marek Vasut
2013-12-14 13:46 ` Shawn Guo
2013-12-16 19:42 ` Troy Kisky
2013-12-16 19:54 ` Marek Vasut
2013-12-16 23:59 ` Troy Kisky
2013-12-13 1:49 ` [PATCH V1 04/11] ARM: dts: imx6qdl-sabrelite: add comments for pinctrl_hog Troy Kisky
2013-12-13 11:47 ` Marek Vasut
2013-12-14 13:54 ` Shawn Guo
2013-12-13 1:49 ` [PATCH V1 05/11] ARM: dts: imx6qdl-sabrelite: specify pad settings Troy Kisky
2013-12-13 11:48 ` Marek Vasut
2013-12-13 18:42 ` Troy Kisky
2013-12-13 21:50 ` Marek Vasut [this message]
2013-12-14 1:44 ` Troy Kisky
2013-12-14 5:00 ` Marek Vasut
2013-12-14 13:29 ` Shawn Guo
2013-12-14 14:16 ` Marek Vasut
2013-12-13 1:49 ` [PATCH V1 06/11] ARM: dts: imx6qdl-sabrelite: add gpio-keys Troy Kisky
2013-12-13 11:51 ` Marek Vasut
2013-12-13 18:45 ` Troy Kisky
2013-12-13 21:50 ` Marek Vasut
2013-12-13 21:55 ` Eric Nelson
2013-12-14 5:00 ` Marek Vasut
2013-12-14 13:57 ` Shawn Guo
2013-12-13 1:49 ` [PATCH V1 07/11] ARM: dts: imx6qdl-sabrelite: add pwms for backlights Troy Kisky
2013-12-13 11:53 ` Marek Vasut
2013-12-13 14:09 ` Eric Nelson
2013-12-13 1:49 ` [PATCH V1 08/11] ARM: dts: imx6qdl-sabrelite: add skews for Micrel phy Troy Kisky
2013-12-13 11:53 ` Marek Vasut
2013-12-13 1:49 ` [PATCH V1 09/11] ARM: dts: imx6qdl-sabrelite: fix ENET group Troy Kisky
2013-12-13 11:54 ` Marek Vasut
2013-12-13 1:49 ` [PATCH V1 10/11] ARM: dts: imx6qdl-sabrelite: Add over-current pin to usbotg Troy Kisky
2013-12-13 11:54 ` Marek Vasut
2013-12-13 1:49 ` [PATCH V1 11/11] ARM: dts: imx: add nitrogen6x board Troy Kisky
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=201312132250.29518.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).