From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from madrid.collaboradmins.com (madrid.collaboradmins.com [46.235.227.194]) (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 0E4971386BF; Thu, 27 Jun 2024 10:39:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=46.235.227.194 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719484781; cv=none; b=STMVE++3gl38ZlXmtoVv2lNjI8mYiyKTIFHru8bF3x+iiFtahl0ShvHrs7vsBZYqLTEsx6dkyaMB4++I0X9/uumHHX+Sq9REhIrk8qNqMZKVQQnx50BZdkTzo3naZwxipz0ltgJVl7YCli/h4PtNwXsj4xLzD7PmPw98bVsaUD8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719484781; c=relaxed/simple; bh=AkpBiq6QZeCkJ2ClHXInJEXgeTHY7jWKyNdh3XWD5TA=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=f3pCTa99R6etBm5Vc8QjmSXmaBa4rddVpvsn94z7KNIrW/GGcEvQhboYTeHfIuA4OoywayqrON32jkXeXG7k7x607HECCXYnz4rzXddyV/6r+fG8WgxLcv5zFUrMAUoSvlfeArMm+Ht79upspMQrIexTcv3ggAMpnB1bwktXDMs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=collabora.com; spf=pass smtp.mailfrom=collabora.com; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b=cX98TkMG; arc=none smtp.client-ip=46.235.227.194 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=collabora.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=collabora.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b="cX98TkMG" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1719484778; bh=AkpBiq6QZeCkJ2ClHXInJEXgeTHY7jWKyNdh3XWD5TA=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=cX98TkMGmatIeQULfWhOZfq2FjpRtak7sKXJiJSqbf9dJHSdOAnuGdZM8zQI1noMV tOGMq7ToTvFPMbbJAjPra82svkgAGTgM+/PZxJ5Svl303Ak4/LvURi8NAS5WLiEyOT YKbI9CxpBzEQx+qACcnBs1xWFln19SbOM6r9JNi8mk7oIae3Twu1GIi6SsdVyF9pd2 CNLFBADqz0un4ihuzORpLjUHC7YIP7lrjvLZlnYGy/S8HzShuQhFVbXQ5W7kvO+VvT 7sqIbTAdIcNSskvyuS7zhZtd8+aM/Ro1R07OWKyQU30o8HwZm1v+x1/bQ81As8lACU 4bJPMia6C1Cgw== Received: from [100.113.186.2] (cola.collaboradmins.com [195.201.22.229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kholk11) by madrid.collaboradmins.com (Postfix) with ESMTPSA id C3C4F3780029; Thu, 27 Jun 2024 10:39:36 +0000 (UTC) Message-ID: <3d54c64b-e1cd-4034-b0dd-e5d6607c3ef1@collabora.com> Date: Thu, 27 Jun 2024 12:39:35 +0200 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v4 6/7] dt-bindings: mfd: syscon: Split and enforce documenting MFD children To: Krzysztof Kozlowski , Orson Zhai , Baolin Wang , Chunyan Zhang , Jacky Huang , Shan-Chun Hung , Khuong Dinh , Lee Jones , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Chuanhua Lei , Rahul Tanwar , Lars Povlsen , Steen Hegelund , Daniel Machon , UNGLinuxDriver@microchip.com, Nishanth Menon , Matthias Brugger Cc: Jiaxun Yang , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Conor Dooley , Maxime Ripard References: <20240627-dt-bindings-mfd-syscon-split-v4-0-dc6699a9f3e4@linaro.org> <20240627-dt-bindings-mfd-syscon-split-v4-6-dc6699a9f3e4@linaro.org> From: AngeloGioacchino Del Regno Content-Language: en-US In-Reply-To: <20240627-dt-bindings-mfd-syscon-split-v4-6-dc6699a9f3e4@linaro.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Il 27/06/24 12:32, Krzysztof Kozlowski ha scritto: > Simple syscon nodes can be documented in common syscon.yaml, however > devices with simple-mfd compatible, thus with some children, should have > their own schema listing these children. Such listing makes the binding > specific, allows better validation (so the incorrect child would not > appear in the simple-mfd node) and actually enforces repeated rule for > simple-mfd devices: > > "simple-mfd" is only for simple devices, where the children do not > depend on the parent. > > Currently the syscon+simple-mfd binding is quite broad and allows > any child or property, thus above rule cannot be enforced. > > Split the syscon.yaml binding into: > 1. Common syscon properties, used potentially by many bindings. > 2. Simple syscon devices (NO simple-mfd!). > > Reviewed-by: Conor Dooley > Reviewed-by: Rob Herring (Arm) > Signed-off-by: Krzysztof Kozlowski Reviewed-by: AngeloGioacchino Del Regno