Message ID | 20171108172404.19118-3-alexander.deucher@amd.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Wed, Nov 08, 2017 at 12:24:03PM -0500, Alex Deucher wrote: > regmap_read(regmap, RT5645_VENDOR_ID2, &val); > > + /* > + * Read after 400msec, as it is the interval required between > + * read and power On. > + */ > + msleep(TIME_TO_POWER_MS); > + regmap_read(regmap, RT5645_VENDOR_ID2, &val); > + This leaves the original read in there so we've both got the early read (which might upset things potentially) and the delayed read. Shouldn't we just be adding a msleep() before the existing read?
On 11/8/2017 11:39 PM, Mark Brown wrote: > On Wed, Nov 08, 2017 at 12:24:03PM -0500, Alex Deucher wrote: > >> regmap_read(regmap, RT5645_VENDOR_ID2, &val); >> >> + /* >> + * Read after 400msec, as it is the interval required between >> + * read and power On. >> + */ >> + msleep(TIME_TO_POWER_MS); >> + regmap_read(regmap, RT5645_VENDOR_ID2, &val); >> + > > This leaves the original read in there so we've both got the early read > (which might upset things potentially) and the delayed read. Shouldn't > we just be adding a msleep() before the existing read? > My bad, I should have removed the addition of register read from the patch.
diff --git a/sound/soc/codecs/rt5645.c b/sound/soc/codecs/rt5645.c index 23cc2cb8393f..ce5d2c3c6976 100644 --- a/sound/soc/codecs/rt5645.c +++ b/sound/soc/codecs/rt5645.c @@ -55,6 +55,8 @@ MODULE_PARM_DESC(quirk, "RT5645 pdata quirk override"); #define RT5645_HWEQ_NUM 57 +#define TIME_TO_POWER_MS 400 + static const struct regmap_range_cfg rt5645_ranges[] = { { .name = "PR", @@ -3786,6 +3788,13 @@ static int rt5645_i2c_probe(struct i2c_client *i2c, } regmap_read(regmap, RT5645_VENDOR_ID2, &val); + /* + * Read after 400msec, as it is the interval required between + * read and power On. + */ + msleep(TIME_TO_POWER_MS); + regmap_read(regmap, RT5645_VENDOR_ID2, &val); + switch (val) { case RT5645_DEVICE_ID: rt5645->regmap = devm_regmap_init_i2c(i2c, &rt5645_regmap);