From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, broonie@kernel.org, lgirdwood@gmail.com,
patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6 RESEND] mfd: arizona: Add missing handling for ISRC3 under/overclocked
Date: Mon, 28 Jul 2014 08:02:54 +0100 [thread overview]
Message-ID: <20140728070254.GI5273@lee--X1> (raw)
In-Reply-To: <1405419710-14789-6-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Tue, 15 Jul 2014, Charles Keepax wrote:
> Some parts have a third ISRC, this patch adds handling for the under and
> overclocked interrupts from this ISRC.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> drivers/mfd/arizona-core.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
Applied, thanks.
> diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
> index e9c3563..ab5cf9a 100644
> --- a/drivers/mfd/arizona-core.c
> +++ b/drivers/mfd/arizona-core.c
> @@ -123,6 +123,8 @@ static irqreturn_t arizona_underclocked(int irq, void *data)
> dev_err(arizona->dev, "AIF2 underclocked\n");
> if (val & ARIZONA_AIF1_UNDERCLOCKED_STS)
> dev_err(arizona->dev, "AIF1 underclocked\n");
> + if (val & ARIZONA_ISRC3_UNDERCLOCKED_STS)
> + dev_err(arizona->dev, "ISRC3 underclocked\n");
> if (val & ARIZONA_ISRC2_UNDERCLOCKED_STS)
> dev_err(arizona->dev, "ISRC2 underclocked\n");
> if (val & ARIZONA_ISRC1_UNDERCLOCKED_STS)
> @@ -192,6 +194,8 @@ static irqreturn_t arizona_overclocked(int irq, void *data)
> dev_err(arizona->dev, "ASRC sync WARP overclocked\n");
> if (val[1] & ARIZONA_ADSP2_1_OVERCLOCKED_STS)
> dev_err(arizona->dev, "DSP1 overclocked\n");
> + if (val[1] & ARIZONA_ISRC3_OVERCLOCKED_STS)
> + dev_err(arizona->dev, "ISRC3 overclocked\n");
> if (val[1] & ARIZONA_ISRC2_OVERCLOCKED_STS)
> dev_err(arizona->dev, "ISRC2 overclocked\n");
> if (val[1] & ARIZONA_ISRC1_OVERCLOCKED_STS)
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-07-28 7:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 10:21 [PATCH 0/6] wm5110 Interrupt Updates Charles Keepax
2014-07-15 10:21 ` [PATCH 1/6 RESEND] mfd: wm5110: Remove non-existant interrupts Charles Keepax
2014-07-28 7:01 ` Lee Jones
2014-07-15 10:21 ` [PATCH 2/6 RESEND] mfd: wm5110: Add in the output done interrupts Charles Keepax
2014-07-28 7:02 ` Lee Jones
2014-07-15 10:21 ` [PATCH 3/6 RESEND] mfd: arizona: Rename thermal shutdown interrupt Charles Keepax
2014-07-28 7:02 ` Lee Jones
2014-07-15 10:21 ` [PATCH 4/6 RESEND] mfd: wm5110: Add new interrupt register definitions Charles Keepax
2014-07-28 7:02 ` Lee Jones
2014-07-15 10:21 ` [PATCH 5/6 RESEND] mfd: arizona: Add missing handling for ISRC3 under/overclocked Charles Keepax
2014-07-28 7:02 ` Lee Jones [this message]
2014-07-15 10:21 ` [PATCH 6/6 RESEND] mfd: arizona: Only free the CTRLIF_ERR IRQ if we requested it Charles Keepax
2014-07-28 7:03 ` Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140728070254.GI5273@lee--X1 \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox