[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DHBCJbfS2Lt7R-3J_TUJi1is2Xn6n5iZkRwvmn5i6Dmg@mail.gmail.com>
Date: Tue, 31 Mar 2020 10:42:33 -0300
From: Fabio Estevam <festevam@...il.com>
To: Robert Foss <robert.foss@...aro.org>
Cc: Dongchun Zhu <dongchun.zhu@...iatek.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Sakari Ailus <sakari.ailus@....fi>,
Tomasz Figa <tfiga@...omium.org>,
linux-media <linux-media@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [v2 2/3] media: ov8856: Add devicetree support
Hi Robert,
On Tue, Mar 31, 2020 at 10:37 AM Robert Foss <robert.foss@...aro.org> wrote:
> After testing this change, it breaks the driver during probing.
Why exactly does it break probing? Maybe the GPIO polarity defined in
the device tree is wrong?
> I had a quick look into GPIOD_OUT_HIGH & LOW definitions, and they
> seem to never be 0 or 1.
If you do a grep in all gpiod_set_value_cansleep() usages in the
kernel tree, there is not a single case where GPIOD_OUT_HIGH or
GPIOD_OUT_LOW is passed as argument of gpiod_set_value_cansleep().
Powered by blists - more mailing lists