From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx.nabladev.com (mx.nabladev.com [178.251.229.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DA0B123E32B; Sat, 4 Apr 2026 18:34:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=178.251.229.89 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775327670; cv=none; b=d8O4pY5hRWqDlhQKb95PqH7K4muV0WyNWpSg+FtEk40MLZidIiSbzcUBtRne1QtSPI2sd1zMkANASroeZbGBIITT06fJ+jCD81m5gEdtRtWQuw3MC6VUeWb882s39AhupOoPycU6je+EiNfnSlX+DQDFWtxvJZQw9ssZOmWiZOo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775327670; c=relaxed/simple; bh=LzJtZSeXf+mawXGTWwa6HLf/TPvBarcperc8O5Ea0Wc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=cI0wep0DEmtHXvDUufCnQd+3F90c4GSzv2cMdrN+euexKGXeEafPIqbxk6deRhdhb3sh3I3OZ2kdgRI5pNXaft/td+ZQ3QraavsPBnpXR5zSCNrwRroIH9MmtKXkXhDqGduILqukQrome3P5dyRvqrQVj1udV/tPxOvvIshP8Eo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=nabladev.com; spf=pass smtp.mailfrom=nabladev.com; dkim=pass (2048-bit key) header.d=nabladev.com header.i=@nabladev.com header.b=CwOHPYAj; arc=none smtp.client-ip=178.251.229.89 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=nabladev.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=nabladev.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=nabladev.com header.i=@nabladev.com header.b="CwOHPYAj" Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 94FFC10D7E3; Sat, 4 Apr 2026 20:34:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nabladev.com; s=dkim; t=1775327665; h=from:subject:date:message-id:to:cc:mime-version: content-transfer-encoding; bh=vGPmMABLDqvJQgCeAHldcVZWSY8iAM2GtD5Yz7P55xo=; b=CwOHPYAjBwe3wHsngMLn2jLeg6iWH3JH0tr+Ezvbrx982/p9tKQRCCm/1WzVdudojgJVhD ifA1xf9Z71z21fqxXhikJZ/juNkGIt2g+oLP4yg8grUSTii2kO8PM4II2MooYxOqhlD6o6 wHbFItrG8vl+bqOpJ8HP8cZRp98SBNNT+yRklvede0exb0VIRFGl40jQbDxur+dfJCTYch XcLIxODG820NUfyJslL2nW6lWd3IQ5mB5lb+B0ijY41BeAcQJ254IJ/ZIByIevwJT86HoP Pn1H/G5p5j11mkjN2SzZQsRgR3a2NluMu43KdyPgQsLeev+lJMNGXR2TtXOu/Q== From: Marek Vasut To: linux-clk@vger.kernel.org Cc: Marek Vasut , Conor Dooley , Conor Dooley , Krzysztof Kozlowski , Michael Turquette , Michael Walle , Rob Herring , Stephen Boyd , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v3 1/4] dt-bindings: clock: fsl-sai: Document i.MX8M support Date: Sat, 4 Apr 2026 20:33:25 +0200 Message-ID: <20260404183419.46455-1-marex@nabladev.com> X-Mailer: git-send-email 2.53.0 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Last-TLS-Session-Version: TLSv1.3 The i.MX8M/Mini/Nano/Plus variant of the SAI IP has control registers shifted by +8 bytes and requires additional bus clock. Document support for the i.MX8M variant of the IP with this register shift and additional clock. Update the description slightly. Acked-by: Conor Dooley Signed-off-by: Marek Vasut --- Cc: Conor Dooley Cc: Krzysztof Kozlowski Cc: Michael Turquette Cc: Michael Walle Cc: Rob Herring Cc: Stephen Boyd Cc: devicetree@vger.kernel.org Cc: linux-clk@vger.kernel.org Cc: linux-kernel@vger.kernel.org --- V2: No change V3: - Rebase on current next, update mail address - Pick ancient AB from Conor, although this may be outdated https://patchwork.kernel.org/project/alsa-devel/patch/20241226162234.40141-1-marex@denx.de/ - Invert the allOf conditional to match on VF610 and limit the clocks/clock-names there. MX8M can have one or two input clock, "bus" is mandatory and "mclk1" is optional. The "mclk1" are used by the driver in 4/4 . --- .../bindings/clock/fsl,sai-clock.yaml | 41 ++++++++++++++++--- 1 file changed, 35 insertions(+), 6 deletions(-) diff --git a/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml b/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml index 3bca9d11c148f..90799b3b505ee 100644 --- a/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml +++ b/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml @@ -10,10 +10,10 @@ maintainers: - Michael Walle description: | - It is possible to use the BCLK pin of a SAI module as a generic clock - output. Some SoC are very constrained in their pin multiplexer - configuration. Eg. pins can only be changed groups. For example, on the - LS1028A SoC you can only enable SAIs in pairs. If you use only one SAI, + It is possible to use the BCLK pin of a SAI module as a generic + clock output. Some SoC are very constrained in their pin multiplexer + configuration. E.g. pins can only be changed in groups. For example, on + the LS1028A SoC you can only enable SAIs in pairs. If you use only one SAI, the second pins are wasted. Using this binding it is possible to use the clock of the second SAI as a MCLK clock for an audio codec, for example. @@ -21,17 +21,46 @@ description: | properties: compatible: - const: fsl,vf610-sai-clock + oneOf: + - items: + - enum: + - fsl,imx8mm-sai-clock + - fsl,imx8mn-sai-clock + - fsl,imx8mp-sai-clock + - const: fsl,imx8mq-sai-clock + - items: + - enum: + - fsl,imx8mq-sai-clock + - fsl,vf610-sai-clock reg: maxItems: 1 clocks: - maxItems: 1 + minItems: 1 + maxItems: 2 + + clock-names: + minItems: 1 + items: + - const: bus + - const: mclk1 '#clock-cells': const: 0 +allOf: + - if: + properties: + compatible: + contains: + const: fsl,vf610-sai-clock + then: + properties: + clocks: + maxItems: 1 + clock-names: false + required: - compatible - reg -- 2.53.0