From: Chris Zhong <zyw@rock-chips.com>
To: dianders@chromium.org, tfiga@chromium.org, heiko@sntech.de,
yzq@rock-chips.com, groeck@chromium.org,
myungjoo.ham@samsung.com, cw00.choi@samsung.com,
wulf@rock-chips.com, marcheu@chromium.org,
briannorris@chromium.org, zhengxing@rock-chips.com,
cychiang@chromium.org, hychao@chromium.org, broonie@kernel.org
Cc: linux-rockchip@lists.infradead.org,
Chris Zhong <zyw@rock-chips.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v15 1/5] extcon: Introduce EXTCON_PROP_DISP_HPD property
Date: Fri, 9 Sep 2016 19:15:44 -0700 [thread overview]
Message-ID: <1473473748-22331-2-git-send-email-zyw@rock-chips.com> (raw)
In-Reply-To: <1473473748-22331-1-git-send-email-zyw@rock-chips.com>
EXTCON_PROP_DISP_HPD is need by display port, if the system has no hpd
interrupt, this property can be used.
Signed-off-by: Chris Zhong <zyw@rock-chips.com>
---
Changes in v15: None
Changes in v14: None
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
Changes in v1: None
include/linux/extcon.h | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/include/linux/extcon.h b/include/linux/extcon.h
index 9147c42..4411893 100644
--- a/include/linux/extcon.h
+++ b/include/linux/extcon.h
@@ -131,9 +131,21 @@
#define EXTCON_PROP_JACK_MAX 100
#define EXTCON_PROP_JACK_CNT (EXTCON_PROP_JACK_MAX - EXTCON_PROP_JACK_MIN + 1)
+/*
+ * Properties of EXTCON_TYPE_DISP.
+ *
+ * - EXTCON_PROP_DISP_HPD
+ * @type: integer (intval)
+ * @value: 0 (no hpd) or 1 (hpd)
+ * @default: 0 (no hpd)
+ *
+ */
+
+#define EXTCON_PROP_DISP_HPD 150
+
/* Properties of EXTCON_TYPE_DISP. */
#define EXTCON_PROP_DISP_MIN 150
-#define EXTCON_PROP_DISP_MAX 150
+#define EXTCON_PROP_DISP_MAX 151
#define EXTCON_PROP_DISP_CNT (EXTCON_PROP_DISP_MAX - EXTCON_PROP_DISP_MIN + 1)
/*
--
1.9.1
next prev parent reply other threads:[~2016-09-10 2:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 2:15 [PATCH v15 0/5] Rockchip Type-C DisplayPort driver Chris Zhong
2016-09-10 2:15 ` Chris Zhong [this message]
2016-09-13 5:25 ` [PATCH v15 1/5] extcon: Introduce EXTCON_PROP_DISP_HPD property Chanwoo Choi
2016-09-10 2:15 ` [PATCH v15 2/5] Documentation: bindings: add dt documentation for cdn DP controller Chris Zhong
2017-02-27 17:27 ` Enric Balletbo Serra
2016-09-10 2:15 ` [PATCH v15 3/5] drm/rockchip: cdn-dp: add cdn DP support for rk3399 Chris Zhong
2016-09-10 4:16 ` [PATCH v15.1 " Chris Zhong
2016-09-12 9:13 ` Mark Brown
2016-09-12 9:45 ` Chris Zhong
2016-09-10 2:15 ` [PATCH v15 4/5] drm/rockchip: cdn-dp: support audio hot-plug Chris Zhong
2016-09-10 2:15 ` [PATCH v15 5/5] ASoC: rockchip: Add DP dai-links to the rk3399-gru machine driver Chris Zhong
2016-09-19 21:37 ` Rob Herring
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=1473473748-22331-2-git-send-email-zyw@rock-chips.com \
--to=zyw@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=cychiang@chromium.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=heiko@sntech.de \
--cc=hychao@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marcheu@chromium.org \
--cc=myungjoo.ham@samsung.com \
--cc=tfiga@chromium.org \
--cc=wulf@rock-chips.com \
--cc=yzq@rock-chips.com \
--cc=zhengxing@rock-chips.com \
/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