From: Mugunthan V N <mugunthanvnm@ti.com>
To: Afzal Mohammed <afzal@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Paul Walmsley <paul@pwsan.com>,
"Benoit Cousson (benoit.cousson@linaro.org)"
<benoit.cousson@linaro.org>, Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH 1/2] ARM: OMAP2+: hwmod: rt address space index for DT
Date: Thu, 25 Jul 2013 15:30:40 +0530 [thread overview]
Message-ID: <51F0F748.9020904@ti.com> (raw)
In-Reply-To: <4bb04ee7bcb8ca73d5fc43049ba029471b9cdda3.1373036932.git.afzal@ti.com>
On 7/5/2013 8:43 PM, Afzal Mohammed wrote:
> Address space is being removed from hwmod database and DT information
> in <reg> property is being used. Currently the 0th index of device
> address space is used to map for register target address. This is not
> always true, eg. cpgmac has it's sysconfig in second address space.
>
> Handle it by specifying index of device address space to be used for
> register target. As default value of this field would be zero with
> static initialization, existing behaviour of using first address space
> for register target while using DT would be kept as such.
>
> Signed-off-by: Afzal Mohammed <afzal@ti.com>
I have tested this patch and it's needed when we have CPSW Ethernet built-in to
go to low power state.
Tested-by: Mugunthan V N <mugunthanvnm@ti.com>
Regards
Mugunthan V N
prev parent reply other threads:[~2013-07-25 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 15:13 [PATCH 1/2] ARM: OMAP2+: hwmod: rt address space index for DT Afzal Mohammed
2013-07-05 15:13 ` [PATCH 2/2] ARM: OMAP2+: hwmod: AM335x: fix cpgmac address space Afzal Mohammed
2013-07-25 10:01 ` Mugunthan V N
2013-07-24 13:38 ` [PATCH 1/2] ARM: OMAP2+: hwmod: rt address space index for DT Afzal Mohammed
2013-07-25 10:00 ` Mugunthan V N [this message]
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=51F0F748.9020904@ti.com \
--to=mugunthanvnm@ti.com \
--cc=afzal@ti.com \
--cc=benoit.cousson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul@pwsan.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).