From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: "Huang, Tao" <huangtao@rock-chips.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
zhangqing <zhangqing@rock-chips.com>,
heiko@sntech.de, lee.jones@linaro.org, zyw@rock-chips.com,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
rtc-linux@googlegroups.com
Subject: [rtc-linux] Re: [RESEND PATCH] rtc: rk808: rename rtc-rk808.c to rtc-rk8xx.c
Date: Tue, 5 Jan 2016 09:54:53 +0100 [thread overview]
Message-ID: <20160105085135.GG32724@piout.net> (raw)
In-Reply-To: <568B7F6A.3000607@rock-chips.com>
Hi,
On 05/01/2016 at 16:31:38 +0800, Huang, Tao wrote :
> You and Alexandre are right. The rename is just make the driver more
> readable, i.e. let people know this driver suit for more PMIC no just
> rk808. In fact, I don't care the name is rk808 or rk8xx.
>
For this purpose, you can add the name of the supported PMICs in the
Kconfig.
> The key change of this patch is try to dis-coupling rk808 driver and RTC
> driver. Because of register offset and function is vary between
> different PMIC, we believe it is hard to write one PMIC driver to suit
> all PMIC. So we hope RTC driver can share between all PMIC from rockchip.
>
> Please review this code:
>
> -static int rk808_rtc_probe(struct platform_device *pdev)
> +static int rk8xx_rtc_probe(struct platform_device *pdev)
> {
> - struct rk808 *rk808 = dev_get_drvdata(pdev->dev.parent);
> ...
> + struct i2c_client *client = to_i2c_client(pdev->dev.parent);
>
> ...
>
> - rk808_rtc->rk808 = rk808;
> + rk8xx_rtc->regmap = devm_regmap_init_i2c(client,
> + &rk8xx_rtc_regmap_config);
> ...
> + rk8xx_rtc->i2c = client;
>
> Old driver have struct rk808 pointer, which defined on
> include/linux/mfd/rk808.h
> If we write new PMIC driver, for example rk818, define a new struct
> rk818. How can we get this pointer from RTC driver?
>
> So another way to solve this problem is introduce common struct share
> between all PMIC driver. For example rk8xx.
>
That is probably the best solution. If you want to reuse drivers between
pmic, then have a common structure that you can pass to those drivers.
I believe the regmap_init_i2c should stay in the MFD driver.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
--
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.
prev parent reply other threads:[~2016-01-05 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 14:14 [rtc-linux] [RESEND PATCH] rtc: rk808: rename rtc-rk808.c to rtc-rk8xx.c zhangqing
2016-01-04 9:14 ` [rtc-linux] " Kever Yang
2016-01-04 9:45 ` Alexandre Belloni
2016-01-04 13:59 ` Alessandro Zummo
2016-01-05 8:31 ` Huang, Tao
2016-01-05 8:54 ` Alexandre Belloni [this message]
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=20160105085135.GG32724@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rtc-linux@googlegroups.com \
--cc=zhangqing@rock-chips.com \
--cc=zyw@rock-chips.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