From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@iki.fi>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Tony Lindgren <tony@atomide.com>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org,
Christoph Fritz <chf.fritz@googlemail.com>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH] RTC: rtc-twl: Convert to module_platform_driver() and relocate reg_map init
Date: Tue, 16 Apr 2013 10:16:00 +0200 [thread overview]
Message-ID: <516D08C0.70702@ti.com> (raw)
In-Reply-To: <516D0790.7090902@iki.fi>
Hi Tomi,
On 04/16/2013 10:10 AM, Tomi Valkeinen wrote:
> Hi,
>
> On 2013-04-16 10:44, Peter Ujfalusi wrote:
>> Convert the driver to use module_platform_driver() to register the platform
>> driver and relocate the rtc_reg_map initialization to platform driver's
>> probe function.
>> In this way we can make sure that the twl-core has been already probed since
>> the core driver will create the device at the end of it's probe function.
>>
>> Reported-by: Christoph Fritz <chf.fritz@googlemail.com>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
> I think there are two distinct things here. The actual fix for the
> regmap, and a module_platform_driver cleanup. I would suggest having
> them in separate patches.
>
> And even if these are combined, I think the patch subject and
> description should talk about fixing the regmap bug. Now it's rather
> unclear that an actual bug is being fixed.
Good point. My thinking was that when I convert the driver to
module_platform_driver() the reg map init must be moved to platform_driver's
probe anyways.
I'll separate the patch and write a bit better commit message for the first.
--
Péter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@iki.fi>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Tony Lindgren <tony@atomide.com>, <rtc-linux@googlegroups.com>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
Christoph Fritz <chf.fritz@googlemail.com>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH] RTC: rtc-twl: Convert to module_platform_driver() and relocate reg_map init
Date: Tue, 16 Apr 2013 10:16:00 +0200 [thread overview]
Message-ID: <516D08C0.70702@ti.com> (raw)
In-Reply-To: <516D0790.7090902@iki.fi>
Hi Tomi,
On 04/16/2013 10:10 AM, Tomi Valkeinen wrote:
> Hi,
>
> On 2013-04-16 10:44, Peter Ujfalusi wrote:
>> Convert the driver to use module_platform_driver() to register the platform
>> driver and relocate the rtc_reg_map initialization to platform driver's
>> probe function.
>> In this way we can make sure that the twl-core has been already probed since
>> the core driver will create the device at the end of it's probe function.
>>
>> Reported-by: Christoph Fritz <chf.fritz@googlemail.com>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
> I think there are two distinct things here. The actual fix for the
> regmap, and a module_platform_driver cleanup. I would suggest having
> them in separate patches.
>
> And even if these are combined, I think the patch subject and
> description should talk about fixing the regmap bug. Now it's rather
> unclear that an actual bug is being fixed.
Good point. My thinking was that when I convert the driver to
module_platform_driver() the reg map init must be moved to platform_driver's
probe anyways.
I'll separate the patch and write a bit better commit message for the first.
--
Péter
next prev parent reply other threads:[~2013-04-16 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 7:44 [PATCH] RTC: rtc-twl: Convert to module_platform_driver() and relocate reg_map init Peter Ujfalusi
2013-04-16 7:44 ` Peter Ujfalusi
2013-04-16 8:10 ` Tomi Valkeinen
2013-04-16 8:16 ` Peter Ujfalusi [this message]
2013-04-16 8:16 ` Peter Ujfalusi
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=516D08C0.70702@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=a.zummo@towertech.it \
--cc=chf.fritz@googlemail.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=tomi.valkeinen@iki.fi \
--cc=tony@atomide.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.