From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-omap@vger.kernel.org, "Tero Kristo" <t-kristo@ti.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: Add am335x mcasp with l3 data port ranges
Date: Mon, 10 Dec 2018 08:21:23 -0800 [thread overview]
Message-ID: <20181210162123.GC6707@atomide.com> (raw)
In-Reply-To: <7e50de23-10d3-511b-a16d-4c32ba58a842@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [181210 16:13]:
> Tony,
>
> On 10/12/2018 17.44, Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [181210 14:49]:
> >> * Peter Ujfalusi <peter.ujfalusi@ti.com> [181210 09:52]:
> >>> On 10/12/2018 9.05, Peter Ujfalusi wrote:
> >>>> Works fine on bbb + audio cape.
> >>>> For some reason my am335x-evm-sk is not booting up at all w/ linux-next,
> >>>> but I believe it is not related to this (disabled audio and still not
> >>>> booting).
> >>>
> >>> bisect on next-20181207 (am335x-evm-sk) points to:
> >>> Author: Tony Lindgren <tony@atomide.com>
> >>> 87fc89ced3a78f7f0845afab1934d509ef4ad0f2
> >>> ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc
> >>>
> >>> when looking for the non booting of am335x-evm-sk (nothing printed on
> >>> serial after stating kernel).
> >>
> >> OK I'm pretty sure this is because we now need to move the gpio1
> >> ti,no-reset-on-init up to the module level because of the DDR being
> >> GPIO controlled. I'll send a patch out shortly for that.
> >>
> >> It might be also worth adding a check for having ti,no-reset-on-init
> >> at the child level to ti-sysc driver too.
> >
> > Looks like we have quite a few boards variants with probably
> > DDR powered by a gpio1 pin. So let's fix the ti-sysc driver first,
> > care to try the following patch?
>
> am335x-evmsk is still not booting with this patch on top of next-20181210.
Oh interesting.
> Fwiw 'git grep ti,no-reset-on-idle' yields no results...
> Where it should be?
Sorry it should be ti,no-reset-on-init.
Regards,
Tony
next prev parent reply other threads:[~2018-12-10 16:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 23:03 [PATCH] ARM: dts: Add am335x mcasp with l3 data port ranges Tony Lindgren
2018-12-10 7:05 ` Peter Ujfalusi
2018-12-10 9:53 ` Peter Ujfalusi
2018-12-10 13:46 ` Peter Ujfalusi
2018-12-10 14:50 ` Tony Lindgren
2018-12-10 15:12 ` Tero Kristo
2018-12-10 15:28 ` Peter Ujfalusi
2018-12-10 14:48 ` Tony Lindgren
2018-12-10 15:44 ` Tony Lindgren
2018-12-10 16:14 ` Peter Ujfalusi
2018-12-10 16:21 ` Tony Lindgren [this message]
2018-12-10 16:38 ` Tony Lindgren
2018-12-10 17:01 ` Peter Ujfalusi
2018-12-10 17:23 ` Tony Lindgren
2018-12-11 7:11 ` Peter Ujfalusi
2018-12-11 8:20 ` Peter Ujfalusi
2018-12-11 10:55 ` Peter Ujfalusi
2018-12-11 14:18 ` Tony Lindgren
2018-12-10 22:20 ` Tony Lindgren
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=20181210162123.GC6707@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.com \
/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).