From: Gaku Inami <gaku.inami.xw@bp.renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/5] ARM: shmobile: r8a7794 SYSC setup code
Date: Thu, 05 Mar 2015 04:23:15 +0000 [thread overview]
Message-ID: <54F7DA33.6040008@bp.renesas.com> (raw)
In-Reply-To: <54F50C56.5030605@bp.renesas.com>
Hi Geert-san,
On 2015/03/04 17:41, Geert Uytterhoeven wrote:
> Hi Inami-san,
>
> On Wed, Mar 4, 2015 at 5:46 AM, Gaku Inami <gaku.inami.xw@bp.renesas.com> wrote:
>>>> +static void __init r8a7794_sysc_init(void)
>>>> +{
>>>> + void __iomem *base = rcar_sysc_init(0xe6180000);
>>>> +
>>>> + /* enable all interrupt sources, but do not use interrupt handler */
>>>> + iowrite32(0x00310060, base + SYSCIER);
>>> Is it intentional that 0x00310060 differs from
>>> the value of 0x0131000e used on the r8a7790 and r8a7791?
>> Yes. According to R-CAR Gen2 HW manual, interrupt bits are
>> different in each SoC. Therefore, I think the setting value
>> of SYSCIER should be set to a different value in each SoC.
>>
>> *Setting value of SYSCIER
>> r8a7790 : 0x013111EF
>> r8a7791 : 0x00111003
>> r8a7794 : 0x00310060
>>
>> I don't know why the value of 0x0131000e is used on the r8a7790
>> and the r8a7791. (maybe wrong value)
> This value was most probably just copied from pm-r8a7779.c
> R-Car H1 has 4 four ARM cores, but there's no interrupt bit for ARM0,
> hence the 0xe value for the lowest nibble.
>
Thank you for your comment. That make sense.
Regards,
Inami
next prev parent reply other threads:[~2015-03-05 4:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 1:20 [PATCH 1/5] ARM: shmobile: r8a7794 SYSC setup code Gaku Inami
2015-03-04 1:40 ` Simon Horman
2015-03-04 4:46 ` Gaku Inami
2015-03-04 8:41 ` Geert Uytterhoeven
2015-03-05 4:23 ` Gaku Inami [this message]
2015-03-06 11:27 ` Simon Horman
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=54F7DA33.6040008@bp.renesas.com \
--to=gaku.inami.xw@bp.renesas.com \
--cc=linux-sh@vger.kernel.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 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.