devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yakir Yang <ykk@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Zheng Yang <zhengyang@rock-chips.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Ken Mixte <kmixter@google.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-rockchip@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	Kumar Gala <galak@codeaurora.org>,
	Thierry Reding <treding@nvidia.com>,
	linux-arm-kernel@lists.infradead.org,
	Ben Chan <benchan@google.com>
Subject: Re: [RFC PATCH v1 2/2] dt-bindings: add document for Innosilicon HDMI on Rockchip platform
Date: Mon, 23 Nov 2015 09:26:04 +0800	[thread overview]
Message-ID: <56526B2C.8030202@rock-chips.com> (raw)
In-Reply-To: <1776316.RzHCH7Zejb@phil>

Hi Heiko,

On 11/22/2015 04:14 AM, Heiko Stuebner wrote:
> Hi Yakir,
>
> Am Mittwoch, 11. November 2015, 15:47:32 schrieb Yakir Yang:
>> Signed-off-by: Yakir Yang <ykk@rock-chips.com>
>> ---
>>   .../display/rockchip/inno_hdmi-rockchip.txt        | 50 ++++++++++++++++++++++
>>   1 file changed, 50 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/display/rockchip/inno_hdmi-rockchip.txt
>>
>> diff --git a/Documentation/devicetree/bindings/display/rockchip/inno_hdmi-rockchip.txt b/Documentation/devicetree/bindings/display/rockchip/inno_hdmi-rockchip.txt
>> new file mode 100644
>> index 0000000..1898408
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/display/rockchip/inno_hdmi-rockchip.txt
>> @@ -0,0 +1,50 @@
>> +Rockchip specific extensions to the Innosilicon HDMI
>> +================================
>> +
>> +Required properties:
>> +- compatible:
>> +	"rockchip,rk3036-dw-hdmi";
> should be "rockchip,rk3036-inno-hdmi"; instead I guess

Right, thanks

- Yakir

>
> Heiko
>
>
>


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-11-23  1:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11  7:45 [RFC PATCH v1 0/2] Introduce Innosilicon HDMI driver on Rockchip platforms Yakir Yang
2015-11-11  7:46 ` [RFC PATCH v1 1/2] drm: rockchip/hdmi: add Innosilicon HDMI support Yakir Yang
2015-12-21  7:31   ` Mark yao
2015-12-21  7:44     ` Yakir Yang
2015-11-11  7:47 ` [RFC PATCH v1 2/2] dt-bindings: add document for Innosilicon HDMI on Rockchip platform Yakir Yang
2015-11-11 20:22   ` Rob Herring
2015-11-12  1:07     ` Yakir Yang
2015-11-21 20:14   ` Heiko Stuebner
2015-11-23  1:26     ` Yakir Yang [this message]
2015-12-21  7:25 ` [RFC PATCH v1 0/2] Introduce Innosilicon HDMI driver on Rockchip platforms Mark yao
2015-12-21  7:44   ` Yakir Yang

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=56526B2C.8030202@rock-chips.com \
    --to=ykk@rock-chips.com \
    --cc=benchan@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=galak@codeaurora.org \
    --cc=heiko@sntech.de \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kmixter@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=treding@nvidia.com \
    --cc=zhengyang@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).