public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Michael Walle <michael@walle.cc>, Priyanka Jain <priyanka.jain@nxp.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 00/10] board: sl28: add sl28cpld support and board cleanups
Date: Mon, 31 Jan 2022 10:25:58 -0500	[thread overview]
Message-ID: <20220131152558.GU7515@bill-the-cat> (raw)
In-Reply-To: <4f5167e18902640bc13a52d20763f51c@walle.cc>

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

On Mon, Jan 31, 2022 at 08:51:39AM +0100, Michael Walle wrote:
> Am 2021-11-15 23:45, schrieb Michael Walle:
> > Add support for the sl28cpld management controller found on this board.
> > This is especially useful, because of the integrated watchdog in this
> > controller. It is used to supervise the bootup of the bootloader and
> > will
> > automatically switch to the failsafe bootloader if u-boot didn't start.
> > Up
> > until now, we had to disable this feature, leaving a gap in the failsafe
> > boot concept of this board. Now, with this driver in place, this
> > watchdog
> > can be enabled at reset and u-boot will disable it late during its
> > startup.
> > 
> > Additionally, add support for the GPIOs which are connected to this
> > controller.
> > 
> > Besides this support, there are various cleanups, like DRAM output fix,
> > printing the version of the management controller and disabling the
> > random
> > MAC address generation.
> > 
> > Implementationwise, the MFD driver is implemented as UCLASS_NOP which
> > provides basic access functions and will enumerate its child nodes. The
> > device tree binding is the same as already acked by the linux kernel.
> 
> Ping. This is now 2.5 month old. It doesn't even touch anything outside
> my own board.

Priyanka?

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2022-01-31 15:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 22:45 [PATCH 00/10] board: sl28: add sl28cpld support and board cleanups Michael Walle
2021-11-15 22:45 ` [PATCH 01/10] misc: add sl28cpld base driver Michael Walle
2021-11-15 22:45 ` [PATCH 02/10] watchdog: add sl28cpld watchdog driver Michael Walle
2021-11-15 22:45 ` [PATCH 03/10] gpio: add sl28cpld driver Michael Walle
2021-11-15 22:45 ` [PATCH 04/10] board: sl28: fix DRAM pretty print Michael Walle
2021-11-15 22:45 ` [PATCH 05/10] board: sl28: print CPLD version on bootup Michael Walle
2021-11-15 22:45 ` [PATCH 06/10] board: sl28: enable sl28cpld support Michael Walle
2021-11-15 22:45 ` [PATCH 07/10] board: sl28: enable SoC watchdog support Michael Walle
2021-11-15 22:45 ` [PATCH 08/10] board: sl28: disable recovery watchdog Michael Walle
2021-11-15 22:45 ` [PATCH 09/10] board: sl28: remove "Useful I2C tricks" section from docs Michael Walle
2021-11-15 22:45 ` [PATCH 10/10] board: sl28: disable random MAC address generation Michael Walle
2021-11-16 21:14   ` Tom Rini
2021-11-17 16:45     ` Michael Walle
2021-11-17 18:24       ` Tom Rini
2021-11-18  8:29         ` Michael Walle
2021-11-18 14:58           ` Tom Rini
2022-01-31  7:51 ` [PATCH 00/10] board: sl28: add sl28cpld support and board cleanups Michael Walle
2022-01-31 15:25   ` Tom Rini [this message]
2022-02-02  6:38     ` Priyanka Jain

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=20220131152558.GU7515@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=michael@walle.cc \
    --cc=priyanka.jain@nxp.com \
    --cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox