public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 01/05] sh: Add GPIO and pinmux base code
Date: Sat, 27 Sep 2008 18:39:32 +0000	[thread overview]
Message-ID: <20080927183931.GA31801@linux-sh.org> (raw)
In-Reply-To: <20080927181016.11246.72087.sendpatchset@rx1.opensource.se>

On Sun, Sep 28, 2008 at 03:10:16AM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@igel.co.jp>
> 
> This patch adds the pinmux table parser and gpiolib glue.
> The old SH3 header code is removed.
> 
> Signed-off-by: Magnus Damm <damm@igel.co.jp>

For starters, I don't know why you decided to kill off the SH-3 gpio
header. It's still in active use by the magicpanelr2 board. Once 7720 and
mpr2 are converted over, then we can kill off the header, but not before
that. Although I suppose we can just fix up the board header to use
cpu-sh3/cpu/gpio.h explicitly.

> --- 0001/arch/sh/include/asm/gpio.h
> +++ work/arch/sh/include/asm/gpio.h	2008-09-28 02:03:40.000000000 +0900
> @@ -1,19 +1,119 @@
>  /*
> - *  include/asm-sh/gpio.h
> + * Generic GPIO API using gpiolib and pinmux table support for SuperH.
>   *
> - *  Copyright (C) 2007 Markus Brunner, Mark Jonas
> + * Copyright (c) 2008 Magnus Damm
>   *
> - *  Addresses for the Pin Function Controller
> + * Generic GPIO derived from x86 version:
> + * Copyright (c) 2007-2008  MontaVista Software, Inc.
> + * Author: Anton Vorontsov <avorontsov@ru.mvista.com>
>   *
> - * This file is subject to the terms and conditions of the GNU General Public
> - * License.  See the file "COPYING" in the main directory of this archive
> - * for more details.
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
>   */
>  #ifndef __ASM_SH_GPIO_H
>  #define __ASM_SH_GPIO_H
>  
I wouldn't bother with the header comments at all, there's nothing
profound here and it's almost all pinmux stuff anyways.

> +static int read_write_reg(unsigned long reg, unsigned long reg_width,
> +			  unsigned long field_width, unsigned long in_pos,
> +			  unsigned long value, int do_write)
> +{
> +	unsigned long flags, data, mask, pos;
> +
> +	flags = 0; /* kill silly warning */
> +	data = 0;
> +	mask = (1 << field_width) - 1;
> +	pos = reg_width - ((in_pos + 1) * field_width);
> +
> +#ifdef DEBUG
> +	pr_info("sh pinmux: %s, addr = %lx, value = %ld, pos = %ld, "
> +		"r_width = %ld, f_width = %ld\n",
> +		do_write ? "write" : "read", reg, value, pos,
> +		reg_width, field_width);
> +#endif
> +
> +	if (do_write)
> +		spin_lock_irqsave(&gpio_register_lock, flags);
> +
The locking here is a bit non-obvious, and should be commented. I had to
read through this a couple of times to figure out what it was supposed to
be doing. You seem to be trying to use a spinlock as a rwlock, which is a
bit error prone to say the least.

  reply	other threads:[~2008-09-27 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-27 18:10 [PATCH 01/05] sh: Add GPIO and pinmux base code Magnus Damm
2008-09-27 18:39 ` Paul Mundt [this message]
2008-09-29  3:34 ` Magnus Damm

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=20080927183931.GA31801@linux-sh.org \
    --to=lethal@linux-sh.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