linux-kernel - Re: [PATCH 2/2] mfd: arizona: Correct mask to allow setting micbias external cap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140924115813.GN19999@lee--X1>
Date:	Wed, 24 Sep 2014 12:58:14 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	sameo@...ux.intel.com, patches@...nsource.wolfsonmicro.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] mfd: arizona: Correct mask to allow setting micbias
 external cap

On Wed, 24 Sep 2014, Charles Keepax wrote:

> Currently the mask for the external capacitor bit is missing when
> writing the MICBIAS config meaning it will never be set this patch fixes
> this.
> 
> Signed-off-by: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
> ---
>  drivers/mfd/arizona-core.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)

Applied, thanks.

> diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
> index 72b3202..bce7c07 100644
> --- a/drivers/mfd/arizona-core.c
> +++ b/drivers/mfd/arizona-core.c
> @@ -947,6 +947,7 @@ int arizona_dev_init(struct arizona *arizona)
>  		regmap_update_bits(arizona->regmap,
>  				   ARIZONA_MIC_BIAS_CTRL_1 + i,
>  				   ARIZONA_MICB1_LVL_MASK |
> +				   ARIZONA_MICB1_EXT_CAP |
>  				   ARIZONA_MICB1_DISCH |
>  				   ARIZONA_MICB1_BYPASS |
>  				   ARIZONA_MICB1_RATE, val);

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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/