Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20201103203232.656475008@linuxfoundation.org> <20201103203243.594174920@linuxfoundation.org>
 <20201105114648.GB9009@duo.ucw.cz>
In-Reply-To: <20201105114648.GB9009@duo.ucw.cz>
From:   Krzysztof Kozlowski <krzk@kernel.org>
Date:   Thu, 5 Nov 2020 13:38:31 +0100
Message-ID: <CAJKOXPeexYuH1_9HZUGn4Q80QBtKmqCKiEd=hNd46VKTM4kGgA@mail.gmail.com>
Subject: Re: [PATCH 4.19 107/191] ARM: dts: s5pv210: move PMU node out of
 clock controller
To:     Pavel Machek <pavel@ucw.cz>
Cc:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "stable@vger.kernel.org" <stable@vger.kernel.org>,
        Jonathan Bakker <xc-racer2@live.ca>,
        Sasha Levin <sashal@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, 5 Nov 2020 at 12:46, Pavel Machek <pavel@ucw.cz> wrote:
>
> Hi!
>
> > The Power Management Unit (PMU) is a separate device which has little
> > common with clock controller.  Moving it to one level up (from clock
> > controller child to SoC) allows to remove fake simple-bus compatible and
> > dtbs_check warnings like:
> >
> >   clock-controller@e0100000: $nodename:0:
> >     'clock-controller@e0100000' does not match '^([a-z][a-z0-9\\-]+-bus|bus|soc|axi|ahb|apb)(@[0-9a-f]+)?$'
>
> > +++ b/arch/arm/boot/dts/s5pv210.dtsi
> > @@ -98,19 +98,16 @@
> >               };
> >
> >               clocks: clock-controller@e0100000 {
> > -                     compatible = "samsung,s5pv210-clock", "simple-bus";
> > +                     compatible = "samsung,s5pv210-clock";
> >                       reg = <0xe0100000 0x10000>;
> ...
> > +             pmu_syscon: syscon@e0108000 {
> > +                     compatible = "samsung-s5pv210-pmu", "syscon";
> > +                     reg = <0xe0108000 0x8000>;
> >               };
>
> Should clock-controller@e0100000's reg be shortened to 0x8000 so that
> the ranges do not overlap?
>
> Signed-off-by: Pavel Machek (CIP) <pavel@denx.de>

I don't think this commit should be backported to stable. It is simple
dtbs_check - checking whether Devicetree source matches device tree
schema. Neither the schema nor the warning existed in v4.19. I think
dtbs_check fixes should not be backported, unless a real issue is
pointed out.

Best regards,
Krzysztof