From: Phil Reid <preid@electromag.com.au>
To: gregkh@linuxfoundation.org, bhanusreemahesh@gmail.com,
leobras.c@gmail.com, nsaenzjulienne@suse.de,
nishadkamdar@gmail.com, preid@electromag.com.au,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: [PATCH 0/2] Staging: fbtft: Fix probing of gpio descriptor
Date: Tue, 16 Jul 2019 00:24:35 +0000 [thread overview]
Message-ID: <1563236677-5045-1-git-send-email-preid@electromag.com.au> (raw)
In-Reply-To: <1562833913-10510-1-git-send-email-preid@electromag.com.au>
GPIO probing and reset polarity are broken.
Fix them.
Fixes: c440eee1a7a1 ("Staging: fbtft: Switch to the gpio descriptor interface")
Changes from v2:
- Add fixes tag to "Fix reset assertion when using gpio descriptor"
- Add tested-by / reviewed-by tags
Phil Reid (2):
Staging: fbtft: Fix probing of gpio descriptor
Staging: fbtft: Fix reset assertion when using gpio descriptor
drivers/staging/fbtft/fbtft-core.c | 43 ++++++++++++++++++--------------------
1 file changed, 20 insertions(+), 23 deletions(-)
--
1.8.3.1
next prev parent reply other threads:[~2019-07-16 0:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 8:31 [PATCH 0/2] Staging: fbtft: Fix probing of gpio descriptor Phil Reid
2019-07-11 8:31 ` [PATCH 1/2] " Phil Reid
2019-07-11 8:31 ` [PATCH 2/2] Staging: fbtft: Fix reset assertion when using " Phil Reid
2019-07-15 14:27 ` [PATCH 0/2] Staging: fbtft: Fix probing of " Nicolas Saenz Julienne
2019-07-16 0:24 ` Phil Reid [this message]
2019-07-16 0:24 ` [PATCH v2 1/2] " Phil Reid
2019-07-16 0:24 ` [PATCH v2 2/2] Staging: fbtft: Fix reset assertion when using " Phil Reid
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=1563236677-5045-1-git-send-email-preid@electromag.com.au \
--to=preid@electromag.com.au \
--cc=bhanusreemahesh@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=leobras.c@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=nishadkamdar@gmail.com \
--cc=nsaenzjulienne@suse.de \
/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).