From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: Re: [PATCH] soc: renesas: r8a774c0-sysc: Fix initialization order of 3DG-{A,B}
Date: Wed, 2 Jan 2019 11:42:48 +0100 [thread overview]
Message-ID: <CAMuHMdXhLJpvFOjr42v13sAJVja-ivG+6vnoUjWvAWSQML_0=Q@mail.gmail.com> (raw)
In-Reply-To: <1544617031-28114-1-git-send-email-biju.das@bp.renesas.com>
On Wed, Dec 12, 2018 at 1:25 PM Biju Das <biju.das@bp.renesas.com> wrote:
> The workaround for the wrong hierarchy of the 3DG-{A,B} power domains on
> RZ/G2E ES1.0 corrected the parent domains. However, the 3DG-{A,B} power
> domains were still initialized and powered in the wrong order, causing
> 3DG operation to fail.
>
> Fix this by changing the order in the table at runtime, when running on
> an affected SoC.
>
> This work is based on the work done by Geert for R-Car E3.
>
> Fixes: f37d211c687588328 ("soc: renesas: rcar-sysc: Add r8a774c0 support")
>
> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
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
prev parent reply other threads:[~2019-01-02 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 12:17 [PATCH] soc: renesas: r8a774c0-sysc: Fix initialization order of 3DG-{A,B} Biju Das
2018-12-13 11:18 ` Simon Horman
2018-12-14 15:59 ` Simon Horman
2019-01-02 9:39 ` Simon Horman
2019-01-02 10:39 ` Geert Uytterhoeven
2019-01-04 9:04 ` Simon Horman
2019-01-07 8:34 ` Geert Uytterhoeven
2019-01-07 13:52 ` Simon Horman
2019-01-02 15:11 ` Biju Das
2019-01-02 10:42 ` 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='CAMuHMdXhLJpvFOjr42v13sAJVja-ivG+6vnoUjWvAWSQML_0=Q@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).