linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: allen <allen.chen@ite.com.tw>
To: unlisted-recipients:; (no To-header on input)
Cc: Allen Chen <allen.chen@ite.com.tw>,
	Jau-Chih Tseng <Jau-Chih.Tseng@ite.com.tw>,
	Kenneth Hung <Kenneth.Hung@ite.com.tw>,
	Hermes Wu <Hermes.Wu@ite.com.tw>,
	Pin-yen Lin <treapking@chromium.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/2] *** IT6505 driver read dt properties ***
Date: Thu, 6 Oct 2022 10:04:42 +0800	[thread overview]
Message-ID: <20221006020444.15823-1-allen.chen@ite.com.tw> (raw)

From: allen chen <allen.chen@ite.com.tw>

This series let driver can read properties from dt to restrict dp output
bandwidth.

Changes in v3:
-Rename property name.

allen chen (2):
  dt-bindings: it6505: add properties to restrict output bandwidth
  drm/bridge: add it6505 driver to read data-lanes and
    max-pixel-clock-mhz from dt

 .../bindings/display/bridge/ite,it6505.yaml   | 12 +++++++
 drivers/gpu/drm/bridge/ite-it6505.c           | 36 +++++++++++++++++--
 2 files changed, 45 insertions(+), 3 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-10-06  2:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06  2:04 allen [this message]
2022-10-06  2:04 ` [PATCH v3 1/2] dt-bindings: it6505: add properties to restrict output bandwidth allen
2022-10-06  8:16   ` Krzysztof Kozlowski
2022-10-07  3:18     ` allen.chen
2022-10-07  6:58       ` Krzysztof Kozlowski
2022-10-06 12:27   ` Rob Herring
2022-10-06 12:54   ` Rob Herring
2022-10-06  2:04 ` [PATCH v3 2/2] drm/bridge: add it6505 driver to read data-lanes and max-pixel-clock-mhz from dt allen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221006020444.15823-1-allen.chen@ite.com.tw \
    --to=allen.chen@ite.com.tw \
    --cc=Hermes.Wu@ite.com.tw \
    --cc=Jau-Chih.Tseng@ite.com.tw \
    --cc=Kenneth.Hung@ite.com.tw \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=treapking@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).