public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Gary Yang <gary.yang@cixtech.com>
To: linus.walleij@linaro.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	cix-kernel-upstream@cixtech.com,
	Gary Yang <gary.yang@cixtech.com>
Subject: [v2 0/3] Add pinctrl support for sky1
Date: Fri, 12 Sep 2025 14:06:47 +0800	[thread overview]
Message-ID: <20250912060650.2180691-1-gary.yang@cixtech.com> (raw)

Patch 1: add Cix pinctrl driver to support pinmux and pinconfigs
Patch 2: add Cix pinctrl nodes and header file
Patch 3: add yaml doc

Changes for v2:
- restructure the pinctrl driver to support pinmux=<..>
- redefine pinmux macros
- move header file from dt-bindings to dts
- fix the code-style issues



Gary Yang (3):
  pinctrl: cix: Add pin-controller support for sky1
  dt-bindings: pinctrl: Add cix,sky1-pinctrl
  arm64: dts: cix: Add pinctrl nodes for sky1

 .../bindings/pinctrl/cix,sky1-pinctrl.yaml    |   85 +
 arch/arm64/boot/dts/cix/sky1-orion-o6.dts     |   32 +
 arch/arm64/boot/dts/cix/sky1-pinfunc.h        |  417 +++++
 arch/arm64/boot/dts/cix/sky1.dtsi             |   10 +
 drivers/pinctrl/Kconfig                       |    1 +
 drivers/pinctrl/Makefile                      |    1 +
 drivers/pinctrl/cix/Kconfig                   |   14 +
 drivers/pinctrl/cix/Makefile                  |    4 +
 drivers/pinctrl/cix/pinctrl-sky1-base.c       |  581 +++++++
 drivers/pinctrl/cix/pinctrl-sky1.c            | 1435 +++++++++++++++++
 drivers/pinctrl/cix/pinctrl-sky1.h            |   46 +
 11 files changed, 2626 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/pinctrl/cix,sky1-pinctrl.yaml
 create mode 100644 arch/arm64/boot/dts/cix/sky1-pinfunc.h
 create mode 100644 drivers/pinctrl/cix/Kconfig
 create mode 100644 drivers/pinctrl/cix/Makefile
 create mode 100644 drivers/pinctrl/cix/pinctrl-sky1-base.c
 create mode 100644 drivers/pinctrl/cix/pinctrl-sky1.c
 create mode 100644 drivers/pinctrl/cix/pinctrl-sky1.h

-- 
2.49.0



             reply	other threads:[~2025-09-12  6:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12  6:06 Gary Yang [this message]
2025-09-12  6:06 ` [v2 1/3] pinctrl: cix: Add pin-controller support for sky1 Gary Yang
2025-09-12 11:59   ` Linus Walleij
     [not found]     ` <TYUPR06MB5876BB28E3C30EEB9BB05997EF15A@TYUPR06MB5876.apcprd06.prod.outlook.com>
2025-09-15  8:35       ` Linus Walleij
     [not found]         ` <PUZPR06MB5887DA8FE0E128993F11E2B3EF16A@PUZPR06MB5887.apcprd06.prod.outlook.com>
2025-09-30 12:34           ` Linus Walleij
2025-09-12  6:06 ` [v2 2/3] dt-bindings: pinctrl: Add cix,sky1-pinctrl Gary Yang
2025-09-12  7:39   ` Linus Walleij
2025-09-12 14:19   ` Rob Herring
2025-09-12 14:23   ` Rob Herring (Arm)
2025-09-12  6:06 ` [v2 3/3] arm64: dts: cix: Add pinctrl nodes for sky1 Gary Yang
2025-09-12  7:45 ` [v2 0/3] Add pinctrl support " Linus Walleij

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=20250912060650.2180691-1-gary.yang@cixtech.com \
    --to=gary.yang@cixtech.com \
    --cc=cix-kernel-upstream@cixtech.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.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