From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Guenter Roeck <linux@roeck-us.net>,
qemu-devel@nongnu.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH RFC] hw/sh4/sh7750: Add STBCR/STBCR2 register support
Date: Thu, 19 Oct 2023 11:03:39 +0900 [thread overview]
Message-ID: <875y338j2c.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20231018124023.2927710-1-geert+renesas@glider.be>
On Wed, 18 Oct 2023 21:40:23 +0900,
Geert Uytterhoeven wrote:
>
> The new Linux SH7750 clock driver uses the registers for power-down
> mode control, causing a crash:
>
> byte read to SH7750_STBCR_A7 (0x000000001fc00004) not supported
> Aborted (core dumped)
>
> Fix this by adding support for the Standby Control Registers STBCR and
> STBCR2.
FRQCR is also not returning the correct value, so it needs to be fixed.
Here are my changes.
https://gitlab.com/yoshinori.sato/qemu.git
It include.
- Minimal CPG support.
- DT support
- Add target LANDISK.
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> [RFC PATCH v3 12/35] drivers/clk/renesas: clk-sh7750.c SH7750/7751 CPG driver.
> https://lore.kernel.org/all/a772e1b6de89af22057d3af31cc03dcad7964fc7.1697199949.git.ysato@users.sourceforge.jp
>
> Accesses to CLKSTP00 and CLKSTCLK00 (0xfe0a0000/0x1e0a0000 and
> 0xfe0a0008/0x1e0a0008) don't seem to cause any issues, although I can't
> see immediately where they are handled?
>
> ---
> hw/sh4/sh7750.c | 23 +++++++++++++++++++++--
> 1 file changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/hw/sh4/sh7750.c b/hw/sh4/sh7750.c
> index ebe0fd96d94ca17b..deeb83b4540bbf2b 100644
> --- a/hw/sh4/sh7750.c
> +++ b/hw/sh4/sh7750.c
> @@ -59,6 +59,9 @@ typedef struct SH7750State {
> uint16_t bcr3;
> uint32_t bcr4;
> uint16_t rfcr;
> + /* Power-Down Modes */
> + uint8_t stbcr;
> + uint8_t stbcr2;
> /* PCMCIA controller */
> uint16_t pcr;
> /* IO ports */
> @@ -219,7 +222,13 @@ static void ignore_access(const char *kind, hwaddr addr)
>
> static uint32_t sh7750_mem_readb(void *opaque, hwaddr addr)
> {
> + SH7750State *s = opaque;
> +
> switch (addr) {
> + case SH7750_STBCR_A7:
> + return s->stbcr;
> + case SH7750_STBCR2_A7:
> + return s->stbcr2;
> default:
> error_access("byte read", addr);
> abort();
> @@ -318,14 +327,24 @@ static uint32_t sh7750_mem_readl(void *opaque, hwaddr addr)
> static void sh7750_mem_writeb(void *opaque, hwaddr addr,
> uint32_t mem_value)
> {
> + SH7750State *s = opaque;
>
> if (is_in_sdrmx(addr, 2) || is_in_sdrmx(addr, 3)) {
> ignore_access("byte write", addr);
> return;
> }
>
> - error_access("byte write", addr);
> - abort();
> + switch (addr) {
> + case SH7750_STBCR_A7:
> + s->stbcr = mem_value;
> + return;
> + case SH7750_STBCR2_A7:
> + s->stbcr2 = mem_value;
> + return;
> + default:
> + error_access("byte write", addr);
> + abort();
> + }
> }
>
> static void sh7750_mem_writew(void *opaque, hwaddr addr,
> --
> 2.34.1
>
--
Yosinori Sato
next prev parent reply other threads:[~2023-10-19 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 12:40 [PATCH RFC] hw/sh4/sh7750: Add STBCR/STBCR2 register support Geert Uytterhoeven
2023-10-18 12:46 ` John Paul Adrian Glaubitz
2023-10-18 13:03 ` Geert Uytterhoeven
2023-10-19 2:03 ` Yoshinori Sato [this message]
2023-10-19 7:14 ` Geert Uytterhoeven
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=875y338j2c.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=geert+renesas@glider.be \
--cc=linux-sh@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=qemu-devel@nongnu.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).