From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tony Lindgren <tony@atomide.com>, <linux-omap@vger.kernel.org>
Cc: Dave Gerlach <d-gerlach@ti.com>, Faiz Abbas <faiz_abbas@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Keerthy <j-keerthy@ti.com>, Nishanth Menon <nm@ti.com>,
Suman Anna <s-anna@ti.com>, Tero Kristo <t-kristo@ti.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: omap5: Add l4 interconnect hierarchy and ti-sysc data
Date: Wed, 12 Dec 2018 12:46:02 +0200 [thread overview]
Message-ID: <ebc7e271-8717-fe9d-d24f-ae406860b913@ti.com> (raw)
In-Reply-To: <9b7e07ae-66f9-cedf-937d-b1c5c510e018@ti.com>
On 12/12/2018 12.12, Peter Ujfalusi wrote:
> Tony,
>
> On 16/11/2018 0.45, Tony Lindgren wrote:
>> Similar to commit 8f42cb7f64c7 ("ARM: dts: omap4: Add l4 interconnect
>> hierarchy and ti-sysc data"), let's add proper interconnect hierarchy
>> for l4 interconnect instances with the related ti-sysc interconnect
>> module data as in Documentation/devicetree/bindings/bus/ti-sysc.txt.
>>
>> Using ti-sysc driver binding allows us to start dropping legacy platform
>> data in arch/arm/mach-omap2/omap*hwmod*data.c files later on in favor of
>> ti-sysc dts data.
>>
>> This data is generated based on platform data from a booted system
>> and the interconnect acces protection registers for ranges. To avoid
>> regressions, we initially validate the device tree provided data
>> against the existing platform data on boot.
>
> Reverting this patch in linux-next-20181210 will make the ethernet
> working again.
>
> bootlog w/ revert: https://pastebin.com/dpRk1xWv
> bootlog w/o revert: https://pastebin.com/PWrBttxd
on omap5-uevm.
- Péter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2018-12-12 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 22:45 Tony Lindgren
2018-12-12 10:12 ` Peter Ujfalusi
2018-12-12 10:46 ` Peter Ujfalusi [this message]
2018-12-12 17:11 ` Tony Lindgren
2018-12-13 1:19 ` 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=ebc7e271-8717-fe9d-d24f-ae406860b913@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®