linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Simon Horman <horms@verge.net.au>,
	linux-sh@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] pinctrl: sh-pfc: Get rid of CONFIG_SHMOBILE_LEGACY
Date: Fri, 28 Aug 2015 22:02:12 +0000	[thread overview]
Message-ID: <1519243.Gb6txjtt2n@avalon> (raw)
In-Reply-To: <1440705812-2960-1-git-send-email-geert+renesas@glider.be>

Hi Geert,

Thank you for the patch.

On Thursday 27 August 2015 22:03:32 Geert Uytterhoeven wrote:
> Shmobile is all multiplatform these days, so get rid of the reference to
> CONFIG_ARCH_SHMOBILE_LEGACY.
> 
> Move the legacy code to do the non-DT mapping between GPIOs and pins
> inside the existing #ifdef CONFIG_SUPERH section.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> ---
>   - Against renesas-devel-20150826-v4.2-rc8,
>   - This must not be applied to a branch that still has
>     CONFIG_SHMOBILE_LEGACY.
> 
>  drivers/pinctrl/sh-pfc/gpio.c | 41 ++++++++++++++++++---------------------
>  1 file changed, 19 insertions(+), 22 deletions(-)
> 
> diff --git a/drivers/pinctrl/sh-pfc/gpio.c b/drivers/pinctrl/sh-pfc/gpio.c
> index 685b3c24627daf03..a917c62f07124b0b 100644
> --- a/drivers/pinctrl/sh-pfc/gpio.c
> +++ b/drivers/pinctrl/sh-pfc/gpio.c
> @@ -341,7 +341,6 @@ int sh_pfc_register_gpiochip(struct sh_pfc *pfc)
>  	struct sh_pfc_chip *chip;
>  	phys_addr_t address;
>  	unsigned int i;
> -	int ret;
> 
>  	if (pfc->info->data_regs = NULL)
>  		return 0;
> @@ -379,29 +378,27 @@ int sh_pfc_register_gpiochip(struct sh_pfc *pfc)
>  	if (IS_ENABLED(CONFIG_OF) && pfc->dev->of_node)
>  		return 0;
> 
> -	if (IS_ENABLED(CONFIG_SUPERH) ||
> -	    IS_ENABLED(CONFIG_ARCH_SHMOBILE_LEGACY)) {
> -		/*
> -		 * Register the GPIO to pin mappings. As pins with GPIO ports
> -		 * must come first in the ranges, skip the pins without GPIO
> -		 * ports by stopping at the first range that contains such a
> -		 * pin.
> -		 */
> -		for (i = 0; i < pfc->nr_ranges; ++i) {
> -			const struct sh_pfc_pin_range *range = &pfc->ranges[i];
> -
> -			if (range->start >= pfc->nr_gpio_pins)
> -				break;
> -
> -			ret = gpiochip_add_pin_range(&chip->gpio_chip,
> -				dev_name(pfc->dev), range->start, range->start,
> -				range->end - range->start + 1);
> -			if (ret < 0)
> -				return ret;
> -		}
> +#ifdef CONFIG_SUPERH
> +	/*
> +	 * Register the GPIO to pin mappings. As pins with GPIO ports
> +	 * must come first in the ranges, skip the pins without GPIO
> +	 * ports by stopping at the first range that contains such a
> +	 * pin.
> +	 */
> +	for (i = 0; i < pfc->nr_ranges; ++i) {
> +		const struct sh_pfc_pin_range *range = &pfc->ranges[i];
> +		int ret;
> +
> +		if (range->start >= pfc->nr_gpio_pins)
> +			break;
> +
> +		ret = gpiochip_add_pin_range(&chip->gpio_chip,
> +			dev_name(pfc->dev), range->start, range->start,
> +			range->end - range->start + 1);
> +		if (ret < 0)
> +			return ret;
>  	}
> 
> -#ifdef CONFIG_SUPERH
>  	/* Register the function GPIOs chip. */
>  	if (pfc->info->nr_func_gpios = 0)
>  		return 0;

-- 
Regards,

Laurent Pinchart


      parent reply	other threads:[~2015-08-28 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 20:03 [PATCH] pinctrl: sh-pfc: Get rid of CONFIG_SHMOBILE_LEGACY Geert Uytterhoeven
2015-08-27 20:07 ` [PATCH] pinctrl: sh-pfc: Get rid of CONFIG_ARCH_SHMOBILE_LEGACY Geert Uytterhoeven
2015-09-25 16:14   ` Linus Walleij
2015-08-28 22:02 ` 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=1519243.Gb6txjtt2n@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).