linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: davidb@codeaurora.org, "David S. Miller" <davem@davemloft.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Bryan Huntsman <bryanh@codeaurora.org>,
	Daniel Walker <dwalker@fifo99.com>,
	David Collins <collinsd@codeaurora.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Joe Perches <joe@perches.com>,
	Russell King <linux@arm.linux.org.uk>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Stepan Moskovchenko <stepanm@codeaurora.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Linus Walleij <linux.walleij@sterricsson.com>,
	Thomas Glexiner <tglx@linutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Qualcomm PM8921 MFD v2 3/6] gpio: pm8xxx-gpio: Add pm8xxx gpio driver
Date: Wed, 16 Mar 2011 11:55:19 -0700	[thread overview]
Message-ID: <4D810797.4090000@codeaurora.org> (raw)
In-Reply-To: <20110312093645.GL9347@angua.secretlab.ca>


>>
>> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
>> index 664660e..c5e6f51 100644
>> --- a/drivers/gpio/Kconfig
>> +++ b/drivers/gpio/Kconfig
>> @@ -411,4 +411,14 @@ config GPIO_JANZ_TTL
>>  	  This driver provides support for driving the pins in output
>>  	  mode only. Input mode is not supported.
>>  
>> +comment "SSBI GPIO expanders:"
> 
> SSBI?  Also, the comment seems rather out of place when there
> currently appears to only be one of such devices.

SSBI is a bus architecture used to access this device's register 
(actually this is a subdevice in the pmic and ssbi is used to access all 
the registers in the pmic).The bus driver can be found here
https://patchwork.kernel.org/patch/601771/

It didnt occur to me that the comment is only meant for buses which have 
more than one gpio devices. I saw
comment "MODULbus GPIO expanders:"
comment "AC97 GPIO expanders:"
both containing single devices and thought it is a norm to add a comment 
  if a device running on a new bus is introduced.

Let me know if you still think I should remove
comment "SSBI GPIO expanders:" ?

>> +
>> +struct pm_gpio_chip {
>> +	struct list_head	link;
>> +	struct gpio_chip	gpio_chip;
>> +	struct mutex		pm_lock;
>> +	u8			*bank1;
>> +	int			irq_base;
>> +};
>> +
>> +static LIST_HEAD(pm_gpio_chips);
> 
> Looks like you need a mutex for protecting this list from mutual access.

Yes will fix this.

> 
>> +

>> +#ifndef __PM8XXX_GPIO_H
>> +#define __PM8XXX_GPIO_H
>> +
>> +#include <linux/errno.h>
>> +
>> +#define PM8XXX_GPIO_DEV_NAME	"pm8xxx-gpio"
>> +
>> +struct pm8xxx_gpio_core_data {
>> +	u32	rev;
>> +	int	ngpios;
>> +};
>> +
>> +struct pm8xxx_gpio_platform_data {
>> +	struct pm8xxx_gpio_core_data	gpio_cdata;
>> +	int				gpio_base;
>> +};
> 
> There doesn't seem to be any value it splitting pm8xxx_gpio_core_data
> into a separate structure from what I see in this patch.  How is this
> going to be used?

gpio_base comes from the platform data because the board file knows 
where in the global gpio numbers the pm8xxx gpio start. For example if 
the MSM code supports 150 gpios(0 through 149), the board file will set 
gpio_base to indicate pm8xxx gpios should start from 150.

The pm8xxx_gpio_core_data is meant to be filled in by the pm8921 core. 
We have different pmic chips with similar gpio implementations. For 
example 8058 pmic, 8901 pmic and 8921 pmic, all  have the same gpio 
implementation but different number of gpio lines. The pm8xxx-gpio.c is 
used for all these pmics. Hence we separated core specific gpio 
information (number of gpio lines supported) from board specific gpio 
information (where in the global map the gpio number for this device 
starts).

--
Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm 
Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-03-16 18:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  6:09 [Qualcomm PM8921 MFD v2 0/6] pmic 8921 core and subdevices adharmap
2011-03-08  6:09 ` [Qualcomm PM8921 MFD v2 1/6] mfd: pm8921: Add PMIC 8921 core driver adharmap
2011-03-08 17:58   ` Randy Dunlap
2011-03-08  6:09 ` [Qualcomm PM8921 MFD v2 2/6] mfd: pm8xxx: Add irq support adharmap
2011-03-08 12:04   ` Thomas Gleixner
2011-03-09  5:21     ` Abhijeet Dharmapurikar
2011-03-10 10:32       ` Thomas Gleixner
2011-03-11  4:43         ` Abhijeet Dharmapurikar
2011-03-11 17:57           ` Thomas Gleixner
2011-03-11 19:02             ` Abhijeet Dharmapurikar
2011-03-11 19:43               ` Thomas Gleixner
2011-03-11 19:57                 ` Mark Brown
2011-03-11 20:12                   ` Thomas Gleixner
2011-03-11 20:06                 ` Abhijeet Dharmapurikar
2011-03-11 20:37                   ` Thomas Gleixner
2011-03-12  0:13                     ` Abhijeet Dharmapurikar
2011-03-12 10:18                     ` [tip:irq/core] genirq: Add chip flag to force mask on suspend tip-bot for Thomas Gleixner
2011-03-08  6:09 ` [Qualcomm PM8921 MFD v2 3/6] gpio: pm8xxx-gpio: Add pm8xxx gpio driver adharmap
2011-03-12  9:36   ` Grant Likely
2011-03-16 18:55     ` Abhijeet Dharmapurikar [this message]
2011-03-16 19:54       ` Grant Likely
2011-03-16 19:56         ` Mark Brown
2011-03-16 23:06           ` Grant Likely
2011-03-08  6:09 ` [Qualcomm PM8921 MFD v2 4/6] mfd: pm8xxx-mpp: Add pm8xxx MPP driver adharmap
2011-03-08 23:30   ` Mark Brown
2011-03-10  3:36     ` Abhijeet Dharmapurikar
2011-03-10  3:56       ` Trilok Soni
2011-03-10 15:13       ` Mark Brown
2011-03-08  6:09 ` [Qualcomm PM8921 MFD v2 5/6] MAINTAINERS: Add patterns for pmic 8921 files to MSM subsystem adharmap
2011-03-08 23:31   ` Mark Brown
2011-03-08  6:09 ` [Qualcomm PM8921 MFD v2 6/6] msm: board-8960: Add support for pm8921 adharmap

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=4D810797.4090000@codeaurora.org \
    --to=adharmap@codeaurora.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=bryanh@codeaurora.org \
    --cc=collinsd@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=davidb@codeaurora.org \
    --cc=dwalker@fifo99.com \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@suse.de \
    --cc=joe@perches.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.walleij@sterricsson.com \
    --cc=linux@arm.linux.org.uk \
    --cc=sameo@linux.intel.com \
    --cc=stepanm@codeaurora.org \
    --cc=tglx@linutronix.de \
    /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).