From mboxrd@z Thu Jan 1 00:00:00 1970 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 5A572C19F29 for ; Wed, 27 Jul 2022 06:52:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229998AbiG0GwB (ORCPT ); Wed, 27 Jul 2022 02:52:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60350 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230268AbiG0Gvq (ORCPT ); Wed, 27 Jul 2022 02:51:46 -0400 Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 21D76F69 for ; Tue, 26 Jul 2022 23:51:15 -0700 (PDT) Received: by mail-lj1-x230.google.com with SMTP id v21so192666ljh.3 for ; Tue, 26 Jul 2022 23:51:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=aJUcWFFmWH0ACuT+DEaxkfE7LttZ2cDcW0MPuo+aX+s=; b=vtx7QZ7D3Fz/UFYvObJYc0p4k7igsEZqawJNaTCN9XLR0p2eXTc+WIMlOoklwoTvVg +QLAzNztvGzIkJqCovfYla9H+MiEhwjj9TDqG0s6Qqd0aXmLCTUdzoviFSPZPS9rq3R5 uUcqItXA0SmeaFAn1fWctXsDsM1nEVL1UdJuHBRUrFcZnrJ6gHOilwMN6guglZL5610v /vX6PUe/gnAMkcr6aZ6Hf4t2/JYgoUvY3hL240dIqbwhPvDo+M8/IyVsFJ6L3oZGzTfB dgqF8MvxA7kwGoiHvO6l4MUBuaevuECVhPUkEGtzp3iXH1d8BsdLYv3R5DRnTz8DTQYw lubg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=aJUcWFFmWH0ACuT+DEaxkfE7LttZ2cDcW0MPuo+aX+s=; b=Lryh6drxj74XYi0sFcNT3cCoKZwg+GExjAnP5xp6dQp7xIPxi+3l7gxDeGUPRxsrRA HwhNpQUejMEAJ59ww3TU9jWqrqoJC1lW8hGH1UaXIY8bQ+k5UJp9rZHFTjd4qz3d8MS/ p2GCKymdb8k8EvZsINX3iYUmWQNdUPt9rUciwcS0EuZi2XhJniTDBkcNAx1rhDHPA3fh u+VKbjcUWNjkR9t3fLxj+jCvCL42pNJWhEkB7yuZJD1BShby1rIUhPOpHvoMcej/DwNo qv9OgDi3TSTUAkHJS5keCEYtSQ4FYtNHuW42ooOnCOjtukwxF9mWVayBN1nmHyOf/xmQ ImyQ== X-Gm-Message-State: AJIora+P9LCAQwCG1/DOCtr0q1/XfsHww3QrBANPotR/83lclc/go469 903FctKv597MtqSqCIrMLRxgwNBMDVYFydLD X-Google-Smtp-Source: AGRyM1ueak/90bYUNOSpELSH8le2EAc2zF3399bwDPGwAEYllYwk9el8QSzhFMo2e77a56LQfDbCAw== X-Received: by 2002:a2e:98d5:0:b0:25e:c1b:f262 with SMTP id s21-20020a2e98d5000000b0025e0c1bf262mr3590812ljj.343.1658904673405; Tue, 26 Jul 2022 23:51:13 -0700 (PDT) Received: from [192.168.3.197] (78-26-46-173.network.trollfjord.no. [78.26.46.173]) by smtp.gmail.com with ESMTPSA id h7-20020a19ca47000000b0048aa00a03fesm808662lfj.215.2022.07.26.23.51.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jul 2022 23:51:12 -0700 (PDT) Message-ID: <8463a831-f263-31b2-6cd7-482ae9594bc1@linaro.org> Date: Wed, 27 Jul 2022 08:51:11 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Subject: Re: [PATCH v2 2/2] spi: npcm-pspi: Add NPCM845 peripheral SPI support Content-Language: en-US To: Tomer Maimon Cc: Mark Brown , Avi Fishman , Tali Perry , Joel Stanley , Patrick Venture , Nancy Yuen , Benjamin Fair , Rob Herring , Krzysztof Kozlowski , OpenBMC Maillist , linux-spi@vger.kernel.org, Linux Kernel Mailing List , devicetree References: <20220722114136.251415-1-tmaimon77@gmail.com> <20220722114136.251415-3-tmaimon77@gmail.com> <0c8688d5-b0c1-8cc1-ec27-292acbb38dfc@linaro.org> <20869b88-41f3-9e9c-347e-17c3d01baa5d@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 26/07/2022 21:32, Tomer Maimon wrote: > Hi Krzysztof, > > Thanks for your explanation. > > On Tue, 26 Jul 2022 at 12:47, Krzysztof Kozlowski > wrote: >> >> On 24/07/2022 10:44, Tomer Maimon wrote: >>> Hi Mark and Krzysztof, >>> >>> Thanks for your reply, >>> >>> On Fri, 22 Jul 2022 at 21:57, Mark Brown wrote: >>>> >>>> On Fri, Jul 22, 2022 at 08:47:24PM +0200, Krzysztof Kozlowski wrote: >>>>> On 22/07/2022 20:43, Mark Brown wrote: >>>> >>>>>> ...with a fallback list required by the bindings so the driver actually >>>>>> binds. Note that bindings are currently not in YAML format so there'd >>>>>> be even less enforcement of that than normal, and as they're currently >>>>>> written the bindings don't require fallback. >>>> >>>>> Yes, the bindings document should be rephrased but we were living like >>>>> that for few years. :) >>>> >>>> The binding document as it stands only has one compatible, there's no >>>> existing problem with it other than the YAML conversion. If we're >>>> adding something new that requires a fallback we should be explicit >>>> about that rather than have something that's actively misleading where >>>> previously things were clear. I don't mind if we add the compatible to >>>> the driver or document the requirement for the fallback but we should do >>>> one of the two. >>> >>> is V2 good enough? adding the compatible to the driver and the document? >>> Or should we use fallback? >>> If fallback is choosen, can you explain how I should do it? >> >> I propose to use fallback. The preferred way is to convert it to DT >> schema and then add new device support (so two commits). Other >> acceptable way is to rephrase the TXT so it clearly states desired >> compatibles - one for old device, two for new devices. There are plenty >> of examples in current sources. > Appreciate if you could clarify. > in case we use DT-schema, we dont describe the fallback like we doing > in txt document? > I mean that in the yaml file we should describe the NPCM PSPI > compatible property as follow: > compatible: > enum: > - nuvoton,npcm750-pspi > - nuvoton,npcm845-pspi > > If yes, how should the user know that he needs to use fallback incase > is using nuvoton,npcm845-pspi? only from the device tree? > If you use DT schema format, you must code it as with fallback (so items). This is the most popular setup for SoC components so you will easily find such examples. Best regards, Krzysztof