From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Doug Anderson <dianders@chromium.org>,
Olof Johansson <olof@lixom.net>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
rtc-linux@googlegroups.com, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH RESEND v9 5/5] rtc: Add driver for Maxim 77802 PMIC Real-Time-Clock
Date: Mon, 15 Sep 2014 16:07:46 +0200 [thread overview]
Message-ID: <5416F2B2.1060300@collabora.co.uk> (raw)
In-Reply-To: <20140912151334.cd53fca611a7de487f23241b@linux-foundation.org>
Hello Andrew,
On 09/13/2014 12:13 AM, Andrew Morton wrote:
> On Fri, 12 Sep 2014 10:17:43 +0200 Javier Martinez Canillas <javier.martinez@collabora.co.uk> wrote:
>
>> The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms.
>> This patch adds support for the RTC and is based on a driver
>> added by Simon Glass to the Chrome OS kernel 3.8 tree.
>>
>> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>
> Would it be appropriate to gather Simon's signoff?
>
I don't know. The original driver written by Simon supported 2 devices:
max77686 and max77802. I split the max77802 bits and addressed all the issues
pointed out on early revisions so even when Simon is mentioned as the
MODULE_AUTHOR(), I didn't know if he would like his s-o-b to remain in the
patch since it was quite different than the original one from which was based.
>> +static inline int max77802_rtc_calculate_wday(u8 shifted)
>> +{
>> + int counter = -1;
>> +
>> + while (shifted) {
>> + shifted >>= 1;
>> + counter++;
>> + }
>
> Can't use log2() or similar?
>
Yes, ffs() - 1 can be used instead of this function indeed.
I see that you already included this patch to your -mm tree [0]. Does it mean
that I've to send a follow-up patch on top of this to remove this function or
should I send a new version of this patch?
Best regards,
Javier
[0]:
http://ozlabs.org/~akpm/mmots/broken-out/rtc-add-driver-for-maxim-77802-pmic-real-time-clock.patch
WARNING: multiple messages have this Message-ID (diff)
From: javier.martinez@collabora.co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v9 5/5] rtc: Add driver for Maxim 77802 PMIC Real-Time-Clock
Date: Mon, 15 Sep 2014 16:07:46 +0200 [thread overview]
Message-ID: <5416F2B2.1060300@collabora.co.uk> (raw)
In-Reply-To: <20140912151334.cd53fca611a7de487f23241b@linux-foundation.org>
Hello Andrew,
On 09/13/2014 12:13 AM, Andrew Morton wrote:
> On Fri, 12 Sep 2014 10:17:43 +0200 Javier Martinez Canillas <javier.martinez@collabora.co.uk> wrote:
>
>> The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms.
>> This patch adds support for the RTC and is based on a driver
>> added by Simon Glass to the Chrome OS kernel 3.8 tree.
>>
>> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>
> Would it be appropriate to gather Simon's signoff?
>
I don't know. The original driver written by Simon supported 2 devices:
max77686 and max77802. I split the max77802 bits and addressed all the issues
pointed out on early revisions so even when Simon is mentioned as the
MODULE_AUTHOR(), I didn't know if he would like his s-o-b to remain in the
patch since it was quite different than the original one from which was based.
>> +static inline int max77802_rtc_calculate_wday(u8 shifted)
>> +{
>> + int counter = -1;
>> +
>> + while (shifted) {
>> + shifted >>= 1;
>> + counter++;
>> + }
>
> Can't use log2() or similar?
>
Yes, ffs() - 1 can be used instead of this function indeed.
I see that you already included this patch to your -mm tree [0]. Does it mean
that I've to send a follow-up patch on top of this to remove this function or
should I send a new version of this patch?
Best regards,
Javier
[0]:
http://ozlabs.org/~akpm/mmots/broken-out/rtc-add-driver-for-maxim-77802-pmic-real-time-clock.patch
next prev parent reply other threads:[~2014-09-15 14:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 8:17 [PATCH RESEND v9 0/5] Add Maxim 77802 RTC support Javier Martinez Canillas
2014-09-12 8:17 ` Javier Martinez Canillas
2014-09-12 8:17 ` [PATCH RESEND v9 1/5] rtc: max77686: Allow the max77686 rtc to wakeup the system Javier Martinez Canillas
2014-09-12 8:17 ` Javier Martinez Canillas
2014-09-12 15:12 ` Doug Anderson
2014-09-12 15:12 ` Doug Anderson
2014-09-12 15:54 ` Javier Martinez Canillas
2014-09-12 15:54 ` Javier Martinez Canillas
2014-09-12 16:03 ` Doug Anderson
2014-09-12 16:03 ` Doug Anderson
2014-09-12 22:05 ` Andrew Morton
2014-09-12 22:05 ` Andrew Morton
2014-09-15 14:03 ` Javier Martinez Canillas
2014-09-15 14:03 ` Javier Martinez Canillas
2014-09-12 8:17 ` [PATCH RESEND v9 2/5] rtc: max77686: Remove dead code for SMPL and WTSR Javier Martinez Canillas
2014-09-12 8:17 ` Javier Martinez Canillas
2014-09-12 8:17 ` Javier Martinez Canillas
2014-09-12 8:17 ` [PATCH RESEND v9 3/5] rtc: max77686: Fail to probe if no RTC regmap irqchip is set Javier Martinez Canillas
2014-09-12 8:17 ` Javier Martinez Canillas
2014-09-12 8:17 ` Javier Martinez Canillas
2014-09-12 8:17 ` [PATCH RESEND v9 4/5] rtc: max77686: Remove unneded info log Javier Martinez Canillas
2014-09-12 8:17 ` Javier Martinez Canillas
2014-09-12 8:17 ` [PATCH RESEND v9 5/5] rtc: Add driver for Maxim 77802 PMIC Real-Time-Clock Javier Martinez Canillas
2014-09-12 8:17 ` Javier Martinez Canillas
2014-09-12 8:17 ` Javier Martinez Canillas
2014-09-12 22:13 ` Andrew Morton
2014-09-12 22:13 ` Andrew Morton
2014-09-15 14:07 ` Javier Martinez Canillas [this message]
2014-09-15 14:07 ` Javier Martinez Canillas
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=5416F2B2.1060300@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=dianders@chromium.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rtc-linux@googlegroups.com \
--cc=sjg@chromium.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 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.