linux-kernel - Re: [PATCH 1/3] cs5535-gpio: add AMD CS5535/CS5536 GPIO driver support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090823112214.3adca590@i1501.lan.towertech.it>
Date:	Sun, 23 Aug 2009 11:22:14 +0200
From:	Alessandro Zummo <alessandro.zummo@...ertech.it>
To:	Andres Salomon <dilinger@...labora.co.uk>
Cc:	akpm@...ux-foundation.org, deepak@...top.org,
	Tobias_Mueller@...m.info, Takashi Iwai <tiwai@...e.de>,
	linux-kernel@...r.kernel.org, cjb@...top.org,
	linux-geode@...ts.infradead.org
Subject: Re: [PATCH 1/3] cs5535-gpio: add AMD CS5535/CS5536 GPIO driver
 support

On Tue, 18 Aug 2009 17:53:14 -0400
Andres Salomon <dilinger@...labora.co.uk> wrote:

> 
> This creates a CS5535/CS5536 GPIO driver which uses a gpio_chip backend
> (allowing GPIO users to use the generic GPIO API if desired) while also
> allowing architecture-specific users directly (via the cs5535_gpio_*
> functions).
> 
> Tested on an OLPC machine.  Some Leemotes also use CS5536 (with a mips
> cpu), which is why this is in drivers/gpio rather than arch/x86.
> Currently, it conflicts with older geode GPIO support; once MFGPT support
> is reworked to also be more generic, the older geode code will be removed.
> 
> Signed-off-by: Andres Salomon <dilinger@...labora.co.uk>

 fwiw,

 Reviewed-by: Alessandro Zummo <a.zummo@...ertech.it>

> +	dev_info(&pdev->dev, "allocated PCI BAR #%d: base 0x%llx\n", GPIO_BAR,
> +			(unsigned long long) cs5535_gpio_chip.base);

 shouldn't this be dev_dbg ?

> 
> +	/* finally, register with the generic GPIO API */
> +	err = gpiochip_add(&cs5535_gpio_chip.chip);
> +	if (err) {
> +		dev_err(&pdev->dev, "failed to register gpio chip\n");

 gpiochip_add already uses pr_err for error conditions, there's no need
 to report twice.

> +		goto release_region;
> +	}
> +
> +	printk(KERN_INFO DRV_NAME ": GPIO support successfully loaded.\n");

 I'd use dev_xxx here, maybe it's worth to have a generic one
 in gpiochip_add .


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/