devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2] sh-pfc: add R8A7794 PFC support
Date: Mon, 16 Feb 2015 21:41:31 +0200	[thread overview]
Message-ID: <33139732.2SupcF0KCS@avalon> (raw)
In-Reply-To: <CAMuHMdX-U-JdWhsg9qiA8okKOjQxqLmusah3kcJbzSjzvhbmnA@mail.gmail.com>

Hi Geert,

On Monday 16 February 2015 09:57:09 Geert Uytterhoeven wrote:
> On Sun, Feb 15, 2015 at 5:06 PM, Laurent Pinchart wrote:
> >> --- /dev/null
> >> +++ linux-pinctrl/drivers/pinctrl/sh-pfc/pfc-r8a7794.c
> >> @@ -0,0 +1,3989 @@
> >> +/*
> >> + * r8a7794 processor support - PFC hardware block.
> >> + *
> >> + * Copyright (C) 2014 Renesas Electronics Corporation
> >> + * Copyright (C) 2015 Renesas Solutions Corp.
> >> + * Copyright (C) 2015 Cogent  Embedded, Inc.,
> >> <source@cogentembedded.com>
> >> + *
> >> + * This program is free software; you can redistribute it and/or modify
> >> + * it under the terms of the GNU General Public License version 2
> >> + * as published by the Free Software Foundation.
> >> + */
> >> +
> >> +#include <linux/kernel.h>
> >> +#include <linux/platform_data/gpio-rcar.h>
> >> +
> >> +#include "core.h"
> >> +#include "sh_pfc.h"
> >> +
> >> +#define CPU_ALL_PORT(fn, sfx)                                           
> >>     \ +     PORT_GP_32(0, fn, sfx),                                     
> >>    \ +     PORT_GP_32(1, fn, sfx),                                      
> >>   \ +     PORT_GP_32(2, fn, sfx),                                       
> >>  \ +     PORT_GP_32(3, fn, sfx),                                        
> >> \ +     PORT_GP_32(4, fn, sfx),                                        
> >> \ +     PORT_GP_32(5, fn, sfx),                                        
> >> \ +     PORT_GP_32(6, fn, sfx)
> > 
> > If I'm not mistaken port GP1 has 26 pins only, GP5 28 pins and GP6 26
> > pins.
> 
> That's correct.
> 
> If that has to be reflected in the CPU_ALL_PORT() macro, a few existing pfc
> drivers should be modified, too:
>   - on r8a7790, port GP1 and GP2 have 30 pins only,
>   - on r8a7791, port GP1 has 26 pins only.

Done :-)

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2015-02-16 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 21:01 [PATCH v2] sh-pfc: add R8A7794 PFC support Sergei Shtylyov
2015-02-15 16:06 ` Laurent Pinchart
2015-02-16  8:57   ` Geert Uytterhoeven
2015-02-16 19:41     ` Laurent Pinchart [this message]

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=33139732.2SupcF0KCS@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=geert@linux-m68k.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    /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).