Devicetree
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Serge Semin" <fancer.lancer@gmail.com>
Cc: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"paulburton@kernel.org" <paulburton@kernel.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 6/6] MIPS: cm: Probe GCR address from DeviceTree
Date: Tue, 10 Sep 2024 21:48:10 +0100	[thread overview]
Message-ID: <b4d57581-bad7-4f6f-8d6f-733f1a5d33ba@app.fastmail.com> (raw)
In-Reply-To: <7j6cc5i4z4nwg73fowjz756eblnesglqm72jveygqfxngw26mc@sdy6xxomo3qe>



在2024年9月10日九月 下午9:07，Serge Semin写道：
[...]
> Both MIPS P5600 and P6600 databooks define the GCR_BASE field as
> optionally R/W:
>
> GCR_BASE 31:15 This field sets the base address of the 32KB          R or R/W
>                GCR block of the P5600 MPS.                           (IP Config-
>                This register has a fixed value after reset if         uration)
>                configured as Read-Only (an IP Configuration Option).
>

Thanks for the pointer, I traced code history and it seems like MIPS decided
to not expose this functionality at some point, but documents were not updated.

Maybe I should add a read back check here.

Thanks
-- 
- Jiaxun

  reply	other threads:[~2024-09-10 20:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 10:08 [PATCH v2 0/6] MIPS: cm: Probe GCR address from devicetree Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 1/6] MIPS: generic: Do __dt_setup_arch in prom_init Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 2/6] MIPS: malta: Move SMP initialisation to device_tree_init Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 3/6] MIPS: cm: Prefix probe functions with __init Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 4/6] MIPS: Move mips_cm_probe after prom_init Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 5/6] dt-bindings: mips: Document mti,mips-cm Jiaxun Yang
2024-06-12 17:01   ` Conor Dooley
2024-08-06 19:56   ` Serge Semin
2024-06-12 10:08 ` [PATCH v2 6/6] MIPS: cm: Probe GCR address from DeviceTree Jiaxun Yang
2024-09-10 12:36   ` Serge Semin
2024-09-10 19:23     ` Jiaxun Yang
2024-09-10 20:07       ` Serge Semin
2024-09-10 20:48         ` Jiaxun Yang [this message]
2024-09-10 22:16           ` Serge Semin
2024-07-06  5:13 ` [PATCH v2 0/6] MIPS: cm: Probe GCR address from devicetree Jiaxun Yang
2024-07-20  7:30 ` Jiaxun Yang
2024-08-06 19:49 ` Serge Semin
2024-09-09 13:32   ` Thomas Bogendoerfer
2024-09-10  8:06     ` Serge Semin
2024-09-10 12:20       ` Serge Semin

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=b4d57581-bad7-4f6f-8d6f-733f1a5d33ba@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paulburton@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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