From: Keerthy <a0393675@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Keerthy <j-keerthy@ti.com>,
linux-omap@vger.kernel.org, lgirdwood@gmail.com,
broonie@kernel.org, linux-kernel@vger.kernel.org,
sameo@linux.intel.com
Subject: Re: [PATCH 7/9] regulator: palmas: Add palmas_pmic_driver_data structure
Date: Wed, 18 Jun 2014 10:31:52 +0530 [thread overview]
Message-ID: <53A11D40.7020201@ti.com> (raw)
In-Reply-To: <20140617163721.GR29841@lee--X1>
On Tuesday 17 June 2014 10:07 PM, Lee Jones wrote:
> On Wed, 28 May 2014, Keerthy wrote:
>
>> Add palmas_pmic_driver_data structure.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> ---
>> include/linux/mfd/palmas.h | 25 +++++++++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>>
>> diff --git a/include/linux/mfd/palmas.h b/include/linux/mfd/palmas.h
>> index 8d68452..70f0695 100644
>> --- a/include/linux/mfd/palmas.h
>> +++ b/include/linux/mfd/palmas.h
>> @@ -53,6 +53,8 @@ struct palmas_pmic;
>> struct palmas_gpadc;
>> struct palmas_resource;
>> struct palmas_usb;
>> +struct palmas_pmic_driver_data;
>> +struct palmas_pmic_platform_data;
>>
>> enum palmas_usb_state {
>> PALMAS_USB_STATE_DISCONNECT,
>> @@ -76,6 +78,8 @@ struct palmas {
>> struct mutex irq_lock;
>> struct regmap_irq_chip_data *irq_data;
>>
>> + struct palmas_pmic_driver_data *pmic_ddata;
>> +
>> /* Child Devices */
>> struct palmas_pmic *pmic;
>> struct palmas_gpadc *gpadc;
>> @@ -107,6 +111,27 @@ struct regs_info {
>> int sleep_id;
>> };
>>
>> +struct palmas_pmic_driver_data {
>> + int smps_start;
>> + int smps_end;
>> + int ldo_begin;
>> + int ldo_end;
>> + int max_reg;
>> + struct regs_info *palmas_regs_info;
>> + struct of_regulator_match *palmas_matches;
>> + struct palmas_sleep_requestor_info *sleep_req_info;
>> + int (*smps_register)(struct palmas_pmic *pmic,
>> + struct palmas_pmic_driver_data *ddata,
>> + struct palmas_pmic_platform_data *pdata,
>> + const char *pdev_name,
>> + struct regulator_config config);
>> + int (*ldo_register)(struct palmas_pmic *pmic,
>> + struct palmas_pmic_driver_data *ddata,
>> + struct palmas_pmic_platform_data *pdata,
>> + const char *pdev_name,
>> + struct regulator_config config);
> Are you sure you need to store all of this stuff?
>
> Particularly the match pointer. Do you really re-use it?
Match pointer is used extensively in the palmas_regulator.c.
This structure is very much used by regulator driver.
>
>> +};
>> +
>> struct palmas_gpadc_platform_data {
>> /* Channel 3 current source is only enabled during conversion */
>> int ch3_current;
next prev parent reply other threads:[~2014-06-18 5:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 10:20 [PATCH 0/9] mfd: tps65917: Add support for for TPS65917 PMIC Keerthy
2014-05-28 10:20 ` [PATCH 1/9] mfd: Add DT bindings for tps65917 PMIC Keerthy
2014-05-28 10:20 ` [PATCH 2/9] regulator: palmas: Add tps65917 compatible string Keerthy
2014-05-28 10:20 ` [PATCH 3/9] mfd: palmas: Add tps65917 specific definitions and enums Keerthy
2014-06-17 16:11 ` Lee Jones
2014-06-18 5:07 ` Keerthy
2014-05-28 10:20 ` [PATCH 4/9] mfd: palmas: Add tps65917 support Keerthy
2014-06-17 16:19 ` Lee Jones
2014-06-18 5:06 ` Keerthy
2014-05-28 10:20 ` [PATCH 5/9] regulator: palmas: Shift the reg_info structure definition to the header file Keerthy
2014-06-17 16:32 ` Lee Jones
2014-06-18 5:05 ` Keerthy
2014-05-28 10:20 ` [PATCH 6/9] mfd: palmas: shift the palmas_sleep_requestor_info " Keerthy
2014-06-17 16:33 ` Lee Jones
2014-06-18 5:04 ` Keerthy
2014-05-28 10:20 ` [PATCH 7/9] regulator: palmas: Add palmas_pmic_driver_data structure Keerthy
2014-06-17 16:37 ` Lee Jones
2014-06-18 5:01 ` Keerthy [this message]
2014-06-18 7:24 ` Lee Jones
2014-05-28 10:20 ` [PATCH 8/9] regulator: palmas: add driver data and modularize the probe Keerthy
2014-06-17 16:45 ` Lee Jones
2014-06-18 4:53 ` Keerthy
2014-05-28 10:20 ` [PATCH 9/9] regulator: palmas: Add tps65917 PMIC support Keerthy
2014-06-06 10:59 ` [PATCH 0/9] mfd: tps65917: Add support for for TPS65917 PMIC Keerthy
2014-06-06 12:43 ` Lee Jones
2014-06-06 12:50 ` Mark Brown
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=53A11D40.7020201@ti.com \
--to=a0393675@ti.com \
--cc=broonie@kernel.org \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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).