Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DD8E0C61DA7 for ; Fri, 27 Jan 2023 08:33:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232571AbjA0IdG (ORCPT ); Fri, 27 Jan 2023 03:33:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41118 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232484AbjA0IdC (ORCPT ); Fri, 27 Jan 2023 03:33:02 -0500 Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7E85F19F23 for ; Fri, 27 Jan 2023 00:33:00 -0800 (PST) Received: by mail-wm1-x32e.google.com with SMTP id iv8-20020a05600c548800b003db04a0a46bso5260281wmb.0 for ; Fri, 27 Jan 2023 00:33:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=mNDzzLve1QZpQMH586QRx6794jByHtxqf4nlX323e/M=; b=wr/faRojnYtopasMYIZ7X5nKWJvOwIFDt6H3ZwcJFlrglXBSFYxDO20pRk+2obypGw lp6sclR+UR+EHorIMkUXCu8LDlgnas4SNpc653G4SjJSFR1rb/7X/I3yuiJXCETM3EDr 83A6hXp1UGKXUu8nI40pGKALkiqAnnJSwTfoe6hyBxm7uiUuR3xsh9+osuJIJb55MYPm xywXnOVLUbpg5jrSC6ADmSw5oxb91f64hNGPIz4Cicrdjt0iCGcC4T9y2P5LyHewgFxn l/6Pay8nOL53WWvAYGjjlZhjdln3wsBScLS8KjDf2HPqdzZ2rbkWVTiShk6sY4zXS+1N 4Jkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mNDzzLve1QZpQMH586QRx6794jByHtxqf4nlX323e/M=; b=S/JaA5ar0zXMnaWMn47D1VwhSsHByaYNNKWx1BOL066u040xgqLozS112eoOV1hmiY PNz76caMuPvqJoCj7pEskG7Ft9SloqC4SzCLFaG3dmejCsUuB39Q7Vq7IWUjulCITIPA U3flMLyvY0ptPHiM708WRq7TGa53P2Hcr+4RXSuoFECSjPW0/S4ThF9Ck4sJl+sWRfIy jR+956dxTwTBId2GWeWPMIQejvWNtw/NIOI1v3NaWHh8PFS+6F41cCOGcWJN40arVVuq peplqb5udebZlDO6D6kppfIRf41v2Rg6vn7Rv7/F8hcAKEGZWYAsd0fMEnuSNoRc+WsV ZZcw== X-Gm-Message-State: AO0yUKUOutOkL45ynA9+tn1BIglrVpqE69Nz7PS1FPK3W4fbeAnneDtB r+EKvZ98O0gMSZyMNCc2QiQmfQ== X-Google-Smtp-Source: AK7set8AUVYQ3DMEqB5mb5eVqgQNd79NxSGC2QpLaYfkKjZyelI9gwbfI++aOYEpI1mjO/SKh2lGNQ== X-Received: by 2002:a05:600c:1caa:b0:3dc:4042:5c30 with SMTP id k42-20020a05600c1caa00b003dc40425c30mr177420wms.10.1674808379017; Fri, 27 Jan 2023 00:32:59 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id d10-20020adffbca000000b00287da7ee033sm3318241wrs.46.2023.01.27.00.32.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 27 Jan 2023 00:32:58 -0800 (PST) Message-ID: <348c3416-be44-b912-98ef-7f394bd408c0@linaro.org> Date: Fri, 27 Jan 2023 09:32:52 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [RFC PATCH v2 02/31] Documentation: Add binding for kalray,kv3-1-core-intc Content-Language: en-US To: Jules Maselbas Cc: Yann Sionneau , Arnd Bergmann , Jonathan Corbet , Thomas Gleixner , Marc Zyngier , Rob Herring , Krzysztof Kozlowski , Will Deacon , Peter Zijlstra , Boqun Feng , Mark Rutland , Eric Biederman , Kees Cook , Oleg Nesterov , Ingo Molnar , Waiman Long , "Aneesh Kumar K.V" , Andrew Morton , Nick Piggin , Paul Moore , Eric Paris , Christian Brauner , Paul Walmsley , Palmer Dabbelt , Albert Ou , Guillaume Thouvenin , Clement Leger , Vincent Chardon , =?UTF-8?Q?Marc_Poulhi=c3=a8s?= , Julian Vetter , Samuel Jones , Ashley Lesdalons , Thomas Costis , Marius Gligor , Jonathan Borne , Julien Villette , Luc Michel , Louis Morhet , Julien Hascoet , Jean-Christophe Pince , Guillaume Missonnier , Alex Michon , Huacai Chen , WANG Xuerui , Shaokun Zhang , John Garry , Guangbin Huang , Bharat Bhushan , Bibo Mao , Atish Patra , "Jason A. Donenfeld" , Qi Liu , Jiaxun Yang , Catalin Marinas , Mark Brown , Janosch Frank , Alexey Dobriyan , Benjamin Mugnier , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-audit@redhat.com, linux-riscv@lists.infradead.org, bpf@vger.kernel.org References: <20230120141002.2442-1-ysionneau@kalray.eu> <20230120141002.2442-3-ysionneau@kalray.eu> <20230126161032.GH5952@tellis.lin.mbt.kalray.eu> From: Krzysztof Kozlowski In-Reply-To: <20230126161032.GH5952@tellis.lin.mbt.kalray.eu> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26/01/2023 17:10, Jules Maselbas wrote: >>> + reg: >>> + maxItems: 0 >> >> ??? No way... What's this? > This (per CPU) interrupt controller is not memory mapped at all, it is > controlled and configured through system registers. > > I do not have found existing .yaml bindings for such devices, only the > file snps,archs-intc.txt has something similar. > > I do not know what is the best way to represent such devices in the > device-tree. Any suggestions are welcome. You cannot have an array property with 0 items. How would it look like in DTS? There are many, many bindings which are expressing it. Just drop the reg. > >> >>> + "kalray,intc-nr-irqs": >> >> Drop quotes. >> >>> + description: Number of irqs handled by the controller. >> >> Why this is variable per board? Why do you need it ? > This property is not even used in our device-tree, this will be removed > from the documentation and from the driver as well. > >>> + >>> +required: >>> + - compatible >>> + - "#interrupt-cells" >>> + - interrupt-controller >> >> missing additionalProperties: false >> >> This binding looks poor, like you started from something odd. Please >> don't. Take the newest reviewed binding or better example-schema and use >> it to build yours. This would solve several trivial mistakes and style >> issues. > I am starting over from the example-schema. > >>> + >>> +examples: >>> + - | >>> + intc: interrupt-controller { >> >> What's the IO address space? > As said above, this is not a memory mapped device, but is accessed > through system registers. Sure, but then you cannot define a reg which was confusing... Best regards, Krzysztof