From: Florian Fainelli <f.fainelli@gmail.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Paul Burton" <paulburton@kernel.org>,
"Jonas Gorski" <jonas.gorski@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] mips: bmips: fix and improve reboot nodes
Date: Tue, 30 Mar 2021 10:14:10 -0700 [thread overview]
Message-ID: <d55889f3-d952-c05b-5243-424caf0bc415@gmail.com> (raw)
In-Reply-To: <20210330130944.GB11217@alpha.franken.de>
On 3/30/21 6:09 AM, Thomas Bogendoerfer wrote:
> On Sun, Mar 14, 2021 at 05:43:45PM +0100, Álvaro Fernández Rojas wrote:
>> These patches improve bmips bcm63xx device tree nodes.
>>
>> v2: add missing BCM63268 patch.
>>
>> Álvaro Fernández Rojas (6):
>> mips: bmips: fix syscon-reboot nodes
>> mips: bmips: bcm6328: populate device tree nodes
>> mips: bmips: bcm6358: populate device tree nodes
>> mips: bmips: bcm6362: populate device tree nodes
>> mips: bmips: bcm6368: populate device tree nodes
>> mips: bmips: bcm63268: populate device tree nodes
>>
>> arch/mips/boot/dts/brcm/bcm3368.dtsi | 2 +-
>> arch/mips/boot/dts/brcm/bcm63268.dtsi | 132 +++++++++++++++++++++++---
>> arch/mips/boot/dts/brcm/bcm6328.dtsi | 119 ++++++++++++++++++++---
>> arch/mips/boot/dts/brcm/bcm6358.dtsi | 85 ++++++++++++++---
>> arch/mips/boot/dts/brcm/bcm6362.dtsi | 129 ++++++++++++++++++++++---
>> arch/mips/boot/dts/brcm/bcm6368.dtsi | 129 ++++++++++++++++++++++---
>> 6 files changed, 530 insertions(+), 66 deletions(-)
>
> Florian, are you ok with this changes ? If yes, I'm going to apply them
> to mips-next.
This all looks good to me and matches the hardware manuals as far as
resources are declared. There may be some room for doing a bit more
consolidation since there is not that much difference between SoCs after
all, maybe as a subsequent change.
--
Florian
next prev parent reply other threads:[~2021-03-30 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 16:43 [PATCH v2 0/6] mips: bmips: fix and improve reboot nodes Álvaro Fernández Rojas
2021-03-14 16:43 ` [PATCH v2 1/6] mips: bmips: fix syscon-reboot nodes Álvaro Fernández Rojas
2021-03-30 17:02 ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 2/6] mips: bmips: bcm6328: populate device tree nodes Álvaro Fernández Rojas
2021-03-30 17:07 ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 3/6] mips: bmips: bcm6358: " Álvaro Fernández Rojas
2021-03-30 17:09 ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 4/6] mips: bmips: bcm6362: " Álvaro Fernández Rojas
2021-03-30 17:10 ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 5/6] mips: bmips: bcm6368: " Álvaro Fernández Rojas
2021-03-30 17:11 ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 6/6] mips: bmips: bcm63268: " Álvaro Fernández Rojas
2021-03-30 17:13 ` Florian Fainelli
2021-03-30 13:09 ` [PATCH v2 0/6] mips: bmips: fix and improve reboot nodes Thomas Bogendoerfer
2021-03-30 17:14 ` Florian Fainelli [this message]
2021-04-06 13:02 ` Thomas Bogendoerfer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d55889f3-d952-c05b-5243-424caf0bc415@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f4bug@amsat.org \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.