From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/6] drivers/power/pmic: Add tps65910 driver
Date: Fri, 26 Jul 2013 08:52:27 -0400 [thread overview]
Message-ID: <20130726125227.GA7424@bill-the-cat> (raw)
In-Reply-To: <51F1635A.1030504@ti.com>
On Thu, Jul 25, 2013 at 12:41:46PM -0500, Dan Murphy wrote:
> On 07/19/2013 02:00 PM, Tom Rini wrote:
> > From: "Philip, Avinash" <avinashphilip@ti.com>
> >
> > Add a driver for the TPS65910 PMIC that is found in the AM335x GP EVM,
> > AM335x EVM SK and others.
>
> Can we add a link to the technical manual?
> http://www.ti.com/product/tps65910
Yup, in the code.
[snip]
> > +/*
> > + * voltage switching for MPU frequency switching.
> > + * @module = mpu - 0, core - 1
> > + * @vddx_op_vol_sel = vdd voltage to set
>
> No return identified here
Fixed.
> > + */
> > +int tps65910_voltage_update(unsigned int module, unsigned char vddx_op_vol_sel)
> > +{
> > + uchar buf[4];
>
> If we only read and write one byte at a time why is this an array of 4?
Fixed.
> > + unsigned int reg_offset;
> > +
> > + if (module == MPU)
> > + reg_offset = TPS65910_VDD1_OP_REG;
> > + else
> > + reg_offset = TPS65910_VDD2_OP_REG;
>
> This seems very specific to the implementation.
>
> Can VDD2 ever be used for the MPU? Or are there constraints on the
> VDD2 SMPS that will not allow that?
Can? Probably. Will someone deviate from the reference design?
Probably not.
> > +
> > + /* Select VDDx OP */
> > + if (i2c_read(TPS65910_CTRL_I2C_ADDR, reg_offset, 1, buf, 1))
> > + return 1;
>
> I am going to assume that you changed this as well like you did for
> the TPS65217?
Correct.
> > +int tps65910_voltage_update(unsigned int module, unsigned char vddx_op_vol_sel);
>
> Nitpick - Don't the interface definitions go at the end of the file?
Sure.
[snip]
> Is this not a family of parts?
>
> http://www.ti.com/product/tps65910
>
> TPS65910, TPS65910A, TPS65910A3, TPS659101, TPS659102, TPS659103
> TPS659104, TPS659105, TPS659106, TPS659107, TPS659108, TPS659109
>
> Do you think we could rename the definitions and the file to TPS65910x?
Fixed the other two minor things, and yes, but if we follow the kernel
example here (note that we didn't copy code) it's still just tps65910
and tps65217 (tps65217 has a/b/c variants).
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130726/82ca76c7/attachment.pgp>
next prev parent reply other threads:[~2013-07-26 12:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 19:00 [U-Boot] [PATCH 1/6] spl/Makefile: Add drivers/power/pmic/libpmic to CONFIG_SPL_POWER_SUPPORT Tom Rini
2013-07-19 19:00 ` [U-Boot] [PATCH 2/6] drivers/power/pmic: Add tps65217 driver Tom Rini
2013-07-23 18:34 ` Dan Murphy
2013-07-25 14:37 ` Tom Rini
2013-07-25 17:21 ` Dan Murphy
2013-07-25 18:05 ` Tom Rini
2013-07-19 19:00 ` [U-Boot] [PATCH 3/6] drivers/power/pmic: Add tps65910 driver Tom Rini
2013-07-25 17:41 ` Dan Murphy
2013-07-26 12:52 ` Tom Rini [this message]
2013-07-19 19:00 ` [U-Boot] [PATCH 4/6] am33xx: Add am33xx_spl_board_init function, call Tom Rini
2013-07-22 14:41 ` [U-Boot] [PATCH v2 " Tom Rini
2013-07-19 19:00 ` [U-Boot] [PATCH 5/6] am33xx: Add the efuse_sma CONTROL_MODULE register Tom Rini
2013-07-19 19:00 ` [U-Boot] [PATCH 6/6] am335x_evm: am33xx_spl_board_init function and scale core frequency Tom Rini
2013-07-19 19:37 ` Enric Balletbo Serra
2013-07-19 19:48 ` Tom Rini
2013-07-19 20:58 ` Tom Rini
2013-07-23 18:46 ` Dan Murphy
2013-07-29 15:57 ` Enric Balletbo Serra
2013-08-07 16:20 ` Tom Rini
2013-08-07 16:56 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2013-08-30 20:28 [U-Boot] [PATCH 1/6] spl/Makefile: Add drivers/power/pmic/libpmic to CONFIG_SPL_POWER_SUPPORT Tom Rini
2013-08-30 20:28 ` [U-Boot] [PATCH 3/6] drivers/power/pmic: Add tps65910 driver Tom Rini
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=20130726125227.GA7424@bill-the-cat \
--to=trini@ti.com \
--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