From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: gregkh@linuxfoundation.org
Cc: neil@brown.name, driverdev-devel@linuxdriverproject.org, gerg@kernel.org
Subject: [PATCH 0/2] staging: mt7621-pci: make gpios 8 and 9 vendor specific
Date: Sat, 21 Mar 2020 08:26:48 +0100 [thread overview]
Message-ID: <20200321072650.7784-1-sergio.paracuellos@gmail.com> (raw)
According to this:
* http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2020-March/142533.html
Gpio's 8 and 9 must be vendor specific and properly be set up
in device tree specific vendor file.
After this changes release part in the driver is not needed anymore
because we rely in the fact that device tree is correct.
This changes have been tested in a gnubee pc1.
Sergio Paracuellos (2):
staging: mt7621-dts: gpio 8 and 9 are vendor specific
staging: mt7621-pci: delete release gpios related code
drivers/staging/mt7621-dts/gbpc1.dts | 4 ++++
drivers/staging/mt7621-dts/mt7621.dtsi | 4 +---
drivers/staging/mt7621-pci/pci-mt7621.c | 27 +++++++------------------
3 files changed, 12 insertions(+), 23 deletions(-)
--
2.25.1
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2020-03-21 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 7:26 Sergio Paracuellos [this message]
2020-03-21 7:26 ` [PATCH 1/2] staging: mt7621-dts: gpio 8 and 9 are vendor specific Sergio Paracuellos
2020-03-21 7:26 ` [PATCH 2/2] staging: mt7621-pci: delete release gpios related code Sergio Paracuellos
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=20200321072650.7784-1-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gerg@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=neil@brown.name \
/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).