[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DK-K19bHhEpyGoVak5Y7bT-xzA9GjtBSiO6Z+yfeEdgw@mail.gmail.com>
Date: Wed, 30 Mar 2016 09:45:21 -0300
From: Fabio Estevam <festevam@...il.com>
To: Petr Štetiar <ynezz@...e.cz>
Cc: Krzysztof Hałasa <khalasa@...p.pl>,
Marcel Ziswiler <marcel.ziswiler@...adex.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Richard Zhu <Richard.Zhu@...escale.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Stefan Agner <stefan@...er.ch>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Lucas Stach <l.stach@...gutronix.de>
Subject: Re: [PATCH] i.MX6 PCIe: Fix imx6_pcie_deassert_core_reset() polarity
On Wed, Mar 30, 2016 at 9:06 AM, Petr Štetiar <ynezz@...e.cz> wrote:
> I'm really puzzled by this :-) With your patch applied I get following on
> Toradex Apalis modules:
>
> DTS: reset-gpio = <&gpio1 28 GPIO_ACTIVE_LOW>;
> dmesg: imx6q-pcie 1ffc000.pcie: phy link never came up
> gpio: gpio-28 ( |reset ) out hi
> pin voltage: 0V
>
> DTS: reset-gpio = <&gpio1 28 GPIO_ACTIVE_HIGH>;
> dmesg: ath9k 0000:01:00.0: enabling device (0140 -> 0142)
> gpio: gpio-28 ( |reset ) out lo
> pin voltage: 3V3
>
> So Toradex Apalis is actually active-high? Thanks.
Yes, exactly. That's why you need to introduce a new property to
handle the active-high case, so that old dtb's are not broken.
Powered by blists - more mailing lists