All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] watchdog: Add Cadence watchdog driver
Date: Wed, 28 Feb 2018 12:19:20 +0100	[thread overview]
Message-ID: <CAHTX3dLpazYvcgOwMOo2BT4yBKkRRNySdJK=z+ub-9pJBXEidA@mail.gmail.com> (raw)
In-Reply-To: <20180228120627.15457852@jawa>

HI,

2018-02-28 12:06 GMT+01:00 Lukasz Majewski <lukma@denx.de>:

> Hi Michal,
>
> > Hi,
> >
> > 2018-02-28 9:51 GMT+01:00 Lukasz Majewski <lukma@denx.de>:
> >
> > > Hi Michal,
> > >
> > > > From: Shreenidhi Shedi <imshedi@gmail.com>
> > > >
> > > > This IP can be found on Zynq and ZynqMP devices.
> > > > The driver was tested with reset-on-timeout; feature.
> > > >
> > > > Also adding WATCHDOG symbol to Kconfig because it is required.
> > >
> > > If I may ask - what is the purpose of adding separate WATCHDOG
> > > symbol?
> > >
> > > Cannot HW_WATCHDOG or CONFIG_WDT be reused?
> > >
> > > Please look into ULP_WATCHDOG as a reference.
> > >
> > >
> > ULP_WATCHDOG hasn't been converted to DM that's why you use
> > hw_watchdog wiring.
> >
> > CONFIG_WDT is used for enabling watchdog uclass.
> > CONFIG_WDT_CDNS - for enabling cadence DM watchdog driver
> > CONFIG_WATCHDOG - for servicing watchdog by u-boot
>         ^^^^^^^^^ - I'm just wondering about this one. How does it
>         corresponds to CONFIG_HW_WATCHDOG?
>

include/watchdog.h

 32 #if defined(CONFIG_HW_WATCHDOG) && defined(CONFIG_WATCHDOG)
 33 #  error "Configuration error: CONFIG_HW_WATCHDOG and CONFIG_WATCHDOG
can't be used together."
 34 #endif

HW_WATCHDOG - non DM drivers, WATCHDOG DM drivers.

M


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform

      reply	other threads:[~2018-02-28 11:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  9:09 [U-Boot] [PATCH v2 1/3] watchdog: Add Cadence watchdog driver Michal Simek
2018-02-26  9:09 ` [U-Boot] [PATCH v2 2/3] arm: zynq: Wire watchdog internals Michal Simek
2018-02-28  8:55   ` Lukasz Majewski
2018-02-28  9:29     ` Michal Simek
2018-02-28  9:42       ` Lukasz Majewski
2018-02-28  9:58         ` Michal Simek
2018-02-28 11:17           ` Lukasz Majewski
2018-02-28 11:24             ` Michal Simek
2018-02-26  9:09 ` [U-Boot] [PATCH v2 3/3] arm: zynq: Enable cadence driver on zc706 Michal Simek
2018-02-28  8:51 ` [U-Boot] [PATCH v2 1/3] watchdog: Add Cadence watchdog driver Lukasz Majewski
2018-02-28  9:34   ` Michal Simek
2018-02-28 11:06     ` Lukasz Majewski
2018-02-28 11:19       ` Michal Simek [this message]

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='CAHTX3dLpazYvcgOwMOo2BT4yBKkRRNySdJK=z+ub-9pJBXEidA@mail.gmail.com' \
    --to=monstr@monstr.eu \
    --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 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.