[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5CtaphPBXSkuRxX37Zbbx9oogXjy13TsRPgtR6y87gAdA@mail.gmail.com>
Date: Wed, 19 Sep 2018 09:12:40 -0300
From: Fabio Estevam <festevam@...il.com>
To: Michal Vokáč <michal.vokac@...ft.com>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Shawn Guo <shawnguo@...nel.org>,
Fabio Estevam <fabio.estevam@....com>,
Rob Herring <robh+dt@...nel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-fbdev@...r.kernel.org
Subject: Re: [PATCH 2/2] video: ssd1307fb: Do not hard code active-low reset sequence
Hi Michal,
On Wed, Sep 19, 2018 at 6:18 AM, Michal Vokáč <michal.vokac@...ft.com> wrote:
> The SSD130x OLED display reset signal is active low. Now the reset
> sequence is implemented in such a way that users are forced to
> define reset-gpios as GPIO_ACTIVE_HIGH in DT to make the reset work.
>
> Do not hard code the active-low sequence into the driver but instead
> allow the user to specify the gpio as GPIO_ACTIVE_LOW to reflect
> the real world.
>
> The only single in-tree user of the display is converted and builds
> fine.
>
> Signed-off-by: Michal Vokáč <michal.vokac@...ft.com>
> ---
> I am not really sure wheater this should be in one commit or the DT
> changes should be done in separate commit. Just tell me and I will
> split/merge the changes as you want. Thanks.
Please separate in two patches: one for the dts and another for the driver.
Thanks
Powered by blists - more mailing lists