From: Serge Semin <Sergey.Semin@baikalelectronics.ru>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: Serge Semin <fancer.lancer@gmail.com>,
"Nguyen, Dinh" <dinh.nguyen@intel.com>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: clocksource: dw_apb_timer: commit 6d2e16a3181b broke Arria10 platform
Date: Fri, 31 Jul 2020 19:41:57 +0300 [thread overview]
Message-ID: <20200731164157.4xuh3kwqs7sfuvmn@mobilestation> (raw)
In-Reply-To: <5304f0ca-e098-a9f0-9f72-1485a286d93a@kernel.org>
On Fri, Jul 31, 2020 at 10:56:37AM -0500, Dinh Nguyen wrote:
> Hi Serge,
>
> On 7/31/20 1:48 AM, Serge Semin wrote:
> > Hello Dinh,
> > It must be something wrong with your timer2 and timer3 declared in the Arria10
> > dts because the patch didn't change anything for the first two timers (timer0 and
> > timer1). It just permits to register all DW APB Timers found in dts.
> >
> > If those timers are broken, then you should have disabled them in the dts in the
> > first place. If they are normal, then you need to investigate further why do
> > they cause the kernel panic.
> >
>
> Indeed, the dts reg entry for timer3 was broken. Thanks alot for
> exposing the issue. Apologies for the noise.
No worries. Glad I could help.
-Sergey
>
> Dinh
prev parent reply other threads:[~2020-07-31 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SA0PR11MB4590258490EB0DD191778F04E4710@SA0PR11MB4590.namprd11.prod.outlook.com>
2020-07-31 6:48 ` clocksource: dw_apb_timer: commit 6d2e16a3181b broke Arria10 platform Serge Semin
2020-07-31 15:56 ` Dinh Nguyen
2020-07-31 16:41 ` Serge Semin [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=20200731164157.4xuh3kwqs7sfuvmn@mobilestation \
--to=sergey.semin@baikalelectronics.ru \
--cc=daniel.lezcano@linaro.org \
--cc=dinguyen@kernel.org \
--cc=dinh.nguyen@intel.com \
--cc=fancer.lancer@gmail.com \
--cc=linux-kernel@vger.kernel.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).