Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1664854ybe; Wed, 11 Sep 2019 19:45:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqzroPUZ9vPSjnokJwzcxm4zKtxwZREz7+pdE6uY4f69SPIr+DUm/YVXHTUoqa4qwPdIRfAw X-Received: by 2002:a17:906:1f14:: with SMTP id w20mr15399191ejj.272.1568256331541; Wed, 11 Sep 2019 19:45:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568256331; cv=none; d=google.com; s=arc-20160816; b=e1RAEYKyuAPFHuskSuWUEaWAXAL/r/WCMKVfHHs8+ArI2r/DWDO0UvoY7TEMG1Ohhj 8hwo+8SizBi1tHFqw9L9Wf70alhfDq9fpoWhMQ5pKQwPyDA6gPmmIZ8njAjzueEslbfD K7fFdxetx2yC043kwu/WaxPJN+uGOIdxY3+D08wDR+oJdQWAnLrkCfGVG4ZLwOte+n5D DBvwClevVWBmg5A4iOeMNspVOGFS0Ods7GvHDrouyNWJ3n/AiptIxJtD/Ll3zG/DZTXX IEHcWIWX2e59za7ThZgF3FNouRcfKeTrwCfNQaQeuQfKoCgSNX9CW7YMiAhcKpmzH0ti 5T7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=GrP39eh2tbg2zaFOB64oY1gm4vOgwRLVKmpoX2YX7FU=; b=j7U2zWg69aVgBxHAYlOJQii+zxQUog1W+R0VHRrBDXDw5DxpEwrCn0gFmTJte2cKK4 ar8JHQA3Q6f6frDy2p8AduqucyYHKrp7EZGtLWKf95FiIW6iyE7g6rrk7/r8/r0iPrVd ZfS4KgF6Fs2NVQa3zMHik/LCI2f76UZka+lBCy74Fg4s4K+yc6qBAOntSzKFh8buv5PC /U9vSjFATG2uJfY/97Nw6UgPrcUu48cOnYfYCKAecA0ZrU7mcySUaNtNbUFunlI9zjAs uJy96ADuTTzOnCijZnouElFtC0tUDohcgN4NnIEBRqJZBDlqQZ49kYvwcfk8Pz9isPlU 5RPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=KE6LHdW4; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y7si1977675edp.279.2019.09.11.19.45.08; Wed, 11 Sep 2019 19:45:31 -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; dkim=pass header.i=@linaro.org header.s=google header.b=KE6LHdW4; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728854AbfILCjF (ORCPT + 99 others); Wed, 11 Sep 2019 22:39:05 -0400 Received: from mail-wr1-f66.google.com ([209.85.221.66]:45899 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727329AbfILCjF (ORCPT ); Wed, 11 Sep 2019 22:39:05 -0400 Received: by mail-wr1-f66.google.com with SMTP id l16so26595951wrv.12 for ; Wed, 11 Sep 2019 19:39:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GrP39eh2tbg2zaFOB64oY1gm4vOgwRLVKmpoX2YX7FU=; b=KE6LHdW4ZTuj4bvCJMtx+uM0Rb3HlKs6OrX55Tnau/FBW4gDZGaUPwnBTYJlReNGXi BE/+/1ZEEIwMcHYkgtZvQp1k9XOh8YsjhKGPwOqpD5hXMDnK6YJh6eBYZTAZrJsmy0Rw AqHgpH/mwPIe2ejnf6iSHuSUj9sqhzGoxaSQTmMB401IvgXUqRJ+3aMwREnWt8kq2B9C /l6zabO2bDa7QConQ0YCLq1PW0/CZ3mnHmnmc9X5YKe7giiLZu09AJhep8acXz8y7vYY o8IjNz5/QpI9hSBNq2FS4rhj39DhI4ZiYJyEd4WeaIhZa+FOYmm1zu7vIOVXsbxGAwQz N4JA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GrP39eh2tbg2zaFOB64oY1gm4vOgwRLVKmpoX2YX7FU=; b=XqQxNjCxq2zBimVCMvOgB5n7tYLqdJqYa7f6/LWXO+qVfhjh9LL5luXFKWv678uTIw jM8BYBqgGod3j7d6co5iZvvOr2EQG3uxjjcXbdn8PCnts/JZLd8OQUYKUW81rT79x3EV EvwyDcVBr06wIu4/iKVI0z44PcQLUcYpL+uD/jVwLu/9AjMu7O8d0SKaWrMww5b4roch IkbwRAiTKuiGyDIxNWuy4fms8IphJzDVJIEG/dsBVxQatqAiHEuWJG5Tb08YcKMFzvoB egKTFizguJcvVyQWZnSiqiVjTK9tn+JCsVPj65ex/n9ZKpA3ZGDMYl9BgyHeHxrAg34C kf8Q== X-Gm-Message-State: APjAAAWIFf20MNuc9TL+d3fsU9QdtiOpfYwnQv3Waae2zxLNTqLgpso3 vLSHDxBJk5XqtClRrSqoqSYM6TNOK/4KSqz8NZ99nw== X-Received: by 2002:a5d:6943:: with SMTP id r3mr4535370wrw.21.1568255942965; Wed, 11 Sep 2019 19:39:02 -0700 (PDT) MIME-Version: 1.0 References: <20190829060550.62095-1-john.stultz@linaro.org> <9d31af23-8a65-d8e8-b73d-b2eb815fcd6f@samsung.com> In-Reply-To: <9d31af23-8a65-d8e8-b73d-b2eb815fcd6f@samsung.com> From: John Stultz Date: Wed, 11 Sep 2019 19:38:50 -0700 Message-ID: Subject: Re: [RFC][PATCH] drm: kirin: Fix dsi probe/attach logic To: Andrzej Hajda Cc: Rob Clark , Jernej Skrabec , Jonas Karlman , David Airlie , Neil Armstrong , lkml , "dri-devel@lists.freedesktop.org" , Xinliang Liu , Thierry Reding , Sean Paul , Laurent Pinchart , Rongrong Zou , Sam Ravnborg , Matt Redfearn , Amit Pundir Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 4, 2019 at 3:26 AM Andrzej Hajda wrote: > On 03.09.2019 18:18, John Stultz wrote: > > On Mon, Sep 2, 2019 at 6:22 AM Andrzej Hajda wrote: > >> On 30.08.2019 19:00, Rob Clark wrote: > >>> On Thu, Aug 29, 2019 at 11:52 PM Andrzej Hajda wrote: > >>>> Of course it seems you have different opinion what is the right thing in > >>>> this case, so if you convince us that your approach is better one can > >>>> revert the patch. > >>> I guess my strongest / most immediate opinion is to not break other > >>> existing adv75xx bridge users. > >> > >> It is pity that breakage happened, and next time we should be more > >> strict about testing other platforms, before patch acceptance. > >> > >> But reverting it now will break also platform which depend on it. > > I'm really of no opinion of which approach is better here, but I will > > say that when a patch breaks previously working boards, that's a > > regression and justifying that some other board is now enabled that > > would be broken by the revert (of a patch that is not yet upstream) > > isn't really a strong argument. > > > > I'm happy to work with folks to try to fixup the kirin driver if this > > patch really is the right approach, but we need someone to do the same > > for the db410c, and I don't think its fair to just dump that work onto > > folks under the threat of the board breaking. > > > These drivers should be fixed anyway - assumption that > drm_bridge/drm_panel will be registered before the bus it is attached to > is just incorrect. > > So instead of reverting, fixing and then re-applying the patch I have > gently proposed shorter path. If you prefer long path we can try to go > this way. > > Matt, is the pure revert OK for you or is it possible to prepare some > workaround allowing cooperation with both approaches? Rob/Andrzej: What's the call here? Should I resubmit the kirin fix for the adv7511 regression here? Or do we revert the adv7511 patch? I believe db410c still needs a fix. I'd just like to keep the HiKey board from breaking, so let me know so I can get the fix submitted if needed. thanks -john