Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
MIME-Version: 1.0
References: <20220307205357.66322-1-singh.kuldeep87k@gmail.com> <20220307205357.66322-2-singh.kuldeep87k@gmail.com>
In-Reply-To: <20220307205357.66322-2-singh.kuldeep87k@gmail.com>
From:   Rob Herring <robh+dt@kernel.org>
Date:   Mon, 7 Mar 2022 19:14:09 -0600
Message-ID: <CAL_JsqKrq-NtkPF=p8Qn-_63qE80_0FSQkbY5WxCfJUcrNxJuA@mail.gmail.com>
Subject: Re: [PATCH 1/2] arm: dts: realview/versatile/ste: Update spi clock name
To:     Kuldeep Singh <singh.kuldeep87k@gmail.com>
Cc:     Linus Walleij <linus.walleij@linaro.org>,
        linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
        devicetree@vger.kernel.org,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, Mar 7, 2022 at 2:54 PM Kuldeep Singh <singh.kuldeep87k@gmail.com> wrote:
>
> SPI clock for pl022 is "sspclk" and meanwhile few platforms such as
> realview, versatile etc. specify "SSPCLK" as clock name. Even though
> bindings checks don't differentiate between the two names still keep
> same convention throughout i.e sspclk to align with other platforms.

I don't see the point in worrying about this. The binding already
allows both. Why? Because I wrote the schema and checked it against
all the in tree users. The resulting warnings are what should be fixed
in the dts files IMO. What's not warning doesn't need to be fixed.

Rob