[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8ec691a9-d91c-752b-de21-a82a7e78ee05@linaro.org>
Date: Wed, 24 Oct 2018 11:50:45 +0100
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Lee Jones <lee.jones@...aro.org>
Cc: robh+dt@...nel.org, broonie@...nel.org, mark.rutland@....com,
lgirdwood@...il.com, bgoswami@...eaurora.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
vkoul@...nel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH v4 02/14] mfd: wcd9335: add support to wcd9335 core
On 24/10/18 08:07, Lee Jones wrote:
>> +#define WCD9335_SLIM_INTERFACE_DEVICE_INDEX 0
>> +
>> +static const struct mfd_cell wcd9335_devices[] = {
>> + { .name = "wcd9335-codec", },
>> +};
> Any news on other devices?
>
We are totally limited with hardware to test other devices on this
codec. Given the fact that no one is actively working on adding support
to other devices ATM.
Also IRC discussions with you suggested that I should move this driver
to codecs for now and when a new device support comes up we can move it
back to mfd.
Regarding other comments, I will make sure that address them if the code
is still there after moving to codecs.
thanks,
srini
>> +static const struct regmap_range_cfg wcd9335_ranges[] = {
>> + {
>> + .name = "WCD9335",
>> + .range_min = 0x0,
>> + .range_max = WCD9335_MAX_REGISTER,
>> + .selector_reg = WCD9335_REG(0x0, 0),
>> + .selector_mask = 0xff,
>> + .selector_shift = 0,
>> + .window_start = 0x0,
>> + .window_len = 0x1000,
>> + },
>> +};
Powered by blists - more mailing lists