From: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
yhanin@marvell.com, haojian.zhuang@marvell.com,
zhouqiao@marvell.com, mturquette@baylibre.com,
k.kozlowski@samsung.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 4/4] mfd: 88pm800: Add support for clk subdevice
Date: Wed, 05 Aug 2015 14:37:50 +0530 [thread overview]
Message-ID: <55C1D266.5090804@linaro.org> (raw)
In-Reply-To: <20150723155008.GS3436@x1>
On Thursday 23 July 2015 09:20 PM, Lee Jones wrote:
> On Tue, 21 Jul 2015, Vaibhav Hiremath wrote:
>
>> This patch adds mfd_cell/clk-subdevice for 88PM800 MFD
>> (and family of devices).
>>
>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
>> ---
>> drivers/mfd/88pm800.c | 25 +++++++++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>>
>> diff --git a/drivers/mfd/88pm800.c b/drivers/mfd/88pm800.c
>> index f104a32..9723eac 100644
>> --- a/drivers/mfd/88pm800.c
>> +++ b/drivers/mfd/88pm800.c
>> @@ -173,6 +173,14 @@ static const struct mfd_cell regulator_devs[] = {
>> },
>> };
>>
>> +static struct mfd_cell clk_devs[] = {
>> + {
>> + .name = "88pm80x-clk",
>> + .of_compatible = "marvell,88pm800-clk",
>> + .id = -1,
>> + },
>> +};
>
> Why does each device in 88pm800.c have it's own mfd_cell?
>
Probably, the author of the driver can comment on this. I have cc'ed
all of them.
But looking at the driver it looks like, except onkey and regulator all
other devices need per-initialization. For example,
in case of clock,
static int device_clk_init(struct pm80x_chip *chip)
{
if (chip->type == CHIP_PM800)
clk_devs[0].name = "88pm800-clk";
else if (chip->type == CHIP_PM860)
clk_devs[0].name = "88pm860-clk";
return mfd_add_devices(chip->dev, 0, &clk_devs[0],
ARRAY_SIZE(clk_devs), NULL, 0, NULL);
}
> Take the opportunity to correct the tabbing in the remainder of the
> file. Make that fix-up patch 1 of this set. Then fixup this patch.
>
Ok, I will.
Thanks,
Vaibhav
WARNING: multiple messages have this Message-ID (diff)
From: vaibhav.hiremath@linaro.org (Vaibhav Hiremath)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] mfd: 88pm800: Add support for clk subdevice
Date: Wed, 05 Aug 2015 14:37:50 +0530 [thread overview]
Message-ID: <55C1D266.5090804@linaro.org> (raw)
In-Reply-To: <20150723155008.GS3436@x1>
On Thursday 23 July 2015 09:20 PM, Lee Jones wrote:
> On Tue, 21 Jul 2015, Vaibhav Hiremath wrote:
>
>> This patch adds mfd_cell/clk-subdevice for 88PM800 MFD
>> (and family of devices).
>>
>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
>> ---
>> drivers/mfd/88pm800.c | 25 +++++++++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>>
>> diff --git a/drivers/mfd/88pm800.c b/drivers/mfd/88pm800.c
>> index f104a32..9723eac 100644
>> --- a/drivers/mfd/88pm800.c
>> +++ b/drivers/mfd/88pm800.c
>> @@ -173,6 +173,14 @@ static const struct mfd_cell regulator_devs[] = {
>> },
>> };
>>
>> +static struct mfd_cell clk_devs[] = {
>> + {
>> + .name = "88pm80x-clk",
>> + .of_compatible = "marvell,88pm800-clk",
>> + .id = -1,
>> + },
>> +};
>
> Why does each device in 88pm800.c have it's own mfd_cell?
>
Probably, the author of the driver can comment on this. I have cc'ed
all of them.
But looking at the driver it looks like, except onkey and regulator all
other devices need per-initialization. For example,
in case of clock,
static int device_clk_init(struct pm80x_chip *chip)
{
if (chip->type == CHIP_PM800)
clk_devs[0].name = "88pm800-clk";
else if (chip->type == CHIP_PM860)
clk_devs[0].name = "88pm860-clk";
return mfd_add_devices(chip->dev, 0, &clk_devs[0],
ARRAY_SIZE(clk_devs), NULL, 0, NULL);
}
> Take the opportunity to correct the tabbing in the remainder of the
> file. Make that fix-up patch 1 of this set. Then fixup this patch.
>
Ok, I will.
Thanks,
Vaibhav
next prev parent reply other threads:[~2015-08-05 9:07 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 11:06 [PATCH 0/4] clk: 88pm800: Add new clk provider driver for 88PM800 MFD Vaibhav Hiremath
2015-07-21 11:06 ` Vaibhav Hiremath
2015-07-21 11:07 ` [PATCH 1/4] mfd: 88pm800: Update the header file with 32K clk related macros Vaibhav Hiremath
2015-07-21 11:07 ` Vaibhav Hiremath
2015-07-23 15:52 ` Lee Jones
2015-07-23 15:52 ` Lee Jones
2015-07-23 15:52 ` Lee Jones
2015-08-05 8:53 ` Vaibhav Hiremath
2015-08-05 8:53 ` Vaibhav Hiremath
2015-07-21 11:07 ` [PATCH 2/4] mfd: devicetree: bindings: Add clock subdevice node information Vaibhav Hiremath
2015-07-21 11:07 ` Vaibhav Hiremath
2015-07-23 5:08 ` Krzysztof Kozlowski
2015-07-23 5:08 ` Krzysztof Kozlowski
2015-07-30 22:13 ` Stephen Boyd
2015-07-30 22:13 ` Stephen Boyd
2015-07-30 22:13 ` Stephen Boyd
2015-07-30 22:21 ` Rob Herring
2015-07-30 22:21 ` Rob Herring
2015-07-30 22:21 ` Rob Herring
2015-08-05 6:39 ` Vaibhav Hiremath
2015-07-21 11:07 ` [PATCH 3/4] clk: 88pm800: Add clk provider driver for 88pm800 family of devices Vaibhav Hiremath
2015-07-21 11:07 ` Vaibhav Hiremath
2015-07-21 19:10 ` Stephen Boyd
2015-07-21 19:10 ` Stephen Boyd
2015-07-21 19:36 ` Vaibhav Hiremath
2015-07-21 19:36 ` Vaibhav Hiremath
2015-07-21 19:36 ` Vaibhav Hiremath
2015-07-21 20:52 ` Stephen Boyd
2015-07-21 20:52 ` Stephen Boyd
2015-07-22 6:27 ` Vaibhav Hiremath
2015-07-22 6:27 ` Vaibhav Hiremath
2015-07-22 6:27 ` Vaibhav Hiremath
2015-07-22 6:46 ` Krzysztof Kozlowski
2015-07-22 6:46 ` Krzysztof Kozlowski
2015-07-22 8:16 ` Vaibhav Hiremath
2015-07-22 8:16 ` Vaibhav Hiremath
2015-07-22 22:03 ` Stephen Boyd
2015-07-22 22:03 ` Stephen Boyd
2015-07-21 11:07 ` [PATCH 4/4] mfd: 88pm800: Add support for clk subdevice Vaibhav Hiremath
2015-07-21 11:07 ` Vaibhav Hiremath
2015-07-23 4:58 ` Krzysztof Kozlowski
2015-07-23 4:58 ` Krzysztof Kozlowski
2015-07-23 4:58 ` Krzysztof Kozlowski
2015-07-23 15:50 ` Lee Jones
2015-07-23 15:50 ` Lee Jones
2015-07-23 15:50 ` Lee Jones
2015-08-05 9:07 ` Vaibhav Hiremath [this message]
2015-08-05 9:07 ` Vaibhav Hiremath
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=55C1D266.5090804@linaro.org \
--to=vaibhav.hiremath@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=haojian.zhuang@marvell.com \
--cc=k.kozlowski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=yhanin@marvell.com \
--cc=zhouqiao@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.