linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: shmobile: Correct SYSCIER values
Date: Thu, 12 Mar 2015 08:21:56 +0000	[thread overview]
Message-ID: <CAMuHMdUh=FE4_ZrKKg03aEKCWNhWWdNVHN361v39aA2JZKyFHQ@mail.gmail.com> (raw)
In-Reply-To: <20150312081442.GA4295@verge.net.au>

Hi Simon,

On Thu, Mar 12, 2015 at 9:14 AM, Simon Horman <horms@verge.net.au> wrote:
> FWIW the values in these patches are the ones that
> you supplied in another email thread. However, I did
> verify them against (my reading of) the documentation.

We could introduce symbols for them. I don't think it's worth doing that at
this point, as ideally these values should come from DT.

If you disagree, feel free to use what I was carrying in my local tree
to get a better understanding (needs some consolidation):

/* SYSC Interrupt Status/Status Clear/Enable/Mask Register */
/* R-Car H1 */
#define SYSCI_IMP               BIT(24) /* IMP-X3 */
#define SYSCI_VDP               BIT(21) /* VDP1 */
#define SYSCI_SGX               BIT(20) /* SGX543 MP2 */
#define SYSCI_SH4A              BIT(16) /* SH-4A (Not documented on H1) */
#define SYSCI_ARM3              BIT(3)  /* ARM3 */
#define SYSCI_ARM2              BIT(2)  /* ARM2 */
#define SYSCI_ARM1              BIT(1)  /* ARM1 */

/* R-Car H2 */
#define SYSCI_IMP               BIT(24) /* IMP-X4 */
#define SYSCI_CA7_SCU           BIT(21) /* CA7-SCU */
#define SYSCI_RGX               BIT(20) /* RGX */
#define SYSCI_SH4A              BIT(16) /* SH-4A */
#define SYSCI_CA15_SCU          BIT(12) /* CA15-SCU */
#define SYSCI_CA7_CPU(i)        BIT(5 + (i))    /* CA7-CPUi */
#define SYSCI_CA15_CPU(i)       BIT(i)  /* CA15-CPUi */

/* R-Car M2-W/M2-N */
#define SYSCI_SGX               BIT(20) /* SGX */
#define SYSCI_SH4A              BIT(16) /* SH-4A */
#define SYSCI_CA15_SCU          BIT(12) /* CA15-SCU */
#define SYSCI_CA15_CPU(i)       BIT(i)  /* CA15-CPUi */

/* R-Car V2H */
#define SYSCI_IMP               BIT(24) /* IMP-X4 */
#define SYSCI_SGX               BIT(20) /* SGX */
#define SYSCI_CA15_SCU          BIT(12) /* CA15-SCU */
#define SYSCI_CA15_CPU(i)       BIT(i)  /* CA15-CPUi */

/* R-Car E2 */
#define SYSCI_CA7_SCU           BIT(21) /* CA7-SCU */
#define SYSCI_SGX               BIT(20) /* SGX */
#define SYSCI_SH4A              BIT(16) /* SH-4A */
#define SYSCI_CA7_CPU(i)        BIT(5 + (i))    /* CA7-CPUi */

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2015-03-12  8:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  3:55 [PATCH 0/2] ARM: shmobile: Correct SYSCIER values Simon Horman
2015-03-12  3:55 ` [PATCH 1/2] ARM: shmobile: r8a7790: Correct SYSCIER value Simon Horman
2015-03-12  3:55 ` [PATCH 2/2] ARM: shmobile: r8a7791: " Simon Horman
2015-03-12  8:03 ` [PATCH 0/2] ARM: shmobile: Correct SYSCIER values Geert Uytterhoeven
2015-03-12  8:14   ` Simon Horman
2015-03-12  8:21     ` Geert Uytterhoeven [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='CAMuHMdUh=FE4_ZrKKg03aEKCWNhWWdNVHN361v39aA2JZKyFHQ@mail.gmail.com' \
    --to=geert@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).