From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <sha@pengutronix.de>,
Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: i.MX watchdog druver regression
Date: Fri, 21 Oct 2022 13:47:35 +0200 [thread overview]
Message-ID: <00b11081-9943-0806-9efc-6d17f1e59c8d@pengutronix.de> (raw)
In-Reply-To: <20221021114350.GA6702@pengutronix.de>
On 21.10.22 13:43, Sascha Hauer wrote:
> On Fri, Oct 21, 2022 at 12:53:59PM +0300, Alexander Shiyan wrote:
>> Hello!
>>
>> An error occurred while registering the i.MX watchdog driver:
>>
>> barebox 2022.06.0-00530-g31d9ff81c63c-dirty #44 Fri Oct 21 12:13:36 MSK 2022
>> ...
>> ERROR: imx-watchdog 73f98000.watchdog@73f98000.of: probe failed: No
>> such file or directory
>> ...
>>
>> Thought it was the result of a patch "watchdog: imxwd: get and enable clock",
>> and added the line:
>> clks[IMX5_CLK_DUMMY] = clk_fixed("dummy", 0);
>> into the beginning of the mx5_clocks_common_init() function, but this
>> does not help...
>
> If the missing clock is the problem then you also have to tell the clock
> core that the dummy clock shall be provided to the watchdog, something
> like:
>
> clkdev_add_physbase(clks[IMX5_CLK_DUMMY], MX53_WDOG1_BASE_ADDR, NULL);
> clkdev_add_physbase(clks[IMX5_CLK_DUMMY], MX53_WDOG2_BASE_ADDR, NULL);
>
> similar is missing for i.MX51 as well
But the imx50.dtsi device tree already has
clocks = <&clks IMX5_CLK_DUMMY>;
>
> Sascha
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-10-21 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 9:53 Alexander Shiyan
2022-10-21 11:43 ` Sascha Hauer
2022-10-21 11:47 ` Ahmad Fatoum [this message]
2022-10-21 11:56 ` Sascha Hauer
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=00b11081-9943-0806-9efc-6d17f1e59c8d@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.com \
--cc=sha@pengutronix.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