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,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
rtc-linux@googlegroups.com, sameo@linux.intel.com,
a.zummo@towertech.it, alexandre.belloni@free-electrons.com,
zhaoy <zhaoy@marvell.com>
Subject: [rtc-linux] Re: [PATCH 2/4] mfd: 88pm800: use irq_mode to configure interrupt status reg clear method
Date: Tue, 02 Jun 2015 14:21:40 +0530 [thread overview]
Message-ID: <556D6E9C.4050402@linaro.org> (raw)
In-Reply-To: <20150601083159.GD3329@x1>
On Monday 01 June 2015 02:01 PM, Lee Jones wrote:
> On Sat, 30 May 2015, Vaibhav Hiremath wrote:
>
>> From the spec, bit 1 of reg 0xe (page 0): IN_CLEAR_MODE controls the
>> method of clearing interrupt status register of 88pm800;
>>
>> 0: clear on read
>> 1: clear on write
>>
>> Signed-off-by: zhaoy <zhaoy@marvell.com>
>
> This signed-off is not acceptable.
>
> No nicknames. Full names only.
>
I just carry forwarded the signoff from original commit.
Let me find his complete signoff and add it to this patch.
>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
>> ---
>> drivers/mfd/88pm800.c | 4 +++-
>> include/linux/mfd/88pm80x.h | 2 ++
>> 2 files changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mfd/88pm800.c b/drivers/mfd/88pm800.c
>> index 06ee058..8ea4467 100644
>> --- a/drivers/mfd/88pm800.c
>> +++ b/drivers/mfd/88pm800.c
>> @@ -391,7 +391,8 @@ static int device_irq_init_800(struct pm80x_chip *chip)
>> PM800_WAKEUP2_INV_INT | PM800_WAKEUP2_INT_CLEAR |
>> PM800_WAKEUP2_INT_MASK;
>>
>> - data = PM800_WAKEUP2_INT_CLEAR;
>> + data = (chip->irq_mode) ?
>> + PM800_WAKEUP2_INT_WRITE_CLEAR : PM800_WAKEUP2_INT_READ_CLEAR;
>
> These variable names are terrible. 'irq_mode' as a bool tells me
> nothing.
>
> What does; irq_mode = 'yes' and irq_mode = 'no' mean? If I didn't
> read the remainder of the code, I would assume if it was 'yes' then
> the device was in IRQ Mode and if not, it would be in PIO or Polling
> mode, but that's not what it means at all is it?
>
> As for 'data', well, isn't everything data?
>
I will rename it.
Thanks,
Vaibhav
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
WARNING: multiple messages have this Message-ID (diff)
From: vaibhav.hiremath@linaro.org (Vaibhav Hiremath)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] mfd: 88pm800: use irq_mode to configure interrupt status reg clear method
Date: Tue, 02 Jun 2015 14:21:40 +0530 [thread overview]
Message-ID: <556D6E9C.4050402@linaro.org> (raw)
In-Reply-To: <20150601083159.GD3329@x1>
On Monday 01 June 2015 02:01 PM, Lee Jones wrote:
> On Sat, 30 May 2015, Vaibhav Hiremath wrote:
>
>> From the spec, bit 1 of reg 0xe (page 0): IN_CLEAR_MODE controls the
>> method of clearing interrupt status register of 88pm800;
>>
>> 0: clear on read
>> 1: clear on write
>>
>> Signed-off-by: zhaoy <zhaoy@marvell.com>
>
> This signed-off is not acceptable.
>
> No nicknames. Full names only.
>
I just carry forwarded the signoff from original commit.
Let me find his complete signoff and add it to this patch.
>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
>> ---
>> drivers/mfd/88pm800.c | 4 +++-
>> include/linux/mfd/88pm80x.h | 2 ++
>> 2 files changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mfd/88pm800.c b/drivers/mfd/88pm800.c
>> index 06ee058..8ea4467 100644
>> --- a/drivers/mfd/88pm800.c
>> +++ b/drivers/mfd/88pm800.c
>> @@ -391,7 +391,8 @@ static int device_irq_init_800(struct pm80x_chip *chip)
>> PM800_WAKEUP2_INV_INT | PM800_WAKEUP2_INT_CLEAR |
>> PM800_WAKEUP2_INT_MASK;
>>
>> - data = PM800_WAKEUP2_INT_CLEAR;
>> + data = (chip->irq_mode) ?
>> + PM800_WAKEUP2_INT_WRITE_CLEAR : PM800_WAKEUP2_INT_READ_CLEAR;
>
> These variable names are terrible. 'irq_mode' as a bool tells me
> nothing.
>
> What does; irq_mode = 'yes' and irq_mode = 'no' mean? If I didn't
> read the remainder of the code, I would assume if it was 'yes' then
> the device was in IRQ Mode and if not, it would be in PIO or Polling
> mode, but that's not what it means at all is it?
>
> As for 'data', well, isn't everything data?
>
I will rename it.
Thanks,
Vaibhav
WARNING: multiple messages have this Message-ID (diff)
From: Vaibhav Hiremath <vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org,
alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org,
zhaoy <zhaoy-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH 2/4] mfd: 88pm800: use irq_mode to configure interrupt status reg clear method
Date: Tue, 02 Jun 2015 14:21:40 +0530 [thread overview]
Message-ID: <556D6E9C.4050402@linaro.org> (raw)
In-Reply-To: <20150601083159.GD3329@x1>
On Monday 01 June 2015 02:01 PM, Lee Jones wrote:
> On Sat, 30 May 2015, Vaibhav Hiremath wrote:
>
>> From the spec, bit 1 of reg 0xe (page 0): IN_CLEAR_MODE controls the
>> method of clearing interrupt status register of 88pm800;
>>
>> 0: clear on read
>> 1: clear on write
>>
>> Signed-off-by: zhaoy <zhaoy-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
>
> This signed-off is not acceptable.
>
> No nicknames. Full names only.
>
I just carry forwarded the signoff from original commit.
Let me find his complete signoff and add it to this patch.
>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>> ---
>> drivers/mfd/88pm800.c | 4 +++-
>> include/linux/mfd/88pm80x.h | 2 ++
>> 2 files changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mfd/88pm800.c b/drivers/mfd/88pm800.c
>> index 06ee058..8ea4467 100644
>> --- a/drivers/mfd/88pm800.c
>> +++ b/drivers/mfd/88pm800.c
>> @@ -391,7 +391,8 @@ static int device_irq_init_800(struct pm80x_chip *chip)
>> PM800_WAKEUP2_INV_INT | PM800_WAKEUP2_INT_CLEAR |
>> PM800_WAKEUP2_INT_MASK;
>>
>> - data = PM800_WAKEUP2_INT_CLEAR;
>> + data = (chip->irq_mode) ?
>> + PM800_WAKEUP2_INT_WRITE_CLEAR : PM800_WAKEUP2_INT_READ_CLEAR;
>
> These variable names are terrible. 'irq_mode' as a bool tells me
> nothing.
>
> What does; irq_mode = 'yes' and irq_mode = 'no' mean? If I didn't
> read the remainder of the code, I would assume if it was 'yes' then
> the device was in IRQ Mode and if not, it would be in PIO or Polling
> mode, but that's not what it means at all is it?
>
> As for 'data', well, isn't everything data?
>
I will rename it.
Thanks,
Vaibhav
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
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,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
rtc-linux@googlegroups.com, sameo@linux.intel.com,
a.zummo@towertech.it, alexandre.belloni@free-electrons.com,
zhaoy <zhaoy@marvell.com>
Subject: Re: [PATCH 2/4] mfd: 88pm800: use irq_mode to configure interrupt status reg clear method
Date: Tue, 02 Jun 2015 14:21:40 +0530 [thread overview]
Message-ID: <556D6E9C.4050402@linaro.org> (raw)
In-Reply-To: <20150601083159.GD3329@x1>
On Monday 01 June 2015 02:01 PM, Lee Jones wrote:
> On Sat, 30 May 2015, Vaibhav Hiremath wrote:
>
>> From the spec, bit 1 of reg 0xe (page 0): IN_CLEAR_MODE controls the
>> method of clearing interrupt status register of 88pm800;
>>
>> 0: clear on read
>> 1: clear on write
>>
>> Signed-off-by: zhaoy <zhaoy@marvell.com>
>
> This signed-off is not acceptable.
>
> No nicknames. Full names only.
>
I just carry forwarded the signoff from original commit.
Let me find his complete signoff and add it to this patch.
>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
>> ---
>> drivers/mfd/88pm800.c | 4 +++-
>> include/linux/mfd/88pm80x.h | 2 ++
>> 2 files changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mfd/88pm800.c b/drivers/mfd/88pm800.c
>> index 06ee058..8ea4467 100644
>> --- a/drivers/mfd/88pm800.c
>> +++ b/drivers/mfd/88pm800.c
>> @@ -391,7 +391,8 @@ static int device_irq_init_800(struct pm80x_chip *chip)
>> PM800_WAKEUP2_INV_INT | PM800_WAKEUP2_INT_CLEAR |
>> PM800_WAKEUP2_INT_MASK;
>>
>> - data = PM800_WAKEUP2_INT_CLEAR;
>> + data = (chip->irq_mode) ?
>> + PM800_WAKEUP2_INT_WRITE_CLEAR : PM800_WAKEUP2_INT_READ_CLEAR;
>
> These variable names are terrible. 'irq_mode' as a bool tells me
> nothing.
>
> What does; irq_mode = 'yes' and irq_mode = 'no' mean? If I didn't
> read the remainder of the code, I would assume if it was 'yes' then
> the device was in IRQ Mode and if not, it would be in PIO or Polling
> mode, but that's not what it means at all is it?
>
> As for 'data', well, isn't everything data?
>
I will rename it.
Thanks,
Vaibhav
next prev parent reply other threads:[~2015-06-02 8:51 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 22:19 [rtc-linux] [PATCH 0/4] Add Device tree support for 88PM800 mfd and rtc driver Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-05-29 22:19 ` [rtc-linux] [PATCH 1/4] mfd: 88pm800: add device tree support Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-06-01 8:38 ` [rtc-linux] " Lee Jones
2015-06-01 8:38 ` Lee Jones
2015-06-01 8:38 ` Lee Jones
2015-06-01 8:38 ` Lee Jones
2015-06-16 7:52 ` [rtc-linux] " Vaibhav Hiremath
2015-06-16 7:52 ` Vaibhav Hiremath
2015-06-16 7:52 ` Vaibhav Hiremath
2015-06-16 7:52 ` Vaibhav Hiremath
2015-06-16 13:02 ` [rtc-linux] " Rob Herring
2015-06-16 13:02 ` Rob Herring
2015-06-16 13:02 ` Rob Herring
2015-06-16 13:02 ` Rob Herring
2015-06-16 14:36 ` [rtc-linux] " Vaibhav Hiremath
2015-06-16 14:36 ` Vaibhav Hiremath
2015-06-16 14:36 ` Vaibhav Hiremath
2015-06-16 14:36 ` Vaibhav Hiremath
2015-05-29 22:19 ` [rtc-linux] [PATCH 2/4] mfd: 88pm800: use irq_mode to configure interrupt status reg clear method Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-06-01 8:31 ` [rtc-linux] " Lee Jones
2015-06-01 8:31 ` Lee Jones
2015-06-01 8:31 ` Lee Jones
2015-06-02 8:51 ` Vaibhav Hiremath [this message]
2015-06-02 8:51 ` Vaibhav Hiremath
2015-06-02 8:51 ` Vaibhav Hiremath
2015-06-02 8:51 ` Vaibhav Hiremath
2015-05-29 22:19 ` [rtc-linux] [PATCH 3/4] rtc: 88pm80x: add device tree support Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-05-29 22:19 ` [rtc-linux] [PATCH 4/4] mfd: 88pm800: allocate pdata->rtc if not allocated earlier Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-05-29 22:19 ` Vaibhav Hiremath
2015-06-01 8:22 ` [rtc-linux] " Lee Jones
2015-06-01 8:22 ` Lee Jones
2015-06-01 8:22 ` Lee Jones
2015-06-02 5:07 ` [rtc-linux] " Vaibhav Hiremath
2015-06-02 5:07 ` Vaibhav Hiremath
2015-06-02 5:07 ` Vaibhav Hiremath
2015-06-02 7:40 ` [rtc-linux] " Lee Jones
2015-06-02 7:40 ` Lee Jones
2015-06-02 7:40 ` Lee Jones
2015-06-02 7:40 ` Lee Jones
2015-06-02 9:05 ` [rtc-linux] " Vaibhav Hiremath
2015-06-02 9:05 ` Vaibhav Hiremath
2015-06-02 9:05 ` Vaibhav Hiremath
2015-06-02 9:05 ` Vaibhav Hiremath
2015-06-02 9:33 ` [rtc-linux] " Lee Jones
2015-06-02 9:33 ` Lee Jones
2015-06-02 9:33 ` Lee Jones
2015-06-02 9:33 ` Lee Jones
2015-06-02 9:49 ` [rtc-linux] " Vaibhav Hiremath
2015-06-02 9:49 ` Vaibhav Hiremath
2015-06-02 9:49 ` Vaibhav Hiremath
2015-06-02 9:49 ` Vaibhav Hiremath
2015-06-02 10:07 ` [rtc-linux] " Lee Jones
2015-06-02 10:07 ` Lee Jones
2015-06-02 10:07 ` Lee Jones
2015-06-02 10:18 ` [rtc-linux] " Vaibhav Hiremath
2015-06-02 10:18 ` Vaibhav Hiremath
2015-06-02 10:18 ` 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=556D6E9C.4050402@linaro.org \
--to=vaibhav.hiremath@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=zhaoy@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.