SUPERH platform development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 13/64] sh-pfc: r8a7779: Add USB0 and USB1 PENC pinmux support
Date: Mon, 06 May 2013 22:43:56 +0000	[thread overview]
Message-ID: <5188322C.1090600@cogentembedded.com> (raw)
In-Reply-To: <1362740544-19164-14-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hello.

On 03/08/2013 02:01 PM, Laurent Pinchart wrote:

> The USB0 and USB1 PENC functions were missing. Add them.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
>   drivers/pinctrl/sh-pfc/pfc-r8a7779.c | 6 +++++-
>   1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a7779.c b/drivers/pinctrl/sh-pfc/pfc-r8a7779.c
> index 492832c..4ab7b11 100644
> --- a/drivers/pinctrl/sh-pfc/pfc-r8a7779.c
> +++ b/drivers/pinctrl/sh-pfc/pfc-r8a7779.c
> @@ -429,7 +429,8 @@ enum {
>   	A0_MARK, SD1_DAT3_MARK, MMC0_D3_MARK, FD3_MARK,
>   	BS_MARK, SD1_DAT2_MARK, MMC0_D2_MARK, FD2_MARK,
>   	ATADIR0_MARK, SDSELF_MARK, HCTS1_MARK, TX4_C_MARK,
> -	USB_PENC2_MARK, SCK0_MARK, PWM1_MARK, PWMFSW0_MARK,
> +	USB_PENC0_MARK, USB_PENC1_MARK, USB_PENC2_MARK,

    PENCn pins don't have USB_ prefix in the manual, so somebody 
deliberately added
it before to FN_USB_PENC. That probably contributed to further confusion 
where PENCn
were grouped together with USB_OVCn  -- which are usually unused and are 
3.3V
alternatives of OVCn 5V pins (which are not multiplexed at all).

WBR, Sergei


  reply	other threads:[~2013-05-06 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 11:01 [PATCH v3 13/64] sh-pfc: r8a7779: Add USB0 and USB1 PENC pinmux support Laurent Pinchart
2013-05-06 22:43 ` Sergei Shtylyov [this message]
2013-05-07 22:18 ` Sergei Shtylyov

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=5188322C.1090600@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=linux-sh@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