From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [RESEND PATCH 2/3] pinctrl: renesas: Make sure the pin type is updated after setting the MUX
Date: Wed, 4 Nov 2020 20:22:02 +0100 [thread overview]
Message-ID: <8fad03e3-8f34-e158-028c-aaad8b2a4ebf@gmail.com> (raw)
In-Reply-To: <20201104172706.473-3-prabhakar.mahadev-lad.rj@bp.renesas.com>
On 11/4/20 6:27 PM, Lad Prabhakar wrote:
> Update pin type after every successful call to sh_pfc_config_mux().
>
> This fixes pin functionality from being overwritten.
Can you please provide more details about the problem you are fixing
here ? What is the problem ? What triggers it ?
next prev parent reply other threads:[~2020-11-04 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 17:27 [RESEND PATCH 0/3] pinctrl: renesas: trivial fixes and enhancements Lad Prabhakar
2020-11-04 17:27 ` [RESEND PATCH 1/3] pinctrl: renesas: Drop unused members from struct sh_pfc_pinctrl Lad Prabhakar
2020-11-04 19:22 ` Marek Vasut
2020-11-04 17:27 ` [RESEND PATCH 2/3] pinctrl: renesas: Make sure the pin type is updated after setting the MUX Lad Prabhakar
2020-11-04 19:22 ` Marek Vasut [this message]
2020-11-05 10:09 ` Lad, Prabhakar
2020-11-04 17:27 ` [RESEND PATCH 3/3] pinctrl: renesas: Implement get_pin_muxing() callback Lad Prabhakar
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=8fad03e3-8f34-e158-028c-aaad8b2a4ebf@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.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