From: Suman Anna <s-anna@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>, Dave Gerlach <d-gerlach@ti.com>,
Jassi Brar <jaswinder.singh@linaro.org>,
Pavel Machek <pavel@ucw.cz>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, Rajendra Nayak <rnayak@ti.com>
Subject: Re: [PATCHv2 06/10] ARM: DRA7: hwmod_data: Add mailbox hwmod data
Date: Tue, 15 Jul 2014 11:57:12 -0500 [thread overview]
Message-ID: <53C55D68.8050308@ti.com> (raw)
In-Reply-To: <20140715133013.GA2605@atomide.com>
Hi Tony,
On 07/15/2014 08:30 AM, Tony Lindgren wrote:
> * Suman Anna <s-anna@ti.com> [140711 14:47]:
>> Add the hwmod data for the 13 instances of the system mailbox
>> IP in DRA7 SoC. The patch is needed for performing a soft-reset
>> while configuring the respective mailbox instance, otherwise is
>> a non-essential change for functionality. The modules are smart
>> idled on reset, and the IP module mode is hardware controlled.
>>
>> Cc: Rajendra Nayak <rnayak@ti.com>
>> Cc: Paul Walmsley <paul@pwsan.com>
>> Signed-off-by: Suman Anna <s-anna@ti.com>
>> ---
>> arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 305 ++++++++++++++++++++++++++++++
>> 1 file changed, 305 insertions(+)
>>
>> diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c b/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
>> index 20b4398..e35f5b1 100644
>> --- a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
>> +++ b/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
>> @@ -939,6 +939,194 @@ static struct omap_hwmod dra7xx_i2c5_hwmod = {
>> };
>>
>> /*
>> + * 'mailbox' class
>> + *
>> + */
>> +
>> +static struct omap_hwmod_class_sysconfig dra7xx_mailbox_sysc = {
>> + .rev_offs = 0x0000,
>> + .sysc_offs = 0x0010,
>> + .sysc_flags = (SYSC_HAS_RESET_STATUS | SYSC_HAS_SIDLEMODE |
>> + SYSC_HAS_SOFTRESET),
>> + .idlemodes = (SIDLE_FORCE | SIDLE_NO | SIDLE_SMART),
>> + .sysc_fields = &omap_hwmod_sysc_type2,
>> +};
>> +
>> +static struct omap_hwmod_class dra7xx_mailbox_hwmod_class = {
>> + .name = "mailbox",
>> + .sysc = &dra7xx_mailbox_sysc,
>> +};
>
> Hmm I'm seeing just the following MAILBOX_SYSCONFIG in at least
> am57xx TRM:
>
> 31:4 RESERVED
> 3:2 SIDLEMODE 0 = force-idle 1 = no-idle, 2 = smart-idle, 3 = reserved
> 1 RESERVED
> 0 SOFTRESET
>
> So it seems that SYSC_HAS_RESET_STATUS above is wrong? Can you guys
> please check.
The same SOFTRESET bit is used for both triggering the softreset and
reading the reset done status. Once you write a 1 to trigger a reset,
the bit will be cleared once the reset is done. This is no different
from OMAP4. The logic in _wait_softreset_complete in omap_hwmod.c was
already designed to work with this properly.
regards
Suman
next prev parent reply other threads:[~2014-07-15 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 21:44 [PATCHv2 00/10] OMAP Mailbox DT node/hwmod cleanup Suman Anna
2014-07-11 21:44 ` [PATCHv2 01/10] ARM: dts: OMAP2+: Add mailbox fifo and user information Suman Anna
2014-07-12 22:13 ` Pavel Machek
2014-07-11 21:44 ` [PATCHv2 02/10] ARM: dts: OMAP4: Add mailbox node Suman Anna
2014-07-11 21:44 ` [PATCHv2 03/10] ARM: dts: AM33xx: " Suman Anna
[not found] ` <1405115083-52977-1-git-send-email-s-anna-l0cyMroinI0@public.gmane.org>
2014-07-11 21:44 ` [PATCHv2 04/10] ARM: dts: AM4372: Correct mailbox node data Suman Anna
2014-07-11 21:44 ` [PATCHv2 05/10] ARM: dts: DRA7: Add mailbox nodes Suman Anna
2014-07-11 21:44 ` [PATCHv2 06/10] ARM: DRA7: hwmod_data: Add mailbox hwmod data Suman Anna
2014-07-15 13:30 ` Tony Lindgren
2014-07-15 16:57 ` Suman Anna [this message]
2014-07-16 7:07 ` Tony Lindgren
2014-07-23 9:24 ` Tony Lindgren
2014-07-23 15:18 ` Suman Anna
2014-07-11 21:44 ` [PATCHv2 07/10] ARM: OMAP2+: Avoid mailbox legacy device creation for DT-boot Suman Anna
2014-07-11 21:44 ` [PATCHv2 08/10] ARM: OMAP2: hwmod_data: Remove legacy mailbox data and addrs Suman Anna
2014-07-11 21:44 ` [PATCHv2 09/10] ARM: OMAP4: hwmod_data: Remove legacy mailbox addrs Suman Anna
2014-07-11 21:44 ` [PATCHv2 10/10] ARM: AM33xx: " Suman Anna
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=53C55D68.8050308@ti.com \
--to=s-anna@ti.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=pavel@ucw.cz \
--cc=rnayak@ti.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).