From: danielhilst@gmail.com (Daniel.)
To: kernelnewbies@lists.kernelnewbies.org
Subject: omap watchdog
Date: Thu, 27 Oct 2016 17:56:29 -0200 [thread overview]
Message-ID: <CAF3SDA4ezhbVhzsbocVWS+CKOmcQQTUeaKptWiPh7dHfkQOKQg@mail.gmail.com> (raw)
In-Reply-To: <1654062.sPNIygC3qZ@corpeters>
Seems a bug to me, you should post it to linux-omap :)
Regards,
2016-10-27 6:14 GMT-02:00 Cor Peters <cpeters@victronenergy.com>:
> Hello everybody
>
> I was looking into an issue with the omap-wdt.c. The watchdog driver not is
> reporting a different boot status when a reset is being triggered by the
> watchdog.
>
> >From what I gathered, the issue is that in the omap_wdt_probe function,
> pdev->dev->platform_data requires to be a reference to the PRM module,
> however it has not been set, and I was wondering how this should work in
> an environment that uses the device tree method. (Link to usage:
> http://lxr.free-electrons.com/source/drivers/watchdog/omap_wdt.c#L268 ).
>
> My questions are as follows:
> 1) Is my assertion correct that the current method does not work when
> the driver is being initialised from an device tree instead of a old style
> board file.
> 2) If that is the case, what would be the best method of fixing this
> situation.
>
> Thank you very much in advance.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
"Do or do not. There is no try"
Yoda Master
prev parent reply other threads:[~2016-10-27 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1477065601.24788.kernelnewbies@kernelnewbies.org>
2016-10-21 17:04 ` Kernelnewbies Digest, Vol 71, Issue 26 Laurence Rochfort
2016-10-21 17:40 ` Valdis.Kletnieks at vt.edu
2016-10-21 17:52 ` Laurence Rochfort
2016-10-27 8:14 ` omap watchdog Cor Peters
2016-10-27 19:56 ` Daniel. [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=CAF3SDA4ezhbVhzsbocVWS+CKOmcQQTUeaKptWiPh7dHfkQOKQg@mail.gmail.com \
--to=danielhilst@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).