From: "Heiko Stübner" <heiko@sntech.de>
To: Daniel Kurtz <djkurtz@chromium.org>,
David Airlie <airlied@linux.ie>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Andy Yan <andy.yan@rock-chips.com>,
fabio.estevam@freescale.com, rmk+kernel@arm.linux.org.uk,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Shawn Guo <shawn.guo@linaro.org>, Josh Boyer <jwboyer@redhat.com>,
Sean Paul <seanpaul@chromium.org>,
Inki Dae <inki.dae@samsung.com>, Dave Airlie <airlied@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
Lucas Stach <l.stach@pengutronix.de>,
Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>,
Yakir Yang <ykk@rock-chips.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
devel@driverdev.osuosl.org,
"open list:OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Xu Jianqun <jay.xu@rock-chips.com>, Pawel Moll <pawel.moll@arm.>
Subject: Re: [PATCH v18 12/12] drm: bridge/dw_hdmi: add rockchip rk3288 support
Date: Thu, 11 Dec 2014 12:24:15 +0100 [thread overview]
Message-ID: <6479148.dVz0vTNYfK@phil> (raw)
In-Reply-To: <CAGS+omA1Gf8yqrd4Bu=Pm1OBdsJBHg0gt+TP_6vi88Zz+O3jHA@mail.gmail.com>
Hi Daniel,
Am Mittwoch, 10. Dezember 2014, 20:36:17 schrieb Daniel Kurtz:
> This driver adds HDMI to rockchip/drm. The fact that rockchip's hdmi
> uses dw_hdmi is an implementation detail. I do not think that the names
> used for rk3288-hdmi should include "dw" in them.
>
> See inline for what I mean...
I guess in general this is more a matter of preference.
Past practices suggest that having the dw in the name is a sane solution too,
like in dw_mmc-foo (mmc/host), dwmac-foo (net/ethernet/stmicro/stmmac).
And personally I'd keep to this already established naming scheme ... i.e. not
hiding the dw heritage.
And also it looks like other involved parties like Philipp and Russell seemed
to be ok with the naming through the revisions till now.
[...]
> > +static enum drm_mode_status
> > +dw_hdmi_rockchip_mode_valid(struct drm_connector *connector,
>
> Similarly, I would rename these function names to start with
> rockchip_hdmi (or maybe rk_hdmi for brevity).
> Especially the ones for the module & driver: (bind/unbind/probe/remove).
Please keep to one rk <-> rockchip style at least per subsystem. The core drm
driver uses rockchip, so the hdmi driver should too (instead of rk).
Heiko
next prev parent reply other threads:[~2014-12-11 11:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 6:22 [PATCH v18 0/12] dw-hdmi: convert imx hdmi to bridge/dw_hdmi Andy Yan
2014-12-05 6:23 ` [PATCH v18 01/12] drm: imx: imx-hdmi: make checkpatch happy Andy Yan
2014-12-05 6:24 ` [PATCH v18 02/12] drm: imx: imx-hdmi: return defer if can't get ddc i2c adapter Andy Yan
2014-12-05 6:25 ` [PATCH v18 03/12] drm: imx: imx-hdmi: convert imx-hdmi to drm_bridge mode Andy Yan
2015-01-06 11:52 ` [PATCH v18.1 " Heiko Stübner
2015-01-06 13:42 ` Russell King - ARM Linux
2014-12-05 6:25 ` [PATCH v18 04/12] drm: imx: imx-hdmi: split phy configuration to platform driver Andy Yan
[not found] ` <1417760750-17047-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-01-06 13:44 ` Russell King - ARM Linux
2014-12-05 6:26 ` [PATCH v18 05/12] drm: imx: imx-hdmi: move imx-hdmi to bridge/dw_hdmi Andy Yan
2014-12-05 6:27 ` [PATCH v18 06/12] dt-bindings: add document for dw_hdmi Andy Yan
2014-12-05 13:54 ` Philipp Zabel
2014-12-08 6:10 ` Andy Yan
2014-12-05 6:28 ` [PATCH v18 07/12] drm: bridge/dw_hdmi: add support for multi-byte register width access Andy Yan
2014-12-05 6:30 ` [PATCH v18 08/12] drm: bridge/dw_hdmi: add mode_valid support Andy Yan
2014-12-05 6:31 ` [PATCH v18 09/12] drm: bridge/dw_hdmi: clear i2cmphy_stat0 reg in hdmi_phy_wait_i2c_done Andy Yan
2014-12-05 6:31 ` [PATCH v18 10/12] drm: bridge/dw_hdmi: add function dw_hdmi_phy_enable_spare Andy Yan
2014-12-05 6:33 ` [PATCH v18 11/12] dt-bindings: Add documentation for rockchip dw hdmi Andy Yan
2014-12-05 6:34 ` [PATCH v18 12/12] drm: bridge/dw_hdmi: add rockchip rk3288 support Andy Yan
[not found] ` <1417761259-17429-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-12-11 4:36 ` Daniel Kurtz
2014-12-11 11:24 ` Heiko Stübner [this message]
2015-01-06 13:51 ` Russell King - ARM Linux
2015-01-07 7:48 ` Andy Yan
2014-12-05 13:55 ` [PATCH v18 0/12] dw-hdmi: convert imx hdmi to bridge/dw_hdmi Philipp Zabel
2014-12-05 16:31 ` Andy Yan
2015-01-06 11:49 ` Heiko Stübner
2015-01-06 15:27 ` Philipp Zabel
2015-01-07 2:39 ` Liu Ying
2015-01-07 7:17 ` Andy Yan
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=6479148.dVz0vTNYfK@phil \
--to=heiko@sntech.de \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=andy.yan@rock-chips.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@freescale.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=inki.dae@samsung.com \
--cc=jay.xu@rock-chips.com \
--cc=jwboyer@redhat.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm. \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robh+dt@kernel.org \
--cc=seanpaul@chromium.org \
--cc=shawn.guo@linaro.org \
--cc=ykk@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;
as well as URLs for NNTP newsgroup(s).