From: Milo Kim <woogyom.kim@gmail.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] ARM: dts: imx6: Add Savageboard common file
Date: Mon, 2 Jan 2017 16:49:16 +0900 [thread overview]
Message-ID: <2de3ba17-91d7-65c2-9a8e-897a8b96d8d8@gmail.com> (raw)
In-Reply-To: <20170102074422.GH20956@dragon>
On 01/02/2017 04:44 PM, Shawn Guo wrote:
> On Mon, Jan 02, 2017 at 04:31:07PM +0900, Milo Kim wrote:
>>
>> On 01/02/2017 03:52 PM, Shawn Guo wrote:
>>>> + panel {
>>>> + compatible = "avic, tm097tdh02", "hannstar,hsd100pxn1";
>>> "avic, tm097tdh02" is an undocumented compatible.
>>>
>>
>> AVIC TM097TDH02 panel is compatible with Hannstar HSD100PXN1, so I
>> reuse it. It's the same rule as the usage of imx6q I2C controller.
>>
>> i2c2: i2c@021a4000 {
>> compatible = "fsl,imx6q-i2c", "fsl,imx21-i2c";
>> };
>
> Forgot to ask, is the "avic" Shanghai AVIC Optoelectronics Co., Ltd. as
> documented in vendor-prefixes.txt?
Yes, right.
Best regards,
Milo
next prev parent reply other threads:[~2017-01-02 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 1:04 [PATCH v3 0/3] ARM: dts: imx6: Support Poslab Savageboard dual & quad Milo Kim
2016-12-09 1:04 ` [PATCH v3 1/3] ARM: dts: imx6: Add Savageboard common file Milo Kim
2016-12-26 16:26 ` Fabio Estevam
2017-01-02 6:52 ` Shawn Guo
2017-01-02 7:31 ` Milo Kim
2017-01-02 7:41 ` Shawn Guo
2017-01-02 7:45 ` Milo Kim
2017-01-02 7:44 ` Shawn Guo
2017-01-02 7:49 ` Milo Kim [this message]
2016-12-09 1:04 ` [PATCH v3 2/3] ARM: dts: imx6: Support Savageboard dual Milo Kim
2016-12-26 16:27 ` Fabio Estevam
2017-01-02 7:03 ` Shawn Guo
2017-01-02 7:32 ` Milo Kim
2016-12-09 1:04 ` [PATCH v3 3/3] ARM: dts: imx6: Support Savageboard quad Milo Kim
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=2de3ba17-91d7-65c2-9a8e-897a8b96d8d8@gmail.com \
--to=woogyom.kim@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@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).