From patchwork Thu Apr 17 11:16:31 2025 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Wolfram Sang X-Patchwork-Id: 882778 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (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 6E025236A98 for ; Thu, 17 Apr 2025 11:16:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1744888611; cv=none; b=Ue0w2Q5Pd8eTxDbOUWsHoO20eF5XrPC6mBcLTvdOoTk6L5UM+Q752OCb8ll8cug0VoD78NVECXI9//q2geS8VABRgTFt0WPrNQjb5X6LHkYjgPLz09RcLekNYQTVhc8BlFqJITWjnNBJDSclxHETxEP5mg++rnAts0hf1C/HLc4= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1744888611; c=relaxed/simple; bh=EMpv3jolt945KdxEwM+fpv4lTRMv1TR/RhfjSpJhFiQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=A0+Unx2452/PR3Il/SNFlFZDunxAD2y88eqGK068NOyZn2tbPWrGpBPi1UrKLJWBQ7D/9Tg3mBkGt0ZdtK2Albo0IcF7wMv7l2+caej0o3Kz4dHZkpMVnoMtkGS/YC4O6V9ODITtjiAIKe8QPt4EFfiW6wxqFvt+7jB81iGFdRc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=c5REP31x; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="c5REP31x" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=from:to:cc:subject:date:message-id :mime-version:content-transfer-encoding; s=k1; bh=gRDp2fEIK8ZrD/ Qsr9hnUov7ClwJjL4bpJhLFXq0ZH8=; b=c5REP31xe4AIzkoh5NJ5nbCX4NaRvv pj/VTMIf3oMsFrJN2ee9wUZVVKqOop2X7bdrog1XlfHDUzyCJ9BGIADIkXkYRCiF C9wpEZ+7D0S+hMukwiDsZp3BszwLPBlf1N63sTsNDXxyiuqp1G9r1wUJwb3VN7rP yr6fvc29HhrdNPeFgeaRdptkgSh0mMkbjL6xzpXYEBUMcMiaoyGr5619Cex4Rdwc 3yLBzJVpMoBh02h9ABHGHu8cvQTQiMA5zH4sLqZsuW9b/LvkdJWzX6oC0emoHbJ2 gG1IS2Vh3M2ey88sNquE61tW5ZuQG+qZzkIJDjStMxdwPqanZP+yD8jQ== Received: (qmail 1071622 invoked from network); 17 Apr 2025 13:16:42 +0200 Received: by mail.zeus03.de with UTF8SMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 17 Apr 2025 13:16:42 +0200 X-UD-Smtp-Session: l3s3148p1@EcVIifcy5pcgAwDPXyfYALbiJ46yNPq3 From: Wolfram Sang To: linux-renesas-soc@vger.kernel.org Cc: Wolfram Sang , Mark Brown , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-spi@vger.kernel.org, devicetree@vger.kernel.org Subject: [PATCH] spi: dt-bindings: Fix description mentioning a removed property Date: Thu, 17 Apr 2025 13:16:31 +0200 Message-ID: <20250417111630.53084-2-wsa+renesas@sang-engineering.com> X-Mailer: git-send-email 2.47.2 Precedence: bulk X-Mailing-List: linux-spi@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 'spi-cpha' was removed from this file. So, replace it in the description with an existing example. Reformat the paragraph to adhere to max line length. Fixes: 233363aba72a ("spi/panel: dt-bindings: drop CPHA and CPOL from common properties") Signed-off-by: Wolfram Sang --- .../bindings/spi/spi-peripheral-props.yaml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml b/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml index 0bb443b8decd..8fc17e16efb2 100644 --- a/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml +++ b/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml @@ -8,12 +8,13 @@ title: Peripheral-specific properties for a SPI bus. description: Many SPI controllers need to add properties to peripheral devices. They could - be common properties like spi-max-frequency, spi-cpha, etc. or they could be - controller specific like delay in clock or data lines, etc. These properties - need to be defined in the peripheral node because they are per-peripheral and - there can be multiple peripherals attached to a controller. All those - properties are listed here. The controller specific properties should go in - their own separate schema that should be referenced from here. + be common properties like spi-max-frequency, spi-cs-high, etc. or they could + be controller specific like delay in clock or data lines, etc. These + properties need to be defined in the peripheral node because they are + per-peripheral and there can be multiple peripherals attached to a + controller. All those properties are listed here. The controller specific + properties should go in their own separate schema that should be referenced + from here. maintainers: - Mark Brown