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 DFCFFC433EF for ; Mon, 14 Mar 2022 10:43:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238651AbiCNKos (ORCPT ); Mon, 14 Mar 2022 06:44:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34284 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236179AbiCNKos (ORCPT ); Mon, 14 Mar 2022 06:44:48 -0400 Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B6DE0BC21 for ; Mon, 14 Mar 2022 03:43:38 -0700 (PDT) Received: by mail-pf1-x429.google.com with SMTP id s11so13919845pfu.13 for ; Mon, 14 Mar 2022 03:43:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=offBx8u5K9bH2yAbo6I5jJGdKaFPcNiQgtHBU/dwurU=; b=abaAC5ZVOSjYCB5GTI4jMzp/Cl/Q0BjriRREyaCyTUp1j4rom2RG1SEY7jugYfJ/EP mvas1maqJCucHjUM5DzwP+zSwpR3D4nPAmt6MI+ongS9Uh2fwmFYeEib3Z4Uy5TDXJSN pnMCu0WnVdNHr7LiEitsfmFUQPWzF1zEZydrUO3xrNkqdWZN/Tb1+QxhXQhxPq2+M+/Z rjQuEQW/radAtdYCXe/lJK/4QP7vj0eRCvSoDLhsbhq+eDmiof0juJ/bgL83/u2sKr+p Qcpi2fniHGCfwftvFpPh7F+wtPYXkjo1ZIBpObCCanSpmaEhCiQn6QNHaXLlKazRCJ1t a1aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=offBx8u5K9bH2yAbo6I5jJGdKaFPcNiQgtHBU/dwurU=; b=I/s384OyfO89yjHH0JlLXl0FJw6ig7D+bhts3EBTLe49Bsvg3dt9azgdJ7NzQQ2Nsc DyAiRKIzQmUmfDQrfBGyuKlvcoerLrijNp7Nsyx2injrvqd1d4fqAwzwiBFlfMgbU7zy uLw7nvn3NBX3JQdJK+5AIpVkfOnlNhXgzpe7Jk/Jqv8Wz1380NSM1fLDFFjTR/tpbjsf BMoSbolYR4JDsFMOnTBhm32wvqCVBZhvyUv6cmZTd8pGkpx8OgrQLuf6j36jiqVLiuiY seMMXF26w5xyoqjx7Ys1TxTRUbgbBM3weRDBpStrzEXuXxh5bpxQ4qGJ1t3aWX5CHitD RlBg== X-Gm-Message-State: AOAM532yY1RgByLSw+dNMCdPDU5hpQ322UxgBbCYKOUDS5ugA9TtbZLo OawZ7LwBlwgaCehLk3nQsWj6qtq6eaI0nQ== X-Google-Smtp-Source: ABdhPJzPuCIBqKGT2yR3Mt9Jycz4pRUYKogWOk7q1ldx2/KnEQ0XxCwD/43nSZpnKOQc0BoR4ieMdg== X-Received: by 2002:a63:914a:0:b0:380:1b9a:5bee with SMTP id l71-20020a63914a000000b003801b9a5beemr19047917pge.39.1647254618131; Mon, 14 Mar 2022 03:43:38 -0700 (PDT) Received: from localhost ([223.184.83.228]) by smtp.gmail.com with ESMTPSA id y5-20020a056a00190500b004f104b5350fsm20537440pfi.93.2022.03.14.03.43.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 14 Mar 2022 03:43:37 -0700 (PDT) Date: Mon, 14 Mar 2022 16:13:36 +0530 From: Viresh Kumar To: Arnd Bergmann Cc: Kuldeep Singh , SoC Team , Viresh Kumar , Shiraz Hashim , Rob Herring , Linux ARM , DTML , Linux Kernel Mailing List Subject: Re: [PATCH 1/2] ARM: dts: spear13xx: Update SPI dma properties Message-ID: <20220314104336.ojkkynvqldrnw2kb@vireshk-i7> References: <20220312180615.68929-1-singh.kuldeep87k@gmail.com> <20220312180615.68929-2-singh.kuldeep87k@gmail.com> <20220314035118.gbjbrwbsywxljjti@vireshk-i7> <20220314065434.GA43329@9a2d8922b8f1> <20220314073102.l6vokyookzyo76hj@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716-391-311a52 Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 14-03-22, 11:27, Arnd Bergmann wrote: > I don't think that it was meant to have a fixed order: unlike the other > bindings that define xxx-names properties, dmas require giving > names to allow the DT to specify more than one possible DMA > specifier for a given name. This means that nothing may ever just > rely on an index but has to use the name for lookup. Is there a way to update the yaml or tooling in that case so it doesn't expect a fixed order ? > OTOH, while fixing the order in the binding does not add any > value, it's also harmless as this should never be able to break > anything that worked for any combination of old/new dtb and > kernel, and it's probably easier to express in the binding. I agree, but such a patch shouldn't be required at all, which caught my attention. It is fine to merge it and won't break anything, but it shouldn't be required as well. -- viresh