From: "Peter A. Bigot" <pab@pabigot.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: meta-ti@yoctoproject.org
Subject: Re: mis-definition of SLEWCTRL_FAST in dt-bindings amxxxx header
Date: Wed, 08 Oct 2014 18:53:51 -0500 [thread overview]
Message-ID: <5435CE8F.3020500@pabigot.com> (raw)
In-Reply-To: <20141007205837.GF25997@denix.org>
Depends what "upstream" means. It's not in 3.17 released 05 Oct, nor in
any other non-TI repository I can find. (Might be hidden in a TI
repository somewhere that I'm not looking.)
Peter
On 10/07/2014 03:58 PM, Denys Dmytriyenko wrote:
> Wasn't this already fixed upstream?
>
> On Wed, Sep 17, 2014 at 07:17:03AM -0500, Peter A. Bigot wrote:
>> Any comment on this? I have a patch, but figured it'd be better for
>> TI to provide an official solution. Or is there another forum it
>> should be raised in?
>>
>> It's really misleading for the self-documenting device tree
>> specifications to lie about what sort of slew is being configured.
>>
>> Peter
>>
>> On 09/06/2014 06:17 PM, Peter A. Bigot wrote:
>>> While converting some old DTS bindings, I noticed that the Linux
>>> include/dt-bindings/pinctrl/am33xx.h and am43xx.h headers both
>>> define SLEWCTRL_FAST constants:
>>>
>>> include/dt-bindings/pinctrl/am33xx.h:#define SLEWCTRL_FAST
>>> (1 << 6)
>>> include/dt-bindings/pinctrl/am43xx.h:#define SLEWCTRL_FAST
>>> (1 << 19)
>>>
>>> According to the TRM for these processors, the effect of setting
>>> that bit is to select slow slew; fast would be selected by leaving
>>> it cleared. The constants should therefore be named
>>> SLEWCTRL_SLOW.
>>>
>>> This is consistent with the value for the I2C binding constants
>>> I'm converting:
>>>
>>> beagleboard/3.14:arch/arm/boot/dts/am335x-bone-common-pinmux.dtsi:
>>> 0x158 0x72 /* spi0_d1.i2c1_sda, SLEWCTRL_SLOW | INPUT_PULLUP
>>> | MODE2 */
>>> beagleboard/3.14:arch/arm/boot/dts/am335x-bone-common-pinmux.dtsi:
>>> 0x15c 0x72 /* spi0_cs0.i2c1_scl, SLEWCTRL_SLOW | INPUT_PULLUP
>>> | MODE2 */
>>>
>>> except that in the official files we have something like:
>>>
>>> stable/linux-3.14.y:arch/arm/boot/dts/am43x-epos-evm.dts: 0x188
>>> (PIN_INPUT_PULLUP | SLEWCTRL_FAST | MUX_MODE0) /*
>>> i2c0_sda.i2c0_sda */
>>> stable/linux-3.14.y:arch/arm/boot/dts/am43x-epos-evm.dts: 0x18c
>>> (PIN_INPUT_PULLUP | SLEWCTRL_FAST | MUX_MODE0) /*
>>> i2c0_scl.i2c0_scl */
>>>
>>> which is either wrong or misleading.
>>>
>>> Peter
>> --
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti
>>
next prev parent reply other threads:[~2014-10-08 23:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 23:17 mis-definition of SLEWCTRL_FAST in dt-bindings amxxxx header Peter A. Bigot
2014-09-17 12:17 ` Peter A. Bigot
2014-10-07 20:58 ` Denys Dmytriyenko
2014-10-08 23:53 ` Peter A. Bigot [this message]
[not found] <549D8379.2060800@inventec.ch>
2014-12-26 16:29 ` Peter A. Bigot
2015-01-09 21:46 ` Denys Dmytriyenko
2015-01-09 23:02 ` Peter A. Bigot
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=5435CE8F.3020500@pabigot.com \
--to=pab@pabigot.com \
--cc=denis@denix.org \
--cc=meta-ti@yoctoproject.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 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.