From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8F704C34983 for ; Fri, 13 Dec 2019 20:36:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A2EE5246A2 for ; Fri, 13 Dec 2019 20:36:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="VZJazS+w" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726680AbfLMLmS (ORCPT ); Fri, 13 Dec 2019 06:42:18 -0500 Received: from perceval.ideasonboard.com ([213.167.242.64]:52992 "EHLO perceval.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725980AbfLMLmS (ORCPT ); Fri, 13 Dec 2019 06:42:18 -0500 Received: from pendragon.ideasonboard.com (81-175-216-236.bb.dnainternet.fi [81.175.216.236]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 6C5379F4; Fri, 13 Dec 2019 12:42:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1576237336; bh=Lb3INQXShawpZfSHODIdowd9VOhGos0XfP5YIGq/8Q0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=VZJazS+wPV46RHeDB7OJ5hxsroytmO1lhn3W99v6cUOEvbRIT35GaSwR9oJ4KikPr fnHjWQYyjAQ73LmaQPZBQ+h9L6mqzf3YwcTnPPoApCZ0Sg2v7hdULqJUmOnKEpNIz4 iTCu2H/qjtHyhwzMJNfVqPZuXA01yqLBptR+d22Y= Date: Fri, 13 Dec 2019 13:42:07 +0200 From: Laurent Pinchart To: Tomi Valkeinen Cc: Tony Lindgren , linux-omap@vger.kernel.org, devicetree@vger.kernel.org, robh+dt@kernel.org, mark.rutland@arm.com, dri-devel@lists.freedesktop.org, Linus Walleij Subject: Re: [PATCH 1/4] ARM: dts: am437x-gp-evm: add HDMI support Message-ID: <20191213114207.GC4860@pendragon.ideasonboard.com> References: <20191125131100.9839-1-tomi.valkeinen@ti.com> <20191212172104.GY35479@atomide.com> <20191212173110.GA35479@atomide.com> <20191213104204.GB4860@pendragon.ideasonboard.com> <2f5cfca4-d36d-da2d-59ba-b76669daeded@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <2f5cfca4-d36d-da2d-59ba-b76669daeded@ti.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Hi Tomi, On Fri, Dec 13, 2019 at 12:56:31PM +0200, Tomi Valkeinen wrote: > On 13/12/2019 12:42, Laurent Pinchart wrote: > > >> I think the correct way would be to have DRM framework understand that we have two displays, which > >> are mutually exclusive, and the display pipeline drivers would have the means to switch the gpio. > >> And that the display setup could be communicated properly to the userspace, and the userspace would > >> understand it. I don't think any of those exists. > > > > Isn't this what possible_clones in drm_encoder is for ? It notifies > > userspace of mutual exclusions between encoders. > > Hmm, how would that work here? Isn't encoder cloning about having two encoders, which take the input > from the same video source, and then outputting to two displays? That's the idea. If you have one encoder for HDMI and one for the panel, you can mark them as non-clonable, and then only one of the two can be active at a time. -- Regards, Laurent Pinchart