From: Frank Wunderlich <linux@fw-web.de>
To: linux-mediatek@lists.infradead.org
Cc: devicetree@vger.kernel.org,
Frank Wunderlich <frank-w@public-files.de>,
Linus Walleij <linus.walleij@linaro.org>,
Sean Wang <sean.wang@kernel.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/3] add available pwm for bananapi-r64
Date: Fri, 16 Oct 2020 22:40:16 +0200 [thread overview]
Message-ID: <20201016204019.2606-1-linux@fw-web.de> (raw)
From: Frank Wunderlich <frank-w@public-files.de>
- mt7622 provides 6 pwm channels and only one is configured in dts
- pinctl-driver contains 7 pwm-channels where one is currently used.
- Mediatek confirmed that pwm7 does not exist and so dts is wrong
and also the pinctrl definitions.
Frank Wunderlich (3):
dts64: mt7622: enable all pwm for bananapi r64
dts64: mt7622: disable spi1 and uart2 because pins are used by pwm
pinctl: mt7622: drop pwm ch7 as mt7622 only has 6 channels
.../boot/dts/mediatek/mt7622-bananapi-bpi-r64.dts | 13 ++++++++-----
drivers/pinctrl/mediatek/pinctrl-mt7622.c | 13 +------------
2 files changed, 9 insertions(+), 17 deletions(-)
--
2.25.1
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next reply other threads:[~2020-10-16 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 20:40 Frank Wunderlich [this message]
2020-10-16 20:40 ` [RFC 1/3] dts64: mt7622: enable all pwm for bananapi r64 Frank Wunderlich
2020-11-27 16:07 ` Matthias Brugger
2020-10-16 20:40 ` [RFC 2/3] dts64: mt7622: disable spi1 and uart2 because pins are used by pwm Frank Wunderlich
2020-10-16 20:40 ` [RFC 3/3] pinctl: mt7622: drop pwm ch7 as mt7622 only has 6 channels Frank Wunderlich
2020-10-29 17:09 ` Linus Walleij
2020-10-30 18:36 ` Sean Wang
2020-11-06 13:40 ` Linus Walleij
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=20201016204019.2606-1-linux@fw-web.de \
--to=linux@fw-web.de \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@kernel.org \
/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).