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=-8.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 13873C7618F for ; Mon, 22 Jul 2019 17:49:17 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E01E021901 for ; Mon, 22 Jul 2019 17:49:16 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="qzc4ilPH" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E01E021901 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=MGWWsERVx4VgcR8nIVodfx0d+JNFV+mrdx8S1VE4jJQ=; b=qzc4ilPHMWxHzJ 8jJVtNVUfRqLElzzAjgMmRSE1dQT23cPUPTlGD9go9XTnLNaqKBEkxPiRU3j9Q5qqxtZSJ0zW1892 TYVGAHx70XRQZtD/qCPAV4QzHhZR0xskjL5hng9xi+MjGSGMn5fmk/VGBTeZJZQO0qa/yW/LUqWTI b9Ybhwe55shYYyzjC91svbq2MZKk6Q4ysnDzZ0WxCjZnd5YZYWkbpBaCeIZ5ftGAQ0rhAYPXt0G0p 1rcVkwK8vkKoi2ulKT2ayQwCnekOc9MtuXklOgXKm3kZZiuYxCTV8jXYom28HnWTehnABNzn1VPJA aDTinmi3VPlOBW/jcDIg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hpcQn-0003UY-Qv; Mon, 22 Jul 2019 17:49:02 +0000 Received: from mail-io1-f67.google.com ([209.85.166.67]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hpcQh-0003U3-JN for linux-arm-kernel@lists.infradead.org; Mon, 22 Jul 2019 17:48:57 +0000 Received: by mail-io1-f67.google.com with SMTP id k20so75811180ios.10 for ; Mon, 22 Jul 2019 10:48:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=CxrJ1h1Gj9qffdtw6gn6IuFX9kNT09jtgH+ckcJPTWk=; b=PMZETR8ktltwkExySofX0Yp9v0C+ZjizxNGwp+CB9x0ABbd118iTYZAcs91OqEZDVy QKoDu+J+EZYuULBiar1QfalMUG1ZXpoLakkY7SfzEvcpTQhWzhwM9UNDKLsYWzXdSF9V cGjWq77b2mPS09nafcotMlLB2eiDtRa8WyjQqeKAoqXSBRiLcafZzBxzFHUeEAAVRcoW xtowUO2pLCIVUXMUOoe6iNHNj1FNUOOpOyg1tuLluJ2Y43MWipV0E51gsrUyjOJDvRuJ QknezbJ/aSuh+ma7Gq6TBjBO1EK+NcmrOfmY0GOKusmuglAp4tkpvoEeOTXRzY2naHrK Aptg== X-Gm-Message-State: APjAAAXriQEiUcZ48t2oUlFmvh3O49gE6ulOFOguXjj2RxGI980Epku/ YZ6XoA9R/vxvTH308aL3jw== X-Google-Smtp-Source: APXvYqw0FDve9Mw/vkxriVI+KvJ+PlrXuiZ8o2qd7ioxmjQY7NUFYzDL8hVPS4tO0BHR0p8241W5WA== X-Received: by 2002:a02:90c8:: with SMTP id c8mr75947688jag.22.1563817734501; Mon, 22 Jul 2019 10:48:54 -0700 (PDT) Received: from localhost ([64.188.179.254]) by smtp.gmail.com with ESMTPSA id c81sm62071726iof.28.2019.07.22.10.48.53 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 22 Jul 2019 10:48:54 -0700 (PDT) Date: Mon, 22 Jul 2019 11:48:53 -0600 From: Rob Herring To: Robert Chiras Subject: Re: [PATCH 05/10] dt-bindings: display: Add max-res property for mxsfb Message-ID: <20190722174853.GA31795@bogus> References: <1561555938-21595-1-git-send-email-robert.chiras@nxp.com> <1561555938-21595-6-git-send-email-robert.chiras@nxp.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1561555938-21595-6-git-send-email-robert.chiras@nxp.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190722_104855_888997_48433399 X-CRM114-Status: GOOD ( 15.32 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Marek Vasut , Mark Rutland , Pengutronix Kernel Team , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, David Airlie , Fabio Estevam , Sascha Hauer , linux-kernel@vger.kernel.org, Stefan Agner , NXP Linux Team , Daniel Vetter , Shawn Guo , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Jun 26, 2019 at 04:32:13PM +0300, Robert Chiras wrote: > Add new optional property 'max-res', to limit the maximum supported > resolution by the MXSFB_DRM driver. Bindings are for h/w description, not driver config. > > Signed-off-by: Robert Chiras > --- > Documentation/devicetree/bindings/display/mxsfb.txt | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/mxsfb.txt b/Documentation/devicetree/bindings/display/mxsfb.txt > index 472e1ea..55e22ed 100644 > --- a/Documentation/devicetree/bindings/display/mxsfb.txt > +++ b/Documentation/devicetree/bindings/display/mxsfb.txt > @@ -17,6 +17,12 @@ Required properties: > Required sub-nodes: > - port: The connection to an encoder chip. > > +Optional properties: > +- max-res: an array with a maximum of two integers, representing the > + maximum supported resolution, in the form of > + , ; if one of the item is <0>, the default > + driver-defined maximum resolution for that axis is used I suppose what you are after is bandwidth limits? IIRC, there's already some bindings expressing such limits. Also, wouldn't you need to account for bpp and using the 2nd plane (IIRC that there is one). Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel