From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
alexandre.belloni@free-electrons.com, a.zummo@towertech.it
Cc: cw00.choi@samsung.com, rtc-linux@googlegroups.com,
linux-kernel@vger.kernel.org, javier@osg.samsung.com,
rklein@nvidia.com
Subject: Re: [PATCH 2/2] rtc: max77686: Use REGMAP_IRQ_REG for regmap-rtc-irqs initialisation
Date: Wed, 02 Mar 2016 10:00:24 +0900 [thread overview]
Message-ID: <56D63B28.9030502@samsung.com> (raw)
In-Reply-To: <1456750705-13579-2-git-send-email-ldewangan@nvidia.com>
On 29.02.2016 21:58, Laxman Dewangan wrote:
> use macro REGMAP_IRQ_REG from regmap.h to initialise the
> regmap irq table for max77686.
Why? Any benefits?
Best regards,
Krzysztof
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> drivers/rtc/rtc-max77686.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/rtc/rtc-max77686.c b/drivers/rtc/rtc-max77686.c
> index 39d529a..0cb422b 100644
> --- a/drivers/rtc/rtc-max77686.c
> +++ b/drivers/rtc/rtc-max77686.c
> @@ -174,12 +174,12 @@ static const unsigned int max77686_map[REG_RTC_END] = {
>
> static const struct regmap_irq max77686_rtc_irqs[] = {
> /* RTC interrupts */
> - { .reg_offset = 0, .mask = MAX77686_RTCINT_RTC60S_MSK, },
> - { .reg_offset = 0, .mask = MAX77686_RTCINT_RTCA1_MSK, },
> - { .reg_offset = 0, .mask = MAX77686_RTCINT_RTCA2_MSK, },
> - { .reg_offset = 0, .mask = MAX77686_RTCINT_SMPL_MSK, },
> - { .reg_offset = 0, .mask = MAX77686_RTCINT_RTC1S_MSK, },
> - { .reg_offset = 0, .mask = MAX77686_RTCINT_WTSR_MSK, },
> + REGMAP_IRQ_REG(0, 0, MAX77686_RTCINT_RTC60S_MSK),
> + REGMAP_IRQ_REG(1, 0, MAX77686_RTCINT_RTCA1_MSK),
> + REGMAP_IRQ_REG(2, 0, MAX77686_RTCINT_RTCA2_MSK),
> + REGMAP_IRQ_REG(3, 0, MAX77686_RTCINT_SMPL_MSK),
> + REGMAP_IRQ_REG(4, 0, MAX77686_RTCINT_RTC1S_MSK),
> + REGMAP_IRQ_REG(5, 0, MAX77686_RTCINT_WTSR_MSK),
> };
>
> static const struct regmap_irq_chip max77686_rtc_irq_chip = {
>
next prev parent reply other threads:[~2016-03-02 1:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 12:58 [PATCH 1/2] rtc: max77686: Add support for MAX20024/MAX77620 RTC IP Laxman Dewangan
2016-02-29 12:58 ` [PATCH 2/2] rtc: max77686: Use REGMAP_IRQ_REG for regmap-rtc-irqs initialisation Laxman Dewangan
2016-03-02 1:00 ` Krzysztof Kozlowski [this message]
2016-03-02 2:04 ` Laxman Dewangan
2016-03-02 3:45 ` Krzysztof Kozlowski
2016-03-02 0:58 ` [PATCH 1/2] rtc: max77686: Add support for MAX20024/MAX77620 RTC IP Krzysztof Kozlowski
2016-03-02 2:15 ` Laxman Dewangan
2016-03-02 3:52 ` Krzysztof Kozlowski
2016-03-02 4:10 ` Laxman Dewangan
2016-03-02 4:28 ` Krzysztof Kozlowski
2016-03-02 6:01 ` Laxman Dewangan
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=56D63B28.9030502@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=cw00.choi@samsung.com \
--cc=javier@osg.samsung.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rklein@nvidia.com \
--cc=rtc-linux@googlegroups.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