From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCHv6 0/4] omapdrm: DSI command mode panel support Date: Thu, 30 May 2019 00:02:30 -0700 Message-ID: <20190530070230.GR5447@atomide.com> References: <20190523200756.25314-1-sebastian.reichel@collabora.com> <60c45d23-de2f-d94a-c3d7-146a2bee538f@ti.com> <20190527112122.GJ5447@atomide.com> <20190528093952.GM5447@atomide.com> <14c6c702-844b-756d-2d97-44e8f5a169df@ti.com> <20190528101847.GN5447@atomide.com> <20190529081038.GP5447@atomide.com> <20190530054640.GQ5447@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20190530054640.GQ5447@atomide.com> Sender: linux-kernel-owner@vger.kernel.org To: Tomi Valkeinen Cc: Sebastian Reichel , Sebastian Reichel , Pavel Machek , Laurent Pinchart , "H. Nikolaus Schaller" , dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@collabora.com, Keerthy , Peter Ujfalusi List-Id: linux-omap@vger.kernel.org * Tony Lindgren [190530 05:47]: > * Tony Lindgren [190529 08:11]: > > * Tomi Valkeinen [190529 07:06]: > > > On 28/05/2019 13:18, Tony Lindgren wrote: > > > > > > > > My board is x15 rev A3, attached to AM5 EVM. I've also attached my kernel > > > > > config. > > > > > > > > Strange that this is not affecting other x15? I think timer12 would > > > > be blocked on HS devices though? > > > > > > Seems that the kernel config affects. omap2plus_defconfig boots ok. > > > > OK, this line in your oops: > > > > Unable to handle kernel paging request at virtual address 5a5a5a5a > > > > Probably means we hit some slab poison with DEBUG_SLAB set. > > Looks like your config boots fine with DEBUG_SLAB disabled > > for me. > > > > As this only happens for timer12, I wonder if we're again > > hitting some uncompress issue with corrupted dtb. Changing > > u-boot ftdaddr higher up might possibly make it go away. > > Or else there's a bug elsewhere :) > > Oh but CM_WKUPAON_TIMER12_CLKCTRL has no CLKSEL option unlike > CM_WKUPAON_TIMER1_CLKCTRL. Below is one part of the fix, but > it seems like we're missing handling somewhere as trying to > get a non-existing clock should just produce -ENODEV type error. > > And the clksel should be just handled with assigned-clocks > in general, but I think we still need it there until we > have drivers/clocksource/ timer drivers updated to boot > using early_platform_device. OK found it, we have the clkctrl clock potentially return uninitialized data. I posted two fixes for the issue: [PATCH] clk: ti: clkctrl: Fix returning uninitialized data [PATCH] ARM: dts: Drop bogus CLKSEL for timer12 on dra7 Regards, Tony