Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/5] mfd: exynos-lpass: Use common soc/exynos-regs-pmu.h header
Date: Wed, 15 Mar 2017 10:10:07 +0000	[thread overview]
Message-ID: <20170315101007.xtnwz7mmkt446sgd@dell> (raw)
In-Reply-To: <20170314164653.15771-5-krzk@kernel.org>

On Tue, 14 Mar 2017, Krzysztof Kozlowski wrote:

> The MFD-specific header will go away because it duplicates defines from
> exynos-regs-pmu.h.
> 
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> Reviewed-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> ---
>  drivers/mfd/exynos-lpass.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Applied, thanks.

> diff --git a/drivers/mfd/exynos-lpass.c b/drivers/mfd/exynos-lpass.c
> index 2e064fb8826f..8bebad92a385 100644
> --- a/drivers/mfd/exynos-lpass.c
> +++ b/drivers/mfd/exynos-lpass.c
> @@ -18,11 +18,11 @@
>  #include <linux/io.h>
>  #include <linux/module.h>
>  #include <linux/mfd/syscon.h>
> -#include <linux/mfd/syscon/exynos5-pmu.h>
>  #include <linux/of.h>
>  #include <linux/of_platform.h>
>  #include <linux/platform_device.h>
>  #include <linux/regmap.h>
> +#include <linux/soc/samsung/exynos-regs-pmu.h>
>  #include <linux/types.h>
>  
>  /* LPASS Top register definitions */
> @@ -83,7 +83,7 @@ static void exynos_lpass_enable(struct exynos_lpass *lpass)
>  
>  	/* Activate related PADs from retention state */
>  	regmap_write(lpass->pmu, EXYNOS5433_PAD_RETENTION_AUD_OPTION,
> -		     EXYNOS5433_PAD_INITIATE_WAKEUP_FROM_LOWPWR);
> +		     EXYNOS_WAKEUP_FROM_LOWPWR);
>  
>  	exynos_lpass_core_sw_reset(lpass, LPASS_I2S_SW_RESET);
>  	exynos_lpass_core_sw_reset(lpass, LPASS_DMA_SW_RESET);

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2017-03-15 10:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 16:46 [PATCH v4 0/5] phy/mfd/soc: exynos: Header cleanup Krzysztof Kozlowski
2017-03-14 16:46 ` [PATCH v4 1/5] phy: exynos4: Remove duplicated defines of PHY register defines Krzysztof Kozlowski
2017-03-14 16:46 ` [PATCH v4 2/5] phy: exynos5: " Krzysztof Kozlowski
2017-03-14 16:46 ` [PATCH v4 3/5] phy: exynos-mipi-video: Use consistent method to address phy registers Krzysztof Kozlowski
2017-03-14 16:46 ` [PATCH v4 4/5] mfd: exynos-lpass: Use common soc/exynos-regs-pmu.h header Krzysztof Kozlowski
2017-03-15 10:10   ` Lee Jones [this message]
2017-03-15 11:02     ` Krzysztof Kozlowski
2017-03-15 12:12       ` Lee Jones
2017-03-15 13:15         ` Krzysztof Kozlowski
2017-03-23 10:51   ` [GIT PULL] Immutable branch between MFD and PHY due for the v4.12 merge window Lee Jones
2017-03-23 11:58     ` Krzysztof Kozlowski
2017-03-27 10:26     ` Kishon Vijay Abraham I
2017-03-14 16:46 ` [PATCH v4 5/5] phy: exynos: Use one define for enable bit Krzysztof Kozlowski
2017-03-27 10:26 ` [PATCH v4 0/5] phy/mfd/soc: exynos: Header cleanup Kishon Vijay Abraham I

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=20170315101007.xtnwz7mmkt446sgd@dell \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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