public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sean Anderson <seanga2@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/4] wdt: Add CONFIG_DESIGNWARE_WATCHDOG to Kconfig
Date: Sun, 2 Feb 2020 13:02:50 -0500	[thread overview]
Message-ID: <e45c27de-2578-e105-6a65-297cd3895e44@gmail.com> (raw)
In-Reply-To: <e8e13d4c-5126-d81c-3e27-3ccfb19fe3e8@denx.de>

> btw what's the motivation for this series, are you hitting some issues
> with the WDT on SoCFPGA ?

This watchdog appears on the Kendryte K210 CPU, which I am adding
support for. The rest of the board uses devicetree to configure drivers,
so I wanted to add support for this watchdog as well.

  reply	other threads:[~2020-02-02 18:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02 17:10 [PATCH 1/4] wdt: Add CONFIG_DESIGNWARE_WATCHDOG to Kconfig Sean Anderson
2020-02-02 17:12 ` [PATCH 2/4] arm: Move asm/utils.h to log2.h Sean Anderson
2020-02-02 17:24   ` Sean Anderson
2020-02-03  0:04   ` Simon Glass
2020-02-03  8:12     ` Marek Vasut
2020-02-03 15:11       ` Simon Glass
2020-02-03 15:27         ` Sean Anderson
2020-02-03 15:31           ` Simon Glass
2020-02-02 17:12 ` [PATCH 3/4] wdt: Remove dependencies on CONFIG_DW_WDT_* from Designware WDT Sean Anderson
2020-02-02 17:25   ` Sean Anderson
2020-02-02 17:13 ` [PATCH 4/4] wdt: Add DM support for " Sean Anderson
2020-02-02 17:25   ` Sean Anderson
2020-02-03  0:04     ` Simon Glass
2020-02-03  1:18       ` Sean Anderson
2020-02-03  4:03         ` Simon Glass
2020-02-02 17:15 ` [PATCH 1/4] wdt: Add CONFIG_DESIGNWARE_WATCHDOG to Kconfig Marek Vasut
2020-02-02 17:23   ` Sean Anderson
2020-02-02 17:40     ` Marek Vasut
2020-02-02 17:48       ` Sean Anderson
2020-02-02 17:52         ` Marek Vasut
2020-02-02 18:02           ` Sean Anderson [this message]
2020-02-03  8:13             ` Marek Vasut
2020-02-19 21:37               ` Sean Anderson
2020-02-20 16:39                 ` Marek Vasut
2020-02-02 17:24 ` Sean Anderson

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=e45c27de-2578-e105-6a65-297cd3895e44@gmail.com \
    --to=seanga2@gmail.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