From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: linus.walleij@linaro.org, geert+renesas@glider.be
Cc: linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: [PATCH v2 0/3] pinctrl: sh-pfc: Rollback to mux if requires when the gpio is freed
Date: Thu, 8 Aug 2019 15:19:00 +0900 [thread overview]
Message-ID: <1565245143-15018-1-git-send-email-yoshihiro.shimoda.uh@renesas.com> (raw)
This patch series is based on renesas-drivers.git /
renesas-drivers-2019-07-30-v5.3-rc2 tag.
About R-Car PWM driver modification, it seems to need more time to achieve
output duty zero about suitable gpio vs pinctrl handling. But, I believe
this pinctrl patches could be applied into the mainline regardless
the R-Car PWM modification.
Changes from v1:
- Spin-off the pinctrl patches (from 1/7 to 3/7).
- Add Geert-san's Reviewed-by on 1/3 and 2/3.
- Add Fixes tag on 2/3.
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=143129
Yoshihiro Shimoda (3):
pinctrl: sh-pfc: add new flags into struct sh_pfc_pin_config
pinctrl: sh-pfc: remove incomplete flag "cfg->type"
pinctrl: sh-pfc: Rollback to mux if requires when the gpio is freed
drivers/pinctrl/sh-pfc/pinctrl.c | 45 ++++++++++++++++++++--------------------
1 file changed, 23 insertions(+), 22 deletions(-)
--
2.7.4
next reply other threads:[~2019-08-08 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 6:19 Yoshihiro Shimoda [this message]
2019-08-08 6:19 ` [PATCH v2 1/3] pinctrl: sh-pfc: add new flags into struct sh_pfc_pin_config Yoshihiro Shimoda
2019-08-09 18:52 ` Simon Horman
2019-08-08 6:19 ` [PATCH v2 2/3] pinctrl: sh-pfc: remove incomplete flag "cfg->type" Yoshihiro Shimoda
2019-08-09 18:52 ` Simon Horman
2019-08-08 6:19 ` [PATCH v2 3/3] pinctrl: sh-pfc: Rollback to mux if requires when the gpio is freed Yoshihiro Shimoda
2019-08-08 8:29 ` Geert Uytterhoeven
2019-08-23 7:10 ` Geert Uytterhoeven
2019-08-09 18:52 ` Simon Horman
2019-08-08 8:31 ` [PATCH v2 0/3] " Geert Uytterhoeven
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=1565245143-15018-1-git-send-email-yoshihiro.shimoda.uh@renesas.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.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).