Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4800879ybi; Tue, 28 May 2019 02:45:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqzoXi5Q/dRodUXYeIjJhs9fCN4fkgVq/2nDg0G0qk0p4Aj+3Qvb7z19iNl3rWG2cGe+yKr4 X-Received: by 2002:a63:8f09:: with SMTP id n9mr102338692pgd.249.1559036709301; Tue, 28 May 2019 02:45:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559036709; cv=none; d=google.com; s=arc-20160816; b=zkvrfYGbvZ9JxwJNIg5YOZGk2Sgj0Fb1AQSmyf/H6GoONof2cQmKzarR500jqaOb6E gmnDyrvcyhjsncM/ACxStOclvq7Dv71b8k2DLxaH+IviE/PGidPi2yIBJKh1bZOh8PMQ HNRvO2ccXuY0uLUgUZ9eF7cLQ9wvvtrRWdOQa+ByJ1JhVkCB0fXn8AA/L2+slD6r6zLS ji9orm4iquhIOqGWkxGr42xC3fwOjo3pZ/An6vdGOTiOc8RFZqCCmBoHlJq8/gW9yx3G 6ZvznowyoqC6FOATJGOs6Bs7x1YL3kDs1mbsdoVVb7kZ1IAOp7004QubFZ5rccMWIaL7 GKVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=WZFPP0HNd24p8DQj3FgKskUqsD4XdVlYG/0f6y600pw=; b=ntNNtU2PYX+MszQurE6uF4sT/7ZWitGagmD0/ym8XRi4cmnVvvUYZ6RQXBLG96F0pv pIcrD65wPd0S/7VqbmRV2NXSC5J8CHQPCF/R2tMmlZWgLeEfAKaax0s6h6Cb/H5lwfTi tMAMnRwgeXgWc44u6rsQCTUyoOpAPnk9BeVXDCj3Zk6RpUy4fxKJ7OGLfL6JroncJwIo NqkekThjINDIctZFVIU0Kyg1A3/ep5U75ylGD2B/vyY9/Nt7XxzWnXgfWPn6qQ/bhjDz 1QQAxQUr5+gVwhsYtIuy1HMY2yQwvOLilcJBjYdEsT4TUQKTw6xcLqRd6aaH8B3NEFaS gGRQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id gn2si20434976plb.34.2019.05.28.02.44.53; Tue, 28 May 2019 02:45:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726798AbfE1Jj5 (ORCPT + 99 others); Tue, 28 May 2019 05:39:57 -0400 Received: from muru.com ([72.249.23.125]:51514 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726236AbfE1Jj4 (ORCPT ); Tue, 28 May 2019 05:39:56 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 5C1A780F3; Tue, 28 May 2019 09:40:15 +0000 (UTC) Date: Tue, 28 May 2019 02:39:52 -0700 From: Tony Lindgren 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 Subject: Re: [PATCHv6 0/4] omapdrm: DSI command mode panel support Message-ID: <20190528093952.GM5447@atomide.com> References: <20190523200756.25314-1-sebastian.reichel@collabora.com> <60c45d23-de2f-d94a-c3d7-146a2bee538f@ti.com> <20190527112122.GJ5447@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, * Tomi Valkeinen [190528 09:19]: > On 27/05/2019 14:21, Tony Lindgren wrote: > > >> Looks good to me. For some reason I can't boot 5.2-rc2 (on x15) so I haven't > >> been able to test yet. I'll pick the series up in any case, and I'll test it > >> when I get the kernel booting. > > > > Great good to have these merged finally :) > > > > Hmm I wonder if some x15 models are affected by the SoC variant > > changes queued in my fixes branch? > > This is what I see with earlycon, on linux-omap fixes branch. I think this looks > similar to what I saw with dra76 _without_ the fixes. OK sounds like we need to use some different SoC specific .dtsi file, is this maybe x15 rev c? You can detect which modules fail based on the module base address for revision register seen with the following debug patch. Then those need to be tagged with status = "disabled" at the module level in the SoC specific dtsi file. Regards, Tony 8< -------------- diff --git a/drivers/bus/ti-sysc.c b/drivers/bus/ti-sysc.c --- a/drivers/bus/ti-sysc.c +++ b/drivers/bus/ti-sysc.c @@ -2069,6 +2069,8 @@ static int sysc_probe(struct platform_device *pdev) struct sysc *ddata; int error; + dev_info(&pdev->dev, "probing device\n"); + ddata = devm_kzalloc(&pdev->dev, sizeof(*ddata), GFP_KERNEL); if (!ddata) return -ENOMEM;