From: Agustin Santiago Isasmendi <isasmendi.agus@gmail.com>
To: "Stefan Dösinger" <stefandoesinger@gmail.com>
Cc: Navid Ghahremani <ghahramani.navid@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: zx279128s pinmux questions
Date: Sat, 21 Nov 2026 10:26:01 +0100 [thread overview]
Message-ID: <20261121092601.1543468-1-isasmendi.agus@gmail.com> (raw)
In-Reply-To: <fWpK6nqqTOKOq96a3X8SYQ@gmail.com>
Hi Stefan,
On the ZX279128S the pins are individually controllable.
The chip's manual has a table of the pads (GPIO 0-63, in order) with up
to four functions each; e.g. JTAG_TDO can be JTAG_TDO, SIM_VCCEN,
UART1_TXD or GPIO2. It doesn't give the register bits, so I mapped
those from the stock U-Boot (it writes a per-board table into the
block) and by flipping bits on my H3600 and watching the GPIO inputs:
- 0x94200000 + 0x00..0x0c hold the mux, one field per pin, 2 bits
where the pad has several functions and 1 bit (function or GPIO)
where it has one. E.g. bits 2k+1:2k of +0x00 are GPIO k for
k = 0..10, and +0x08 holds the NAND/SPI-NAND pads.
- +0x30..+0x38 have one bit per pin; clearing it makes the pin read 0,
so probably an input enable.
- +0x50..+0xa4 have a 6-bit config field per pin, five per word.
Bits 1:0 are the pull (01 up, 10 down); I haven't decoded the rest.
The layout is irregular, though (GPIO 11-21 sit in +0x04, GPIO 36-41 at
the top of +0x00, and the 1-bit pads in +0x0c are out of order), so a
driver needs a table per pin with the mux and config positions, much
like the old pinctrl-zx296718. With that table, a pinmux = <pin
function> binding like yours should work for us too.
I have the per-pin table (manual functions plus the register positions
found so far, some still unverified) if it's useful to you or Navid.
Agustin
prev parent reply other threads:[~2026-11-21 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 19:24 zx279128s pinmux questions Stefan Dösinger
2026-11-21 9:26 ` Agustin Santiago Isasmendi [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=20261121092601.1543468-1-isasmendi.agus@gmail.com \
--to=isasmendi.agus@gmail.com \
--cc=ghahramani.navid@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=stefandoesinger@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