On Thu, Oct 14, 2010 at 02:38:49PM -0400, Cyril Chemparathy wrote:
> TPS6524X provides three step-down converters and two general-purpose LDO
> voltage regulators. This device is interfaced using SPI.
>
> Signed-off-by: Cyril Chemparathy <[email protected]>
This looks mostly good but...
> +static int read(struct tps6524x *hw, int reg)
> +{
I suspect you may run into a namespace issue with this in the future.
> +static const int dcdc1_voltages[] = {
> + 800000, 825000, 850000, 875000,
> + 900000, 925000, 950000, 975000,
> + 1000000, 1025000, 1050000, 1075000,
> + 1100000, 1125000, 1150000, 1175000,
> + 1200000, 1225000, 1250000, 1275000,
> + 1300000, 1325000, 1350000, 1375000,
> + 1400000, 1425000, 1450000, 1475000,
> + 1500000, 1525000, 1550000, 1575000,
Looks like you could just do the maths for most of these tables, might
be a bit clearer/simpler? Not a major issue either way, though.
> +static int list_voltage(struct regulator_dev *rdev, unsigned selector)
> +{
> + const struct supply_info *info;
> + struct tps6524x *hw;
> +
> + hw = rdev_get_drvdata(rdev);
> + info = &supply_info[rdev_get_id(rdev)];
> +
> + if (info->flags & FIXED_VOLTAGE)
> + return selector ? -EINVAL : info->fixed_voltage;
> + else
> + return (selector < 0 || selector >= info->n_voltages) ?
> + -EINVAL : info->voltages[selector];
I'm not sure the ternery operator is helping legibility here - if
statements might be more legible.
> + ret = read_field(hw, &info->voltage);
> + if (ret < 0)
> + return ret;
> + if (ret >= info->n_voltages)
> + return -EINVAL;
Shouldn't this be warning somehow - if we can't understand the register
setting that'd be a driver bug, -EINVAL makes it sound like an invalid
parameter was supplied. Similarly for the current limit.
> +static ssize_t show_reg(struct device *dev, struct device_attribute *attr,
> + char *buf);
> +static ssize_t store_reg(struct device *dev, struct device_attribute *attr,
> + const char *buf, size_t size);
> +
> +static DEVICE_ATTR(ldo_set, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(block_en, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(dcdc_set, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(dcdc_en, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(usb, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(alarm, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(int_enable, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(int_status, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(rev_id, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(write_enable, 0664, show_reg, store_reg);
> +static DEVICE_ATTR(software_reset, 0664, show_reg, store_reg);
Large chunks of this looks like it's exporting functionality which is
part of the regulator API to userspace, replicating functionality which
the API provides. Please either remove or replace with standard
functionality.
The USB setting should be integrated with the USB subsystem, assuming
it's changing a USB current limit.
> + init_data = dev->platform_data;
> + if (!init_data) {
> + dev_err(dev, "could not find regulator platform data\n");
> + return -EIO;
> + }
EIO doesn't look right here...
------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
_______________________________________________
spi-devel-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/spi-devel-general
