From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934265AbeEWWFC convert rfc822-to-8bit (ORCPT ); Wed, 23 May 2018 18:05:02 -0400 Received: from muru.com ([72.249.23.125]:44358 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933791AbeEWWFA (ORCPT ); Wed, 23 May 2018 18:05:00 -0400 Date: Wed, 23 May 2018 15:04:56 -0700 From: Tony Lindgren To: Pavel Machek Cc: Aaro Koskinen , Pali =?utf-8?B?Um9ow6Fy?= , sre@kernel.org, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, khilman@kernel.org, ivo.g.dimitrov.75@gmail.com, patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com, clayton@craftyguy.net, martijn@brixit.nl, sakari.ailus@linux.intel.com, Filip =?utf-8?Q?Matijevi=C4=87?= , Thorsten Leemhuis Subject: Re: v4.17-rc1: regressions on N900, N950 Message-ID: <20180523220456.GY98604@atomide.com> References: <20180422074213.GA12428@amd> <20180423202940.ig6iud5lrbgnu35a@darkstar.musicnaut.iki.fi> <20180521213952.GA11596@amd> <20180522080250.4fzyvqrgw5oigexn@pali> <20180522194139.GB2299@darkstar.musicnaut.iki.fi> <20180522205824.GA24927@amd> <20180522215638.GC2299@darkstar.musicnaut.iki.fi> <20180523140615.GA27180@amd> <20180523201208.GA31731@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: <20180523201208.GA31731@amd> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Pavel Machek [180523 20:14]: > On Wed 2018-05-23 16:06:15, Pavel Machek wrote: > > On Wed 2018-05-23 00:56:38, Aaro Koskinen wrote: > > > Hi, > > > > > > On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote: > > > > On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote: > > > > > My device worked with v4.17-rc1 (haven't found time to test newer kernels), > > > > > but if you say the probe order is random then we must find some proper way > > > > > to express the dependency. > > > > > > > > I started bisect, but.. that will probably not be useful. > > > > > > > > If your device works ok in v4.17-rc1, it probably works in newer -rcs, > > > > too. > > > > > > Actually, my statement may be bogus... Now I tried again with -rc1 > > > (and also -rc6) and it fails... But v4.16 works. > > > > > > > Thanks for the ordering hint, I'll try to figure out what is going on > > > > there. > > > > > > My bisection pointed to 6fa7324ac5489ad43c4b6351355b869bc5458bef which > > > doesn't seem to make any sense...?! So maybe there really is something > > > random stuff going on? :-( > > > > So... I did some experiments on v4.16. > > > > Swapping tsc2005@0 and lcd: acx565akm@2 entries in the dts does break > > stuff. > > > > I thought it might be due to vio regulator, but it does not appear > > so... screen still works with tsc2005 driver disabled in .config. (so > > there's noone to enable vio regulator). > > Deleting tsc2005@0 entry also breaks screen. > > Replacing tsc2005@0 entry with > > foobar@0 { > compatible = "not really with anything"; > spi-max-frequency = <6000000>; > reg = <0>; > }; > > still results in working touchscreen, removing any of the three fields > breaks it again. I bisected one regression down, see "omapdrm regression in v4.17-rc series" not sure if it covers all the issues being discussed here though. Regards, Tony