The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>, vjardin@free.fr
Cc: Dong Aisheng <aisheng.dong@nxp.com>,
	Fabio Estevam <festevam@gmail.com>, Frank Li <Frank.Li@nxp.com>,
	Jacky Bai <ping.bai@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP S32 Linux Team <s32@nxp.com>,
	Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
	Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: Re: [PATCH v7 3/6] soc: fsl: guts: add the RCW override of the pad muxes
Date: Tue, 17 Nov 2026 23:26:38 +0100	[thread overview]
Message-ID: <44bb9bd5-42f5-46d2-8dca-dd220aa221cb@kernel.org> (raw)
In-Reply-To: <avzCrmvlOQh0RVjT@lxl00025.wbi.nxp.com>



Le 17/11/2026 à 22:10, Vladimir Oltean a écrit :
> On Tue, Nov 17, 2026 at 03:53:13PM +0100, Vincent Jardin via B4 Relay wrote:
>> From: Vincent Jardin <vjardin@free.fr>
>>
>> fsl_guts_rcw_rmw() only serves the SerDes lane modes. Export it for
>> the pad-mux fields of the RCW, and for them only:
>>   - fsl_guts_pmux_read() reads the pad-mux fields of a status register
>>   - fsl_guts_pmux_override() changes pad-mux fields of one under
>>     rcwcr_lock and waits for the status register to follow
>>   - fsl_guts_pmux_override_supported() tells whether the SoC has pad-mux
>>     fields and whether the DCSR view of DCFG, which holds the override
>>     registers, is mapped
>>
>> Each SoC lists in its fsl_soc_data the fields that can be overridden,
>> per RCWSR: a register or a field outside of this list is refused, so
>> the SerDes protocols stay with fsl_guts_lane_set_mode(). The LX2160A
>> lists the pad muxes of RCWSR12 to RCWSR14 and of RCWSR27.
>>
>> Suggested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
>> Acked-by: Frank Li <Frank.li@nxp.com>
>> Signed-off-by: Vincent Jardin <vjardin@free.fr>
>> ---
> 
> Looks good, thanks.
> 
> Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>

Acked-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>



  reply	other threads:[~2026-11-17 22:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 14:53 [PATCH v7 0/6] lx2160a: change the pad muxes through the RCW override Vincent Jardin via B4 Relay
2026-11-17 14:53 ` [PATCH v7 1/6] dt-bindings: pinctrl: add the NXP LX2160A RCW pad mux Vincent Jardin via B4 Relay
2026-11-17 21:07   ` Vladimir Oltean
2026-11-17 14:53 ` [PATCH v7 2/6] dt-bindings: soc: fsl: layerscape-dcfg: add the LX2160A pad-mux child Vincent Jardin via B4 Relay
2026-11-17 21:07   ` Vladimir Oltean
2026-11-17 14:53 ` [PATCH v7 3/6] soc: fsl: guts: add the RCW override of the pad muxes Vincent Jardin via B4 Relay
2026-11-17 21:10   ` Vladimir Oltean
2026-11-17 22:26     ` Christophe Leroy (CS GROUP) [this message]
2026-11-17 14:53 ` [PATCH v7 4/6] pinctrl: freescale: add the Layerscape RCW pad-mux driver Vincent Jardin via B4 Relay
2026-11-17 21:25   ` Vladimir Oltean
2026-11-17 14:53 ` [PATCH v7 5/6] arm64: dts: lx2160a: describe the pad muxes as the DCFG RCW override Vincent Jardin via B4 Relay
2026-11-17 21:26   ` Vladimir Oltean
2026-11-17 14:53 ` [PATCH v7 6/6] arm64: dts: lx2160a: drop the I2C bus recovery of i2c6 and i2c7 Vincent Jardin via B4 Relay
2026-11-17 21:32   ` Vladimir Oltean

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=44bb9bd5-42f5-46d2-8dca-dd220aa221cb@kernel.org \
    --to=chleroy@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=ioana.ciornei@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ping.bai@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=s32@nxp.com \
    --cc=shawnguo@kernel.org \
    --cc=vjardin@free.fr \
    --cc=vladimir.oltean@nxp.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