From: Andrew Jeffery <andrew@aj.id.au>
To: linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH 2/3] aspeed/pinctrl: Fix simultaneous RS-232 / PWM and DVO outputs on AST2500 devices
Date: Wed, 01 May 2019 22:05:09 -0400 [thread overview]
Message-ID: <f35bf045-48e4-432f-8239-29f8f6746158@www.fastmail.com> (raw)
In-Reply-To: <1890791123.3393899.1556750986902.JavaMail.zimbra@raptorengineeringinc.com>
On Thu, 2 May 2019, at 08:20, Timothy Pearson wrote:
> There appears to be a small error in the pinmux table on pages 130 and
> 131 of the AST2500 datasheet v1.6. Specifically, the COND2 requirement
> used to mux the surrounding pins to DVI was inadvertently replicated to
> pins V1, W1, V2, and W2 in the table, which do not incorporate DVI
> functionality.
>
> As a result of this error, both serial TX lines and the PWM 0/1 outputs
> were overriding the VPO pinmux settings when VPO was enabled in the
> pinmux hogs.
>
> This patch has been verified to function on Blackbird hardware. Both
> serial TXD pins and PWM0/PWM1 were functionally tested with SCU94[1:0]
> set to 0x1.
>
> Signed-off-by: Timothy Pearson <tpearson@raptorengineering.com>
> ---
> drivers/pinctrl/aspeed/pinctrl-aspeed-g5.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pinctrl/aspeed/pinctrl-aspeed-g5.c
> b/drivers/pinctrl/aspeed/pinctrl-aspeed-g5.c
> index 187abd7693cf..6f357a11e89a 100644
> --- a/drivers/pinctrl/aspeed/pinctrl-aspeed-g5.c
> +++ b/drivers/pinctrl/aspeed/pinctrl-aspeed-g5.c
> @@ -696,14 +696,14 @@ FUNC_GROUP_DECL(NRTS1, P3);
> #define V1 94
> #define V1_DESC SIG_DESC_SET(SCU84, 22)
> SIG_EXPR_LIST_DECL_SINGLE(DASHV1, DASHV1, VPIRSVD_DESC, V1_DESC);
> -SIG_EXPR_LIST_DECL_SINGLE(TXD1, TXD1, V1_DESC, COND2);
> +SIG_EXPR_LIST_DECL_SINGLE(TXD1, TXD1, V1_DESC);
> MS_PIN_DECL(V1, GPIOL6, DASHV1, TXD1);
> FUNC_GROUP_DECL(TXD1, V1);
>
> #define W1 95
> #define W1_DESC SIG_DESC_SET(SCU84, 23)
> SIG_EXPR_LIST_DECL_SINGLE(DASHW1, DASHW1, VPIRSVD_DESC, W1_DESC);
> -SIG_EXPR_LIST_DECL_SINGLE(RXD1, RXD1, W1_DESC, COND2);
> +SIG_EXPR_LIST_DECL_SINGLE(RXD1, RXD1, W1_DESC);
> MS_PIN_DECL(W1, GPIOL7, DASHW1, RXD1);
> FUNC_GROUP_DECL(RXD1, W1);
>
> @@ -766,14 +766,14 @@ FUNC_GROUP_DECL(RXD2, T5);
> #define V2 104
> #define V2_DESC SIG_DESC_SET(SCU88, 0)
> SIG_EXPR_LIST_DECL_SINGLE(DASHN0, DASHN0, VPIRSVD_DESC, V2_DESC);
> -SIG_EXPR_LIST_DECL_SINGLE(PWM0, PWM0, V2_DESC, COND2);
> +SIG_EXPR_LIST_DECL_SINGLE(PWM0, PWM0, V2_DESC);
> MS_PIN_DECL(V2, GPION0, DASHN0, PWM0);
> FUNC_GROUP_DECL(PWM0, V2);
>
> #define W2 105
> #define W2_DESC SIG_DESC_SET(SCU88, 1)
> SIG_EXPR_LIST_DECL_SINGLE(DASHN1, DASHN1, VPIRSVD_DESC, W2_DESC);
> -SIG_EXPR_LIST_DECL_SINGLE(PWM1, PWM1, W2_DESC, COND2);
> +SIG_EXPR_LIST_DECL_SINGLE(PWM1, PWM1, W2_DESC);
> MS_PIN_DECL(W2, GPION1, DASHN1, PWM1);
> FUNC_GROUP_DECL(PWM1, W2);
This looks reasonable to me. I'd like Ryan to chime in though.
Ryan, can you confirm the datasheet needs correction here?
Tim: You need to send these to a broader audience than the linux-aspeed@
list. Please use ./scripts/get_maintainer.pl to determine the appropriate
people to send to. This at least needs to go to Linus Walleij, who maintains
pinctrl.
Andrew
>
> --
> 2.11.0
>
>
next prev parent reply other threads:[~2019-05-02 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 22:49 [PATCH 2/3] aspeed/pinctrl: Fix simultaneous RS-232 / PWM and DVO outputs on AST2500 devices Timothy Pearson
2019-05-02 2:05 ` Andrew Jeffery [this message]
2019-05-02 3:06 ` Ryan Chen
2019-05-02 3:34 ` Timothy Pearson
2019-05-02 3:47 ` Ryan Chen
2019-05-02 4:05 ` Andrew Jeffery
2019-05-02 4:58 ` Ryan Chen
2019-05-02 5:36 ` Andrew Jeffery
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=f35bf045-48e4-432f-8239-29f8f6746158@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=linux-aspeed@lists.ozlabs.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