From: Wolfram Sang <w.sang@pengutronix.de>
To: Jain Priyanka-B32167 <B32167@freescale.com>
Cc: "a.zummo@towertech.it" <a.zummo@towertech.it>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
"p_gortmaker@yahoo.com" <p_gortmaker@yahoo.com>
Subject: Re: [rtc-linux] [PATCH] RTC driver(Linux) for PT7C4338 chip.
Date: Thu, 10 Mar 2011 09:54:14 +0100 [thread overview]
Message-ID: <20110310085414.GA4460@pengutronix.de> (raw)
In-Reply-To: <470DB7CE2CD0944E9436E7ADEFC02FE313B1C2@039-SN1MPN1-003.039d.mgd.msft.net>
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
Hi Priyanka,
> Though register-set looks identical but features were different.
Can you tell what exactly is different?
> And also manufacturer is different.
That does not matter. If you look at ds_type, there are already
different manufacturers. They will be correctly distinguished by
i2c_device_id. The name of the driver itself is, well, just a name.
> But still it might be possible that we can reuse ds1307.c with some
> modification.
I agree. The driver already supports some variants. Adding one more
should not hurt. See 97f902b7be4dd6ba03c6aa8d3400783ed687ebd1 for an
example which added ds3231 support.
> But if I look at the drivers present in drivers/rtc folder. Most of
> them looks similar but still there are different drivers for different
> chips.
Yes, it probably could be cleaned up if somebody had the time/hardware.
> Please suggest which way is more preferred: modifying existing
> drivers(of different manufacturer) or writing new driver.
Ususally avoiding code duplication is good, it reduces maintenance
burden. However, if adding the support turns out to make the original
code unreadable or hard to follow, a new driver might be justified. This
is why it is important to understand the differences of the chip as a
first step. (I have the feeling, that modifying is the way to go here,
though).
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-10 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 3:51 [PATCH] RTC driver(Linux) for PT7C4338 chip Priyanka Jain
2011-03-03 9:22 ` [rtc-linux] " Wolfram Sang
2011-03-09 0:55 ` Andrew Morton
2011-03-09 6:46 ` Wolfram Sang
2011-03-10 3:23 ` Jain Priyanka-B32167
2011-03-10 8:54 ` Wolfram Sang [this message]
2011-03-10 11:06 ` Jain Priyanka-B32167
2011-05-25 23:56 ` Andrew Morton
2011-05-26 7:11 ` Jain Priyanka-B32167
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=20110310085414.GA4460@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=B32167@freescale.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=p_gortmaker@yahoo.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 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.