From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: at91: sama5d2: add ETM, ETB and ETMCK node
Date: Mon, 4 Jul 2016 11:00:18 +0200 [thread overview]
Message-ID: <20160704110018.76288816@bbrezillon> (raw)
In-Reply-To: <CALdGsk+RO_cxfcTLVyKHP3aVMkSTtzEzQXz2G4ARX7vqxRazSA@mail.gmail.com>
On Mon, 4 Jul 2016 10:47:21 +0200
Olivier Schonken <olivier.schonken@gmail.com> wrote:
> Hi Boris
>
> The amba bus is probed after the PIT driver.
So we clearly have a problem in there...
> I have today found pck0 -
> pck2 to work as well. Would this be good enough to use?
But why would we reference one of the programmable clock? AFAICT, the
coresight-etb10 block does not depend on any of the programmable clock.
>
> Regards
>
> Olivier
>
> On 2 July 2016 at 20:46, Boris Brezillon <boris.brezillon@free-electrons.com
> > wrote:
>
> > Hi Olivier,
> >
> > On Fri, 1 Jul 2016 22:07:53 +0200
> > Olivier Schonken <olivier.schonken@gmail.com> wrote:
> >
> > > Hi Alexandre
> > >
> > > Resending this mail, the previous one was accidentally in html format,
> > > thus rejected from the list. My apologies.
> > >
> > > I did try a couple of options regarding the clock, mck included, but
> > > it would then hang when probing occurs in drivers/amba/bus.c when the
> > > clock gets disabled. The dummy clock solved this issue, but I'm open
> > > to better suggestions.
> >
> > Hm, that's really weird. Is the AMBA bus driver probed before the PIT
> > driver?
> > Anyway, I agree that this dummy clock approach is not ideal. Could we
> > make the apb_pclk clock optional in the AMBA bus driver?
> >
> > The other approach would be to have someone claim the mck clock before
> > the AMBA bus driver, and keep it enabled.
> >
> > Regards,
> >
> > Boris
> >
next prev parent reply other threads:[~2016-07-04 9:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 14:37 [PATCH 1/2] coresight-etm3x: Add ARM ETM-A5 peripheral ID Olivier Schonken
2016-07-01 14:37 ` [PATCH 2/2] ARM: dts: at91: sama5d2: add ETM, ETB and ETMCK node Olivier Schonken
2016-07-01 18:32 ` Alexandre Belloni
2016-07-01 20:07 ` Olivier Schonken
2016-07-02 18:46 ` Boris Brezillon
2016-07-04 8:49 ` Olivier Schonken
[not found] ` <CALdGsk+RO_cxfcTLVyKHP3aVMkSTtzEzQXz2G4ARX7vqxRazSA@mail.gmail.com>
2016-07-04 9:00 ` Boris Brezillon [this message]
2016-07-04 9:08 ` Olivier Schonken
2016-07-04 16:02 ` Alexandre Belloni
2016-07-04 20:26 ` Boris Brezillon
2016-07-04 20:47 ` Alexandre Belloni
2016-07-04 20:51 ` Boris Brezillon
2016-07-04 15:38 ` Mathieu Poirier
2016-07-04 15:33 ` [PATCH 1/2] coresight-etm3x: Add ARM ETM-A5 peripheral ID Mathieu Poirier
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=20160704110018.76288816@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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