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 98C8EC43334 for ; Sun, 19 Jun 2022 11:46:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236795AbiFSLqX (ORCPT ); Sun, 19 Jun 2022 07:46:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35318 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229993AbiFSLqW (ORCPT ); Sun, 19 Jun 2022 07:46:22 -0400 Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5762411C0E for ; Sun, 19 Jun 2022 04:46:20 -0700 (PDT) Received: by mail-ej1-x635.google.com with SMTP id h23so16220825ejj.12 for ; Sun, 19 Jun 2022 04:46:20 -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=JIO2mY682oPXJiHyGHgrm7/Q9vi5siXInrOrzmj3AUo=; b=wdwMtYbnB3sGlyq5lBSmHcAWE2vsrrpF/vtNGPPHqz8dnsvflVypNxXbyL3sZClRLN Txh8nCv5gntNEbG067+KrIUpeT1ndJbe5pKlowuafbGQ8YLlXY5H2MXMp0XqF22hkO6p 2GBiB0fbY7KjLdEpoa1Mi3C33+E/ognIiGcRYF7SzSz0V4fu2f2rwm8RfYA8t6C7U7PQ s55KRClprD+V6LjCLA9Cv7PvmEg5CE/KC/O09D5ZzAjJikI3IDrDjdH0/K8UoNCu6DEV BML3PCmmgnVNW1qVhFr2GmWP+64xbBEeg6lrkca0P7GtaUAXNGA79+vqaYF/I5OWv55Q R80Q== 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=JIO2mY682oPXJiHyGHgrm7/Q9vi5siXInrOrzmj3AUo=; b=6KlNmXjKO1Zuh663bTlTIV+QYb2WSBM/fCRPvErQqP0xCled0NCSOUQOvsjLb6RD+2 8oH15DJzRBXqrJbkdqDEx006Luc9QFIIqpiN8iZJZpLyRywPZSgjJAH6n/YESN8RJjTs smKPrwtp9lS6OjA0QfkUk/TGLHoZDKqW+JaOgK41DnLXhNAUpjfi+BB/xeh24k8pMixi 4gsHpM4cx5qo2ZGbacvm70Q+1uNg1MNVOeHMnZqkoHRZP6Z5WwmmJOWqHU7ONYcRBgJ3 FxA5UEFDMvGSqSUdzS2+zzEGJjRweYBooGHE9GteD3lPDiFk+wm1Ba2VG7pSlWal5rke Um/A== X-Gm-Message-State: AJIora9XwXt/Qozc8tarIo8XXc6PSrro/016VXkXNL0fofjhMudXsi6z xSWbx15MrQhrTg7gomiyxA+KLw== X-Google-Smtp-Source: AGRyM1sePyl4/VzHcBtPb/raB3YCRxdOJNwaHxIh3b+epV2BiUpRnbkGH44ooVVXzFb9O5txZOn4/Q== X-Received: by 2002:a17:907:9813:b0:711:d5ac:b9ef with SMTP id ji19-20020a170907981300b00711d5acb9efmr16721384ejc.95.1655639178872; Sun, 19 Jun 2022 04:46:18 -0700 (PDT) Received: from [192.168.0.206] (xdsl-188-155-176-92.adslplus.ch. [188.155.176.92]) by smtp.gmail.com with ESMTPSA id g1-20020a17090604c100b006fec56c57e6sm4521040eja.46.2022.06.19.04.46.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 19 Jun 2022 04:46:18 -0700 (PDT) Message-ID: <8fbee49a-8215-32b7-3545-66df70ecc38d@linaro.org> Date: Sun, 19 Jun 2022 13:46:17 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH] dt-bindings: phy: make phy-cells description a text Content-Language: en-US To: Laurent Pinchart Cc: Chunfeng Yun , Kishon Vijay Abraham I , Vinod Koul , Rob Herring , Krzysztof Kozlowski , Anurag Kumar Vulisha , Michal Simek , Matthias Brugger , linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Sean Anderson References: <20220619113325.21396-1-krzysztof.kozlowski@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: linux-kernel@vger.kernel.org On 19/06/2022 13:40, Laurent Pinchart wrote: > Hi Krzysztof, > > Thank you for the patch. > > On Sun, Jun 19, 2022 at 01:33:25PM +0200, Krzysztof Kozlowski wrote: >> The description field is a string, so using YAML inside phy-cells >> description is not actually helpful. > > Does it hurt though ? For xlnx,zynqmp-psgtr.yaml I wrote it that way to > prepare for a future where it could be described using a YAML schema > (but such future may never come). No, it does not hurt. It is however confusing some folks and they think schema goes into description. The description should be readable/descriptive for humans, so if you think your approach is better, I am perfectly fine with it. Best regards, Krzysztof