devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: tony@atomide.com, balbi@ti.com, linux-omap@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] pinctrl: dra: dt-bindings: Fix output pull up/down
Date: Mon, 3 Nov 2014 11:28:57 +0200	[thread overview]
Message-ID: <54574AD9.3040907@ti.com> (raw)
In-Reply-To: <20141031135030.GA25252@kahuna>

On 10/31/2014 03:50 PM, Nishanth Menon wrote:
> On 12:52-20141031, Roger Quadros wrote:
>> For PIN_OUTPUT_PULLUP and PIN_OUTPUT_PULLDOWN we must not set the
>> PULL_DIS bit which disables the PULLs.
>>
>> While at that get rid for the PULL_ENA defination. It is misleading
>> as there is no PULL enable bit in the register. And a zero bit defination
>> makes no sense.
> It was done to make it readable. Pull is enabled when that bit is 0 and
> disabled when that bit is 1. it is counter intutive enough for a macro

But you can't enable the PULL by ORing it. you have to AND it's inverted version with the rest.
It is confusing because it doesn't follow the logic of the other bit masks.

> to be defined. I suggest retaining that and not mixing with the current
> patch.

Agreed. I'll revise this patch to not touch that macro.

cheers,
-roger

> 
> 
>>
>> Fixes: 23d9cec07c58 (:pinctrl: dra: dt-bindings: Fix pull enable/disable")
> s/:pinctrl/"pinctrl/ ?
> 
>>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> ---
>>  include/dt-bindings/pinctrl/dra.h | 9 ++++-----
>>  1 file changed, 4 insertions(+), 5 deletions(-)
>>
>> diff --git a/include/dt-bindings/pinctrl/dra.h b/include/dt-bindings/pinctrl/dra.h
>> index 3d33794..71098e4 100644
>> --- a/include/dt-bindings/pinctrl/dra.h
>> +++ b/include/dt-bindings/pinctrl/dra.h
>> @@ -30,7 +30,6 @@
>>  #define MUX_MODE14	0xe
>>  #define MUX_MODE15	0xf
>>  
>> -#define PULL_ENA		(0 << 16)
>>  #define PULL_DIS		(1 << 16)
>>  #define PULL_UP			(1 << 17)
>>  #define INPUT_EN		(1 << 18)
>> @@ -40,12 +39,12 @@
>>  
>>  /* Active pin states */
>>  #define PIN_OUTPUT		(0 | PULL_DIS)
>> -#define PIN_OUTPUT_PULLUP	(PIN_OUTPUT | PULL_ENA | PULL_UP)
>> -#define PIN_OUTPUT_PULLDOWN	(PIN_OUTPUT | PULL_ENA)
>> +#define PIN_OUTPUT_PULLUP	(PULL_UP)
>> +#define PIN_OUTPUT_PULLDOWN	(0)
>>  #define PIN_INPUT		(INPUT_EN | PULL_DIS)
>>  #define PIN_INPUT_SLEW		(INPUT_EN | SLEWCONTROL)
>> -#define PIN_INPUT_PULLUP	(PULL_ENA | INPUT_EN | PULL_UP)
>> -#define PIN_INPUT_PULLDOWN	(PULL_ENA | INPUT_EN)
>> +#define PIN_INPUT_PULLUP	(INPUT_EN | PULL_UP)
>> +#define PIN_INPUT_PULLDOWN	(INPUT_EN)
>>  
>>  #endif
>>  
>> -- 
>> 1.8.3.2
>>
> 


  reply	other threads:[~2014-11-03  9:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 10:52 [PATCH] pinctrl: dra: dt-bindings: Fix output pull up/down Roger Quadros
2014-10-31 13:50 ` Nishanth Menon
2014-11-03  9:28   ` Roger Quadros [this message]
2014-11-03 10:09 ` [PATCH v2] " Roger Quadros
2014-11-03 14:30   ` Nishanth Menon
2014-11-03 14:44     ` Roger Quadros
2014-11-03 14:59       ` Nishanth Menon
2014-11-03 15:07         ` Roger Quadros
2014-11-03 17:56           ` Nishanth Menon
2014-11-05 17:10   ` Nishanth Menon
2014-11-10 22:29     ` Tony Lindgren

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=54574AD9.3040907@ti.com \
    --to=rogerq@ti.com \
    --cc=balbi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --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 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).