Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 11:16:15 +0100	[thread overview]
Message-ID: <20261121101615.3726892-1-isasmendi.agus@gmail.com> (raw)
In-Reply-To: <20261121092601.1543468-1-isasmendi.agus@gmail.com>

Hi Stefan,

A follow-up to my earlier mail, with the details behind it.  No mux
field on the ZX279128S controls more than one pin: each pin has its
own field, so nothing is linked together and a pinmux = <pin function>
binding works for us too.  The fields are just not in pin order, so the
driver needs a table of where each pin's field is.  This is what we
have so far.

Pin numbers are GPIO numbers; the functions come from the manual's pad
table, listed by mux value (0/1/2/3).  For 1-bit fields, 0 = function
and 1 = GPIO.  The last column says where each position comes from:
"hw" = flipped on my board and seen on the GPIO input, "code" = written
by the stock U-Boot or kernel for that pin, "inf" = inferred from the
manual and the board tables, not tested.

Mux, 0x94200000:

  reg   bits       pins       functions                         src
  0x00  2k+1:2k    GPIO0-10   e.g. GPIO2 = JTAG_TDO/SIM_VCCEN/   hw: 1-3,8,9
                   (k=0..10)  UART1_TXD/GPIO2                    code: 5
                                                                 inf: rest
  0x00  22, 23     GPIO36,37  UART0 RXD, TXD                     hw
  0x00  24..27     GPIO38-41  I2C0 SCL/SDA, I2C1 SCL/SDA         hw
  0x04  1:0        GPIO11     SSP0_FS0                           inf
  0x04  3:2        GPIO12     SSP0_FS1                           hw
  0x04  5:4        GPIO14     SSP0_FS3                           hw
  0x04  7:6        GPIO15     SSP0_RXD                           code
  0x04  9:8        GPIO16     SSP0_TXD                           hw
  0x04  11:10..    GPIO17-21  SSP0_SCLK, PCM CLK/FS/TXD/RXD      inf
        19:18
  0x04  21:20      GPIO13     SSP0_FS2                           hw
  0x04  23:22      GPIO42     RGMII TXCLK                        inf
  0x08  2k+1:2k    GPIO22-35  NAND ADQ0-7 and control pads;      code
        (k=0..13)             1 on the control pads = SPI-NAND
  0x0c  0          GPIO53     PCIE0_nCLKREQ                      hw
  0x0c  1          GPIO54     PCIE1_RSTB                         code
  0x0c  2          GPIO55     PCIE1_nCLKREQ                      hw
  0x0c  3..6       GPIO56-59  GEPHY LED0-3                       hw
  0x0c  7..11      GPIO43-47  RGMII TXCTL, TXD0-3                inf
  0x0c  12, 13     GPIO50,51  TX/RX_PWRDOWN                      hw
  0x0c  14         GPIO52     PCIE0_RSTB                         code
  0x0c  15, 16     GPIO48,49  TX_SD, RX_LOS                      hw
  0x0c  18         GPIO60     SDMMC_DATA0                        hw
  0x0c  19, 20     GPIO61,62  MDC0, MDIO0                        code
  0x0c  21         GPIO63     STRAP_NAND_PAGE_SIZE0              hw

Unknown: 0x00 bits 31:28, 0x04 bits 27:24, 0x08 bits 31:28, 0x0c
bit 17.

0x30..0x38, one bit per pin: bit n of 0x30 is GPIO n (hw for 1, 2, 3,
8, 9, 12-14, 28, 29); in 0x34 the order is mostly GPIO 32+n but shifts
by one from bit 18.  Clearing a bit makes the pin read 0.

0x50..0xa4, 6-bit pad config, five fields per word.  Three are tested
(0x54 field 0 = GPIO6, 0x60 fields 0 and 2 = GPIO18 and GPIO21).  The
rest seem to follow the manual's pad order (JTAG at 0x50, UART0 at
0x74, I2C at 0x78, PCIe at 0x94/0x98, ...), which puts the pull-ups on
UART0_RXD, the I2C pads, the PCIe nCLKREQ pins and JTAG.  Bits 1:0 are
the pull (01 up, 10 down); bits 5:2 are unknown.

Agustin


      reply	other threads:[~2026-11-21 10:16 UTC|newest]

Thread overview: 3+ 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
2026-11-21 10:16   ` 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=20261121101615.3726892-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