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,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
yizhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org,
Zhao Ye <zhaoy-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH-V5 3/4] mfd: 88pm800: Set default interrupt clear method
Date: Tue, 07 Jul 2015 16:21:15 +0530 [thread overview]
Message-ID: <559BAF23.90002@linaro.org> (raw)
In-Reply-To: <20150707104028.GR3182@x1>
On Tuesday 07 July 2015 04:10 PM, Lee Jones wrote:
> On Tue, 07 Jul 2015, Vaibhav Hiremath wrote:
>> On Tuesday 07 July 2015 12:59 PM, Lee Jones wrote:
>>> On Mon, 29 Jun 2015, Vaibhav Hiremath wrote:
>>>
>>>> As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
>>>> (page 0) controls the method of clearing interrupt
>>>> status of 88pm800 family of devices;
>>>>
>>>> 0: clear on read
>>>> 1: clear on write
>>>>
>>>> If pdata is not coming from board file, then set the
>>>> default irq clear method to "irq clear on write"
>>>>
>>>> Also, as suggested by "Lee Jones" renaming variable field
>>>> to appropriate name.
>>>>
>>>> Signed-off-by: Zhao Ye <zhaoy-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
>>>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>>>> ---
>>>> drivers/mfd/88pm800.c | 15 ++++++++++-----
>>>> include/linux/mfd/88pm80x.h | 10 ++++++++--
>>>> 2 files changed, 18 insertions(+), 7 deletions(-)
>>>>
>>>> diff --git a/drivers/mfd/88pm800.c b/drivers/mfd/88pm800.c
>>>> index d495737..66347be 100644
>>>> --- a/drivers/mfd/88pm800.c
>>>> +++ b/drivers/mfd/88pm800.c
>>>> @@ -374,7 +374,7 @@ static int device_irq_init_800(struct pm80x_chip *chip)
>>>> {
>>>> struct regmap *map = chip->regmap;
>>>> unsigned long flags = IRQF_ONESHOT;
>>>> - int data, mask, ret = -EINVAL;
>>>> + int irq_clr_mode, mask, ret = -EINVAL;
>>>>
>>>> if (!map || !chip->irq) {
>>>> dev_err(chip->dev, "incorrect parameters\n");
>>>> @@ -382,15 +382,16 @@ static int device_irq_init_800(struct pm80x_chip *chip)
>>>> }
>>>>
>>>> /*
>>>> - * irq_mode defines the way of clearing interrupt. it's read-clear by
>>>> - * default.
>>>> + * irq_clr_on_wr defines the way of clearing interrupt by
>>>> + * read/write(0/1). It's read-clear by default.
>>>> */
>>>> mask =
>>>> PM800_WAKEUP2_INV_INT | PM800_WAKEUP2_INT_CLEAR |
>>>> PM800_WAKEUP2_INT_MASK;
>>>>
>>>> - data = PM800_WAKEUP2_INT_CLEAR;
>>>> - ret = regmap_update_bits(map, PM800_WAKEUP2, mask, data);
>>>> + irq_clr_mode = chip->irq_clr_method == PM800_IRQ_CLR_ON_WRITE ?
>>>> + PM800_WAKEUP2_INT_WRITE_CLEAR : PM800_WAKEUP2_INT_READ_CLEAR;
>>>> + ret = regmap_update_bits(map, PM800_WAKEUP2, mask, irq_clr_mode);
>>>
>>> What's stopping you just passing PM800_WAKEUP2_INT_WRITE_CLEAR or
>>> PM800_WAKEUP2_INT_READ_CLEAR from pdata? Then you can use the value
>>> directly without all of this faffing about.
>>>
>>> regmap_update_bits(map, PM800_WAKEUP2, mask, pdata->irq_clr_mode);
>>>
>>
>> Because "irq_clr_method" is of boolean type.
>> And macros which you are referring to is,
>>
>> #define PM800_WAKEUP2_INT_READ_CLEAR (0 << 1)
>> #define PM800_WAKEUP2_INT_WRITE_CLEAR (1 << 1)
>>
>>
>> And also, I feel it is more cleaner approach with the current code as
>> register definition and userflag are maintained separately.
>
> I see your point, although it's a shame we have to have this code in
> its place.
>
> One thing I think you can do though is rid chip->irq_clr_method, just
> use the one you already have in pdata.
>
Looking at the current code,
Yes, this can be done, but I have to do some more changes around it,
to make code cleaner,
change the signature of
static int device_irq_init_800(struct pm80x_chip *chip)
TO
static int device_irq_init_800(struct pm80x_chip *chip, struct
pm80x_platform_data *pdata)
and then only use pdata->irq_clr_method.
How do you want to get this inside? V6 version? or separate patch?
I have one more cleanup patch in the queue, which I am planning to
submit today, if you are ok then I can submit along with that.
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
next prev parent reply other threads:[~2015-07-07 10:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 15:31 [PATCH-V5 0/4] mfd: 88pm800: Add Device tree support Vaibhav Hiremath
2015-06-29 15:31 ` [PATCH-V5 1/4] mfd: 88pm800: Add device " Vaibhav Hiremath
[not found] ` <1435591877-18214-2-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-30 0:32 ` Krzysztof Kozlowski
2015-07-07 7:30 ` Lee Jones
[not found] ` <1435591877-18214-1-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-29 15:31 ` [PATCH-V5 2/4] mfd: 88pm800: Remove unnecessary protection around pdata Vaibhav Hiremath
[not found] ` <1435591877-18214-3-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-30 0:34 ` Krzysztof Kozlowski
2015-07-07 7:30 ` Lee Jones
2015-06-29 15:31 ` [PATCH-V5 3/4] mfd: 88pm800: Set default interrupt clear method Vaibhav Hiremath
[not found] ` <1435591877-18214-4-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-30 0:29 ` Krzysztof Kozlowski
2015-07-07 7:29 ` Lee Jones
2015-07-07 9:53 ` Vaibhav Hiremath
[not found] ` <559BA1AE.9050006-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-07-07 10:40 ` Lee Jones
2015-07-07 10:51 ` Vaibhav Hiremath [this message]
2015-07-07 11:12 ` Lee Jones
2015-07-07 11:18 ` Vaibhav Hiremath
[not found] ` <559BB58E.9010406-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-07-07 11:25 ` Vaibhav Hiremath
[not found] ` <559BB727.2070106-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-07-07 12:54 ` Lee Jones
2015-07-07 14:47 ` Vaibhav Hiremath
2015-07-07 14:57 ` Lee Jones
2015-07-08 12:22 ` Vaibhav Hiremath
2015-06-29 15:31 ` [PATCH-V5 4/4] mfd: devicetree: bindings: Add new 88pm800 mfd binding Vaibhav Hiremath
[not found] ` <1435591877-18214-5-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-30 0:30 ` Krzysztof Kozłowski
2015-07-01 7:43 ` Lee Jones
2015-07-01 8:00 ` Krzysztof Kozłowski
2015-06-30 0:31 ` Krzysztof Kozlowski
[not found] ` <CAJKOXPdyDRPiEwKd_MLq6rkhuWxxqqageUweMk-p69RXfH2hJA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-30 5:40 ` Vaibhav Hiremath
2015-07-07 7:31 ` Lee Jones
2015-07-01 16:10 ` Rob Herring
2015-07-01 16:21 ` Vaibhav Hiremath
[not found] ` <5594137D.6070106-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-07-01 17:17 ` Rob Herring
[not found] ` <CAL_JsqKgxPK3oBJifAn9-S8pB8Ew7JRmi9cJE4qO1b=aRC4N+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-01 17:24 ` 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=559BAF23.90002@linaro.org \
--to=vaibhav.hiremath-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=yizhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org \
--cc=zhaoy-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org \
/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).