mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch -mm 13/20] chardev: GPIO for SCx200 & PC-8736x:  add new pc8736x_gpio module
Date: Mon, 19 Jun 2006 22:22:10 -0700	[thread overview]
Message-ID: <20060619222210.f275dde7.akpm@osdl.org> (raw)
In-Reply-To: <44944B3D.8040604@gmail.com>

On Sat, 17 Jun 2006 12:34:37 -0600
Jim Cromie <jim.cromie@gmail.com> wrote:

> --- ax-12/drivers/char/pc8736x_gpio.c	1969-12-31 17:00:00.000000000 -0700
> +++ ax-13/drivers/char/pc8736x_gpio.c	2006-06-17 01:39:58.000000000 -0600
> @@ -0,0 +1,295 @@
> +/* linux/drivers/char/pc8736x_gpio.c
> +
> +   National Semiconductor PC8736x GPIO driver.  Allows a user space
> +   process to play with the GPIO pins.
> +
> +   Copyright (c) 2005 Jim Cromie <jim.cromie@gmail.com>
> +
> +   adapted from linux/drivers/char/scx200_gpio.c
> +   Copyright (c) 2001,2002 Christer Weinigel <wingel@nano-system.com>,
> +*/
> +
> +#include <linux/config.h>
> +#include <linux/fs.h>
> +#include <linux/module.h>
> +#include <linux/errno.h>
> +#include <linux/kernel.h>
> +#include <linux/init.h>
> +#include <linux/ioport.h>
> +#include <linux/nsc_gpio.h>
> +#include <asm/uaccess.h>
> +#include <asm/io.h>

New code should use linux/io.h and linux/uaccess.h.  It won't matter in
this case, but you might pick up some goodies in the future.

> +#define NAME "pc8736x_gpio"
> +
> +MODULE_AUTHOR("Jim Cromie <jim.cromie@gmail.com>");
> +MODULE_DESCRIPTION("NatSemi SCx200 GPIO Pin Driver");
> +MODULE_LICENSE("GPL");
> +
> +static int major = 0;		/* default to dynamic major */

Unneeded initialisation.

> +static int pc8736x_superio_present(void)
> +     /* try the 2 possible values, read a hardware reg to verify */
> +{

weird comment placement.

> +extern void nsc_gpio_dump(unsigned iminor);

Goes in a .h file.

> +static int __init pc8736x_gpio_init(void)
> +{
> +	int r, rc;
> +
> +	printk(KERN_DEBUG NAME " initializing\n");
> +
> +	if (!pc8736x_superio_present()) {
> +		printk(KERN_ERR NAME ": no device found\n");
> +		return -ENODEV;
> +	}
> +
> +	/* Verify that chip and it's GPIO unit are both enabled.
> +	   My BIOS does this, so I take minimum action here
> +	 */
> +	rc = superio_inb(SIO_CF1);
> +	if (!(rc & 0x01)) {
> +		printk(KERN_ERR NAME ": device not enabled\n");
> +		return -ENODEV;
> +	}
> +	device_select(SIO_GPIO_UNIT);
> +	if (!superio_inb(SIO_UNIT_ACT)) {
> +		printk(KERN_ERR NAME ": GPIO unit not enabled\n");
> +		return -ENODEV;
> +	}
> +
> +	/* read GPIO unit base address */
> +	pc8736x_gpio_base = (superio_inb(SIO_BASE_HADDR) << 8
> +			     | superio_inb(SIO_BASE_LADDR));
> +
> +	if (request_region(pc8736x_gpio_base, 16, NAME))
> +		printk(KERN_INFO NAME ": GPIO ioport %x reserved\n",
> +		       pc8736x_gpio_base);

Isn't this fatal?  If this IO region is in use by some other device, we
don't want this driver poking at it?


> +	r = register_chrdev(major, NAME, &pc8736x_gpio_fops);
> +	if (r < 0) {
> +		printk(KERN_ERR NAME ": unable to register character device\n");
> +		return r;

release_region()?

undo that device_select()?

> +	}
> +	if (!major) {
> +		major = r;
> +		printk(KERN_DEBUG NAME ": got dynamic major %d\n", major);
> +	}
> +
> +	return 0;
> +}
> +
> +static void __exit pc8736x_gpio_cleanup(void)
> +{
> +	printk(KERN_DEBUG NAME " cleanup\n");
> +
> +	release_region(pc8736x_gpio_base, 16);
> +
> +	unregister_chrdev(major, NAME);
> +}

No need to shut down any hardware here?



  reply	other threads:[~2006-06-20  5:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <448DB57F.2050006@gmail.com>
     [not found] ` <cfe85dfa0606121150y369f6beeqc643a1fe5c7ce69b@mail.gmail.com>
2006-06-17 18:23   ` [patch -mm 01/20] chardev: GPIO for SCx200 & PC-8736x: whitespace pre-clean Jim Cromie
2006-06-17 18:24   ` [patch -mm 02/20] chardev: GPIO for SCx200 & PC-8736x: modernize driver init to 2.6 api Jim Cromie
2006-06-20  5:21     ` Andrew Morton
2006-06-17 18:25   ` [patch -mm 03/20] chardev: GPIO for SCx200 & PC-8736x: add platforn_device for use w dev_dbg Jim Cromie
2006-06-20  5:22     ` Andrew Morton
2006-06-17 18:26   ` [patch -mm 04/20] chardev: GPIO for SCx200 & PC-8736x: device minor numbers are unsigned ints Jim Cromie
2006-06-17 18:27   ` [patch -mm 05/20] chardev: GPIO for SCx200 & PC-8736x: put gpio_dump on a diet Jim Cromie
2006-06-20  5:22     ` Andrew Morton
2006-06-17 18:28   ` [patch -mm 06/20] chardev: GPIO for SCx200 & PC-8736x: add 'v' command to device-file Jim Cromie
2006-06-17 18:29   ` [patch -mm 07/20] chardev: GPIO for SCx200 & PC-8736x: refactor scx200_probe to better segregate _gpio initialization Jim Cromie
2006-06-17 18:30   ` [patch -mm 09/20] chardev: GPIO for SCx200 & PC-8736x: dispatch via vtable Jim Cromie
2006-06-17 18:31   ` [patch -mm 10/20] chardev: GPIO for SCx200 & PC-8736x: add empty common-module Jim Cromie
2006-06-17 18:32   ` [patch -mm 11/20] chardev: GPIO for SCx200 & PC-8736x: migrate file-ops to common module Jim Cromie
2006-06-20  5:22     ` Andrew Morton
2006-06-17 18:33   ` [patch -mm 12/20] chardev: GPIO for SCx200 & PC-8736x: migrate gpio_dump " Jim Cromie
2006-06-17 18:33   ` [patch -mm 08/20] chardev: GPIO for SCx200 & PC-8736x: add gpio-ops vtable Jim Cromie
2006-06-17 18:34   ` [patch -mm 13/20] chardev: GPIO for SCx200 & PC-8736x: add new pc8736x_gpio module Jim Cromie
2006-06-20  5:22     ` Andrew Morton [this message]
2006-06-17 18:35   ` [patch -mm 14/20] chardev: GPIO for SCx200 & PC-8736x: add platform_device for use w dev_dbg Jim Cromie
2006-06-20  5:22     ` Andrew Morton
2006-06-17 18:36   ` [patch -mm 15/20] chardev: GPIO for SCx200 & PC-8736x: use dev_dbg in common module Jim Cromie
2006-06-20  5:22     ` Andrew Morton
2006-06-17 18:37   ` [patch -mm 16/20] chardev: GPIO for SCx200 & PC-8736x: fix gpio_current, use shadow regs Jim Cromie
2006-06-20  5:22     ` Andrew Morton
2006-06-17 18:38   ` [patch -mm 17/20] chardev: GPIO for SCx200 & PC-8736x: replace spinlocks w mutexes Jim Cromie
2006-06-20  5:22     ` Andrew Morton
2006-06-17 18:39   ` [patch -mm 18/20] chardev: GPIO for SCx200 & PC-8736x: display pin values in/out in gpio_dump Jim Cromie
2006-06-17 18:40   ` [patch -mm 19/20] chardev: GPIO for SCx200 & PC-8736x: add proper Kconfig, Makefile entries Jim Cromie
2006-06-17 18:42   ` [patch -mm 20/20 RFC] chardev: GPIO for SCx200 & PC-8736x: add sysfs-GPIO interface Jim Cromie
2006-06-20  5:22     ` Andrew Morton
2006-06-20 19:57       ` Jim Cromie
2006-06-20 20:14         ` Randy.Dunlap
2006-06-20 20:40           ` Jim Cromie
2006-06-20 20:52             ` Randy.Dunlap
2006-06-20 21:50               ` Jim Cromie
2006-06-20 22:52                 ` Randy.Dunlap
2006-06-21  0:12         ` Andrew Morton
2006-06-21  3:49     ` Randy.Dunlap

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=20060619222210.f275dde7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=jim.cromie@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®