From: stefano babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V6 2/3] PMIC: Add dialog pmic support
Date: Sat, 23 Apr 2011 09:45:59 +0200 [thread overview]
Message-ID: <4DB283B7.8030704@denx.de> (raw)
In-Reply-To: <BANLkTin-CUD+y7MeQyJF3W1Jq49zzTSAiw@mail.gmail.com>
Am 22/04/2011 16:50, schrieb Jason Liu:
Hi Jason,
>> As I can see now, this driver is quite a copy of fsl_pmic.c, with
>> slightly changes. Are you sure we cannot simply change the already
>> provided driver, adding support for the new chip ?
>>
>> I have not read the DA9053 datasheet, but from your patch it seems to me
>> that the relevant changes are:
>> - registers are 1 byte wide instead of 32 bit
>> - different size of register area
>>
>> Really not enough to justify a new driver. All functions are really
>> copied from the old one. Please consider to adapt fsl_pmic.c instead of
>> adding a slightly different new one.
>
> fsl_pmic is about freescale mc13892 and fsl_pmic.c is dedicated for fsl pmic
> as you write this file, right?
It was for MC13892, but it is for MC13783 as well, used in i.MX31 boards.
>
> As I add the Dialog PMIC support, I do want to not add one new file, but I find
> it's not easy to add it and it will make the file very mess, so, I
> decide not to touch
> the original file and add one new file. The head of this file tell it
> clear that this patch is
> Based on drivers/misc/fsl_pmic.c.
I do not mind an issue related to set where the driver is coming from.
My concern is due to the fact that your patch is very similar (for the
i2c part) to the fsl_pmic.c file, and I want to avoid to have two
different driver making the same things, having then the necessity to
maintain both. At the end, this file expones only a common interface to
the board maintainers to access the pmic registers (via I2c or SPI as
well). Running diff on the two files I do not see a lot of differences.
>
> If you still want me to include the DA9053 support into fsl_pmic,
> could you please
> extend the fsl_pmic support to easily add another vender's pmic support first?
Really I have not understood your question. What do you mean ?
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-04-23 7:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 12:55 [U-Boot] [PATCH V2 1/1] mx5: board: code clean up for checkboard code Jason Liu
2011-04-22 12:55 ` [U-Boot] [PATCH V6 1/3] MX5: clock: Add clock config interface Jason Liu
2011-04-22 12:55 ` [U-Boot] [PATCH V6 2/3] PMIC: Add dialog pmic support Jason Liu
2011-04-22 14:11 ` Stefano Babic
2011-04-22 14:50 ` Jason Liu
2011-04-23 7:45 ` stefano babic [this message]
2011-04-25 2:59 ` Jason Hui
2011-04-26 12:02 ` Stefano Babic
2011-04-27 9:39 ` Detlev Zundel
2011-04-27 9:44 ` Stefano Babic
2011-05-10 5:39 ` Jason Liu
2011-05-10 8:35 ` Stefano Babic
2011-05-10 8:42 ` Jason Hui
2011-04-23 18:53 ` Wolfgang Denk
2011-04-22 12:55 ` [U-Boot] [PATCH V6 3/3] MX53: support for freescale MX53LOCO board Jason Liu
2011-05-11 7:16 ` [U-Boot] [PATCH V2 1/1] mx5: board: code clean up for checkboard code Jason Liu
2011-05-16 5:48 ` Jason Liu
2011-05-16 6:14 ` Stefano Babic
2011-05-16 6:16 ` Stefano Babic
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=4DB283B7.8030704@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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