[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111226112605.GD8722@opensource.wolfsonmicro.com>
Date: Mon, 26 Dec 2011 11:26:06 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Sangbeom Kim <sbkim73@...sung.com>
Cc: sameo@...ux.intel.com, lrg@...com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 4/5] regulator: Add S5M8767 regulator driver
On Fri, Dec 23, 2011 at 05:28:11PM +0900, Sangbeom Kim wrote:
> + ret = s5m_reg_read(s5m8767->iodev, reg, &val);
> + if (ret)
> + return ret;
> +
> + val &= mask;
> +
> + if (rdev->desc && rdev->desc->ops && rdev->desc->ops->list_voltage)
> + return rdev->desc->ops->list_voltage(rdev, val);
> +
> + return s5m8767_list_voltage(rdev, val);
This looks really weird, I'm not sure why you're looking directly in the
descriptor. In any case, just implement get_voltage_sel() rather than
plain get_voltage() and the core will do the lookup for you.
> + s5m_reg_read(s5m8767->iodev, reg, &val);
> + val = val & mask;
> +
> + ret = s5m_reg_update(s5m8767->iodev, reg, i, mask);
> + *selector = i;
This looks odd - shouldn't reg_update() already be masking things for
you.
> +
> + if (val < i){
> + udelay(DIV_ROUND_UP(desc->step * (i - val),
> + s5m8767->ramp_delay));
> + }
You should implement set_voltage_time_sel() and drop this, the core will
add the delay for you.
Also note the odd indentation and whitespace with a lot of this code.
> + case S5M8767_BUCK2:
> + if(s5m8767->buck2_gpiodvs){
> + while ( s5m8767->buck2_vol[i] != new_val )
> + i++;
This has some of the other odd whitespace - not enough spaces on the
line with the if () but extras inside the () on the while.
> + s5m8767 = kzalloc(sizeof(struct s5m8767_info), GFP_KERNEL);
> + if (!s5m8767)
> + return -ENOMEM;
devm_kzalloc().
> + size = sizeof(struct regulator_dev *) * pdata->num_regulators;
Just have fixed size arrays for the regulators and always register them
- it's less error prone and makes the code simpler.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists