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 B02B337B41C; Tue, 7 Apr 2026 21:11:33 +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=1775596295; cv=none; b=gioMF/cXziY3oQZQFR4ssG1FInDzEOPLM0CkKTlQtKrOZHF4Ca/UCsUPMXAd/0bU/1LU59sP6UFKafH+Ue9Ss1KsDw6Mrhtj/z/ue9BGnA8e5hLrPfYgcoIcvL4B6HSfhGHqI2iFkAnm1mhRkOTMsrp80bbuK7d/kMjuzk5XPto= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775596295; c=relaxed/simple; bh=8VbxCLeD3LHO9WeuL0mxVX2ozN/abN6OBGaPDwhqkk4=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=o3DZRFhl/GPpF2hZS6yZcuYdHNW7lUiNuUPawTtxQOLvm02T9Hki2b0Zesm4IuoO+GZWvFbi2I2Ofgy2wQocbmF9qm3WrHrC0YsNvRAwjnluiUIHuY/sbZqr6GLPdCLeZSwl9PmMou0AZEteDihK8Q6ji/DDG5jLSiE6IAXoecU= 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=DFdMrKAZ; 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="DFdMrKAZ" Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 6FB5B113345; Tue, 7 Apr 2026 23:11:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nabladev.com; s=dkim; t=1775596292; h=from:subject:date:message-id:to:cc:mime-version: content-transfer-encoding:in-reply-to:references; bh=QkvH1wZDq7H+oXywOmHewKF4USwKI4zFmcukh1lvkuE=; b=DFdMrKAZjp44l3ribfu9Nsx8OJIy/e4ZyxbmPLCUImfO1VO5KrSussgtFoAcS1/QBHfMqn b12a0R7o0h+0wclzJ6RufidGU9QW7w+mRX6UkHG84JDBWUYDcqGeFyVepOArs0kCDjuAsY txN6F0wezPEHziXusEdhld4wtg0tGIIAB90knBXmdVjLv9DbSEQ7dS1m3VfEyv6lDW+EGH vLA9+2uIqPfosyvqxIG9H6jve4EWJydnEYi42zPgbFRZhp+3Lc3LyjjXjllR6PgPgsQown orsUpumB1qS6+wtc3rURo7Rv4P5oWeHJoamsY1jRaUuFtTEVWxlyk5P6lrShJA== From: Marek Vasut To: linux-clk@vger.kernel.org Cc: Marek Vasut , Conor Dooley , Brian Masney , Conor Dooley , Krzysztof Kozlowski , Michael Turquette , Michael Walle , Rob Herring , Stephen Boyd , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v5 4/6] dt-bindings: clock: fsl-sai: Document clock-cells = <1> support Date: Tue, 7 Apr 2026 23:10:01 +0200 Message-ID: <20260407211123.77602-4-marex@nabladev.com> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260407211123.77602-1-marex@nabladev.com> References: <20260407211123.77602-1-marex@nabladev.com> 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 driver now supports generation of both BCLK and MCLK, document support for #clock-cells = <0> for legacy case and #clock-cells = <1> for the new case which can differentiate between BCLK and MCLK. Acked-by: Conor Dooley Signed-off-by: Marek Vasut --- Cc: Brian Masney 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: Update commit message, align it with the bindings one 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-3-marex@denx.de/ V4: No change V5: No change --- Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml b/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml index 90799b3b505ee..041a63fa2d2b0 100644 --- a/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml +++ b/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml @@ -10,7 +10,7 @@ maintainers: - Michael Walle description: | - It is possible to use the BCLK pin of a SAI module as a generic + It is possible to use the BCLK or MCLK 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, @@ -47,7 +47,7 @@ properties: - const: mclk1 '#clock-cells': - const: 0 + maximum: 1 allOf: - if: -- 2.53.0