[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <9524a32b-d7f5-487c-e791-12bf0554a90f@norik.com>
Date: Fri, 3 Dec 2021 09:59:02 +0100
From: Andrej Picej <andrej.picej@...ik.com>
To: Christoph Niedermaier <cniedermaier@...electronics.com>,
"support.opensource@...semi.com" <support.opensource@...semi.com>,
"linux@...ck-us.net" <linux@...ck-us.net>,
"linux-watchdog@...r.kernel.org" <linux-watchdog@...r.kernel.org>
Cc: "wim@...ux-watchdog.org" <wim@...ux-watchdog.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"festevam@...il.com" <festevam@...il.com>,
"linux-imx@....com" <linux-imx@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v4 1/4] mfd: da9062: make register CONFIG_I writable
On 2. 12. 21 16:18, Christoph Niedermaier wrote:
> From: Andrej Picej
> Sent: Thursday, December 2, 2021 10:32 AM
>> From: Stefan Christ <s.christ@...tec.de>
>>
>> Make the config register CONFIG_I writable to change the watchdog mode.
>>
>> Signed-off-by: Stefan Christ <s.christ@...tec.de>
>> Signed-off-by: Andrej Picej <andrej.picej@...ik.com>
>> ---
>> Chnages in v4:
>> - no changes
>>
>> Changes in v3:
>> - no chagnes
>>
>> Changes in v2:
>> - no changes
>> ---
>> drivers/mfd/da9062-core.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/mfd/da9062-core.c b/drivers/mfd/da9062-core.c
>> index 01f8e10dfa55..7041ba53efb4 100644
>> --- a/drivers/mfd/da9062-core.c
>> +++ b/drivers/mfd/da9062-core.c
>> @@ -556,6 +556,7 @@ static const struct regmap_range
>> da9062_aa_writeable_ranges[] = {
>> regmap_reg_range(DA9062AA_VBUCK3_B, DA9062AA_VBUCK3_B),
>> regmap_reg_range(DA9062AA_VLDO1_B, DA9062AA_VLDO4_B),
>> regmap_reg_range(DA9062AA_BBAT_CONT, DA9062AA_BBAT_CONT),
>> + regmap_reg_range(DA9062AA_CONFIG_I, DA9062AA_CONFIG_I),
>> regmap_reg_range(DA9062AA_GP_ID_0, DA9062AA_GP_ID_19),
>> };
> Could you also include the CONFIG_I for the DA9061?
> So I can test it on my system.
>
Yes, I don't see the problem here.
@Maintainers, should I send a new version with this (then I would also
fix the minor spelling mistake in commit message of 2/4), or do you
prefer a separate patch?
Thanks,
Andrej.
Powered by blists - more mailing lists