Received: by 2002:a05:7412:8d11:b0:fa:4934:9f with SMTP id bj17csp432687rdb; Mon, 15 Jan 2024 01:53:24 -0800 (PST) X-Google-Smtp-Source: AGHT+IHP/0dx80fpyHzZAInsHu7EXm4NRTYtSu0pkxhxOYONQ9pY2ylFj33KIn5TCLb8wCFEBKXw X-Received: by 2002:a05:6214:1d2c:b0:67a:d79b:67e7 with SMTP id f12-20020a0562141d2c00b0067ad79b67e7mr7270973qvd.29.1705312403857; Mon, 15 Jan 2024 01:53:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1705312403; cv=none; d=google.com; s=arc-20160816; b=i3HIC3EAVlKnshcXaXImRSr1pVVBPkIcsuQXWkgEdnmdYYOFk8w8DlRusQaCipoVMN KwBUHWzVdt3AHBh6Xv2SV2DAFT/k+vRCMcw9IU69WziXgDSdOiDdEiPv7An7hvAyuZLo +3A1x57x+BXNIPUztJs3muTrEBy8e0pvOASjTW6kEjJqDZagf2CnDahKXFucMUfrq44E shFzzb3rsHtf0s5OesFRFCk6nkg18FbXfqxFjDH7bjiTSN0WSvmVEgZCMuf3LVGyOMj1 4YfMt7nbWIqPW5g53aLnkQvYu29DIVybwmVGL3RsM6EangLdZcXFLPps/1kJNbiG+ZFA 2w/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:list-unsubscribe:list-subscribe :list-id:precedence; bh=ZFDl0jZMXdZ3unkGx5DmmCJ/FhVag42jO4CLQhckQUc=; fh=QWCsUX5ERRpw4wfLAN2fORqk94harjIIZQNTkLgx7yg=; b=muAU8kQQDxWH6BWTU5FgKgya3Pd4PkTUKzE1zpXYyXX4CS4VtuOYSURVIv+tCAvUOi Wa+wLy/GxfUESxPC4QJ65J9Obw+XMBalxFlCUgKMMyDtDZyMLnnTuE7lgY0Os0WM5i9p QWDpxnZfIThOA7nZCs0wqPg28SIItUnH8foZI7bMPaWz80naxUXB8IiX+HNDu40/qfmr NZtIUmu7B3aL+96wCbuoxoR/BkGvVNWg1bV3ITG5gjZ9lX77/iOwadcL7+MApRIeQzZZ qvRdLJTbFelf8HrVXvAIyqxgamNLlZ17mAoZLC1NFEiNl7rAzh3blJSyNYz1KUdRh+HH TtWQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel+bounces-25826-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-25826-linux.lists.archive=gmail.com@vger.kernel.org" Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id t4-20020a0c8d84000000b0067f32b8e421si7690074qvb.417.2024.01.15.01.53.23 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 15 Jan 2024 01:53:23 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-25826-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel+bounces-25826-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-25826-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 8D87B1C21618 for ; Mon, 15 Jan 2024 09:53:23 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 9A18E11CA0; Mon, 15 Jan 2024 09:52:51 +0000 (UTC) Received: from mail-yw1-f175.google.com (mail-yw1-f175.google.com [209.85.128.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 54944FC11; Mon, 15 Jan 2024 09:52:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-yw1-f175.google.com with SMTP id 00721157ae682-5e76948cda7so77666167b3.3; Mon, 15 Jan 2024 01:52:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705312368; x=1705917168; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=wsMhOFSC0mxjAJYvrikbFmAm65pBG0U6QI3j9yJqaic=; b=NqW2mCDtcUyTwgZFAA/rkTMwmahWtBYNzWc32YZPKxNlkm0yMW0+8HOjveMxShuxBy CQcHx+Msh/CWIuQxKxaPkIPXMN/G+5Z2e8g8ISXK/Yjc4+w8vNr3nUS9fgey+uTk+fK2 oZzyLlN2CaMWRWehm60qBBYaXqBTu1GEtBVOQH0QeL96x1EN+koc3aPHVxdo6atY5h3R LRf/i8kG84+bhDXyaHj+Lu81cV0ZSKJV8bSKDsaOSjH7n/TWEOtQPeuM8nTNKWhFKvGX Zo7uJl/lwyrGDQzCIk5PIReijBY10X23ny24PH0mO2I69pGmfNF7H7iMjU1mI4muKq8b i7qA== X-Gm-Message-State: AOJu0YyjDcFNHqPCE7Bn5PhldVqqWrg8jbyb6Z/+i9fnqy8Rf+XHhjUe lVw2vQYIGyA0BD9THlzr3wSSNvnngfGL5A== X-Received: by 2002:a81:7613:0:b0:5f7:b18e:9298 with SMTP id r19-20020a817613000000b005f7b18e9298mr3674121ywc.67.1705312368108; Mon, 15 Jan 2024 01:52:48 -0800 (PST) Received: from mail-yw1-f169.google.com (mail-yw1-f169.google.com. [209.85.128.169]) by smtp.gmail.com with ESMTPSA id l6-20020a0de206000000b005ff3b4a89a8sm271889ywe.107.2024.01.15.01.52.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 15 Jan 2024 01:52:47 -0800 (PST) Received: by mail-yw1-f169.google.com with SMTP id 00721157ae682-5e76948cda7so77665967b3.3; Mon, 15 Jan 2024 01:52:47 -0800 (PST) X-Received: by 2002:a81:6d41:0:b0:5f6:46b:b0be with SMTP id i62-20020a816d41000000b005f6046bb0bemr2963784ywc.61.1705312367679; Mon, 15 Jan 2024 01:52:47 -0800 (PST) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <9c3a9caaa1e2fc7e515cac67f07a20af071bd1be.1704788539.git.ysato@users.sourceforge.jp> In-Reply-To: <9c3a9caaa1e2fc7e515cac67f07a20af071bd1be.1704788539.git.ysato@users.sourceforge.jp> From: Geert Uytterhoeven Date: Mon, 15 Jan 2024 10:52:36 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DO NOT MERGE v6 22/37] dt-bindings: display: smi,sm501: SMI SM501 binding json-schema To: Yoshinori Sato Cc: linux-sh@vger.kernel.org, Damien Le Moal , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Michael Turquette , Stephen Boyd , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Daniel Vetter , Thomas Gleixner , Lorenzo Pieralisi , =?UTF-8?Q?Krzysztof_Wilczy=C5=84ski?= , Bjorn Helgaas , Greg Kroah-Hartman , Jiri Slaby , Magnus Damm , Daniel Lezcano , Rich Felker , John Paul Adrian Glaubitz , Lee Jones , Helge Deller , Heiko Stuebner , Jernej Skrabec , Chris Morgan , Yang Xiwen , Sebastian Reichel , Linus Walleij , Randy Dunlap , Arnd Bergmann , Vlastimil Babka , Hyeonggon Yoo <42.hyeyoo@gmail.com>, David Rientjes , Baoquan He , Andrew Morton , Guenter Roeck , Stephen Rothwell , Azeem Shaikh , Javier Martinez Canillas , Max Filippov , Palmer Dabbelt , Bin Meng , Jonathan Corbet , Jacky Huang , Lukas Bulwahn , Biju Das , =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , Sam Ravnborg , Sergey Shtylyov , Michael Karcher , Laurent Pinchart , linux-ide@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-pci@vger.kernel.org, linux-serial@vger.kernel.org, linux-fbdev@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Sato-san, On Tue, Jan 9, 2024 at 9:24=E2=80=AFAM Yoshinori Sato wrote: > Signed-off-by: Yoshinori Sato Thanks for your patch! > --- > .../bindings/display/smi,sm501.yaml | 417 ++++++++++++++++++ > 1 file changed, 417 insertions(+) > create mode 100644 Documentation/devicetree/bindings/display/smi,sm501.y= aml Surely Documentation/devicetree/bindings/display/sm501fb.txt should be removed, too? > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/smi,sm501.yaml > + crt: > + type: object > + description: CRT output control > + properties: > + edid: > + $ref: /schemas/types.yaml#/definitions/uint8-array > + description: | > + verbatim EDID data block describing attached display. > + Data from the detailed timing descriptor will be used to > + program the display controller. > + > + smi,flags: > + $ref: /schemas/types.yaml#/definitions/string-array > + description: Display control flags. > + items: > + anyOf: > + - const: use-init-done > + - const: disable-at-exit > + - const: use-hwcursor > + - const: use-hwaccel The "use-*" flags look like software policy, not hardware description, and thus do not belong in DT? > + - const: panel-no-fpen > + - const: panel-no-vbiasen > + - const: panel-inv-fpen > + - const: panel-inv-vbiasen > + maxItems: 8 > + > + bpp: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: Color depth > + > + panel: > + type: object > + description: Panel output control > + properties: > + edid: > + $ref: /schemas/types.yaml#/definitions/uint8-array > + description: | > + verbatim EDID data block describing attached display. > + Data from the detailed timing descriptor will be used to > + program the display controller. > + > + smi,flags: > + $ref: /schemas/types.yaml#/definitions/string-array > + description: Display control flags. > + items: > + anyOf: > + - const: use-init-done > + - const: disable-at-exit > + - const: use-hwcursor > + - const: use-hwaccel The "use-*" flags look like software policy, not hardware description, and thus do not belong in DT? > + - const: panel-no-fpen > + - const: panel-no-vbiasen > + - const: panel-inv-fpen > + - const: panel-inv-vbiasen > + maxItems: 8 > + > + bpp: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: Color depth > + > + smi,devices: > + $ref: /schemas/types.yaml#/definitions/string-array > + description: Select SM501 device functions. > + items: > + anyOf: > + - const: usb-host > + - const: usb-slave > + - const: ssp0 > + - const: ssp1 > + - const: uart0 > + - const: uart1 > + - const: fbaccel > + - const: ac97 > + - const: i2s > + - const: gpio > + minItems: 1 > + maxItems: 10 I think it would be better to have individual subnodes for the sub devices, with status =3D "ok"/"disabled". If you go that route, you do need some fallback code to handle the lack of subnodes in the existing user in arch/powerpc/boot/dts/charon.dts. BTW, why can sm501_pci_initdata get away with setting ".devices =3D SM501_USE_ALL"? Or, would it hurt to enable all subdevices unconditionally? > + > + smi,mclk: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: mclk frequency. > + > + smi,m1xclk: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: m1xclk frequency. These two should be clock specifiers (i.e. phandles pointing to clock nodes + optional clock indices). > + > + misc-timing: > + type: object > + description: Miscellaneous Timing register values. > + properties: > + ex: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: Extend bus holding time. > + enum: [0, 16, 32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, = 208, 224, 240] > + > + xc: > + $ref: /schemas/types.yaml#/definitions/string > + description: Xscale clock input select. > + items: > + enum: > + - internal-pll > + - hclk > + - gpio33 Software policy instead of hardware description again? I am not familiar with how the SM501 works, so I cannot comment on the other properties, but several of them look like they need rework. Gr{oetje,eeting}s, Geert --=20 Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k= org In personal conversations with technical people, I call myself a hacker. Bu= t when I'm talking to journalists I just say "programmer" or something like t= hat. -- Linus Torvalds