From: Michael Trimarchi <michael@amarulasolutions.com>
To: "Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-phy@lists.infradead.org,
linux-amarula@amarulasolutions.com
Subject: [RFC PATCH 1/4] phy: add PHY_MODE_TTL
Date: Sun, 2 Oct 2022 08:45:37 +0200 [thread overview]
Message-ID: <20221002064540.2500257-2-michael@amarulasolutions.com> (raw)
In-Reply-To: <20221002064540.2500257-1-michael@amarulasolutions.com>
There are combo phys out there that can be switched between doing
dsi, lvds, and ttl. So add a mode definition for it.
Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
---
include/linux/phy/phy.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
index b1413757fcc3..87ae8c27ec57 100644
--- a/include/linux/phy/phy.h
+++ b/include/linux/phy/phy.h
@@ -42,7 +42,8 @@ enum phy_mode {
PHY_MODE_MIPI_DPHY,
PHY_MODE_SATA,
PHY_MODE_LVDS,
- PHY_MODE_DP
+ PHY_MODE_DP,
+ PHY_MODE_TTL
};
enum phy_media {
--
2.34.1
next prev parent reply other threads:[~2022-10-02 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 6:45 [RFC PATCH 0/4] Add RGB ttl connection on rockchip phy Michael Trimarchi
2022-10-02 6:45 ` Michael Trimarchi [this message]
2022-10-02 6:45 ` [RFC PATCH 2/4] phy: rockchip: Add inno_is_valid_phy_mode Michael Trimarchi
2023-01-13 17:58 ` Vinod Koul
2022-10-02 6:45 ` [RFC PATCH 3/4] phy: rockchip: Implement TTY phy mode Michael Trimarchi
2022-10-02 6:45 ` [RFC PATCH 4/4] drm/rockchip: rgb: Add dphy connection to rgb output Michael Trimarchi
2022-12-19 12:35 ` [RFC PATCH 0/4] Add RGB ttl connection on rockchip phy Michael Nazzareno Trimarchi
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=20221002064540.2500257-2-michael@amarulasolutions.com \
--to=michael@amarulasolutions.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=kishon@ti.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=vkoul@kernel.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).