From: Tony Lindgren <tony@atomide.com>
To: Franklin S Cooper Jr <fcooper@ti.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux@arm.linux.org.uk, rogerq@ti.com, nm@ti.com,
lokeshvutla@ti.com
Subject: Re: [PATCH 2/2] ARM: omap4: hwmod: Remove elm address space from hwmod data
Date: Mon, 30 Nov 2015 13:19:13 -0800 [thread overview]
Message-ID: <20151130211912.GS2517@atomide.com> (raw)
In-Reply-To: <1446066137-11527-3-git-send-email-fcooper@ti.com>
* Franklin S Cooper Jr <fcooper@ti.com> [151028 14:02]:
> ELM address information is provided by device tree. No longer need
> to include this information within hwmod.
>
> This patch has only been boot tested.
>
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
And this one seems safe for me to apply into omap-for-v4.5/soc thanks.
Tony
> ---
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index 43eebf2..8f13f4a 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -3915,21 +3915,11 @@ static struct omap_hwmod_ocp_if omap44xx_l4_per__dss_venc = {
> .user = OCP_USER_MPU,
> };
>
> -static struct omap_hwmod_addr_space omap44xx_elm_addrs[] = {
> - {
> - .pa_start = 0x48078000,
> - .pa_end = 0x48078fff,
> - .flags = ADDR_TYPE_RT
> - },
> - { }
> -};
> -
> /* l4_per -> elm */
> static struct omap_hwmod_ocp_if omap44xx_l4_per__elm = {
> .master = &omap44xx_l4_per_hwmod,
> .slave = &omap44xx_elm_hwmod,
> .clk = "l4_div_ck",
> - .addr = omap44xx_elm_addrs,
> .user = OCP_USER_MPU | OCP_USER_SDMA,
> };
>
> --
> 2.6.1
>
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: omap4: hwmod: Remove elm address space from hwmod data
Date: Mon, 30 Nov 2015 13:19:13 -0800 [thread overview]
Message-ID: <20151130211912.GS2517@atomide.com> (raw)
In-Reply-To: <1446066137-11527-3-git-send-email-fcooper@ti.com>
* Franklin S Cooper Jr <fcooper@ti.com> [151028 14:02]:
> ELM address information is provided by device tree. No longer need
> to include this information within hwmod.
>
> This patch has only been boot tested.
>
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
And this one seems safe for me to apply into omap-for-v4.5/soc thanks.
Tony
> ---
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index 43eebf2..8f13f4a 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -3915,21 +3915,11 @@ static struct omap_hwmod_ocp_if omap44xx_l4_per__dss_venc = {
> .user = OCP_USER_MPU,
> };
>
> -static struct omap_hwmod_addr_space omap44xx_elm_addrs[] = {
> - {
> - .pa_start = 0x48078000,
> - .pa_end = 0x48078fff,
> - .flags = ADDR_TYPE_RT
> - },
> - { }
> -};
> -
> /* l4_per -> elm */
> static struct omap_hwmod_ocp_if omap44xx_l4_per__elm = {
> .master = &omap44xx_l4_per_hwmod,
> .slave = &omap44xx_elm_hwmod,
> .clk = "l4_div_ck",
> - .addr = omap44xx_elm_addrs,
> .user = OCP_USER_MPU | OCP_USER_SDMA,
> };
>
> --
> 2.6.1
>
next prev parent reply other threads:[~2015-11-30 21:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 21:02 [PATCH 0/2] Remove elm address space from omap4 hwmod Franklin S Cooper Jr
2015-10-28 21:02 ` Franklin S Cooper Jr
2015-10-28 21:02 ` [PATCH 1/2] ARM: dts: omap4: Add elm node Franklin S Cooper Jr
2015-10-28 21:02 ` Franklin S Cooper Jr
2015-11-30 21:17 ` Tony Lindgren
2015-11-30 21:17 ` Tony Lindgren
2015-10-28 21:02 ` [PATCH 2/2] ARM: omap4: hwmod: Remove elm address space from hwmod data Franklin S Cooper Jr
2015-10-28 21:02 ` Franklin S Cooper Jr
2015-11-30 21:19 ` Tony Lindgren [this message]
2015-11-30 21:19 ` Tony Lindgren
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=20151130211912.GS2517@atomide.com \
--to=tony@atomide.com \
--cc=fcooper@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=rogerq@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.