linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Nishanth Menon <nm@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1
Date: Fri, 2 Sep 2016 14:48:52 +0300	[thread overview]
Message-ID: <f4cff876-4457-4548-31ad-3bbe43607f72@ti.com> (raw)
In-Reply-To: <d3df6f32-1294-17bc-8b5f-236d14a349a0@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 1331 bytes --]



On 02/09/16 13:01, Nishanth Menon wrote:
> On 09/02/2016 04:58 AM, Tomi Valkeinen wrote:
>> On 02/09/16 12:06, Nishanth Menon wrote:
>>
>>> diff --git a/arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts
>>> b/arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts
>>> new file mode 100644
>>> index 000000000000..da61dbba7768
>>> --- /dev/null
>>> +++ b/arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts
>>> @@ -0,0 +1,24 @@
>>> +/*
>>> + * Copyright (C) 2014-2016 Texas Instruments Incorporated -
>>> http://www.ti.com/
>>> + *
>>> + * This program is free software; you can redistribute it and/or modify
>>> + * it under the terms of the GNU General Public License version 2 as
>>> + * published by the Free Software Foundation.
>>> + */
>>> +
>>> +#include "am57xx-beagle-x15-common.dtsi"
>>> +
>>> +/ {
>>> +    model = "TI AM5728 BeagleBoard-X15 rev B1";
>>> +};
>>> +
>>> +&tpd12s015 {
>>> +    gpios = <&gpio7 10 GPIO_ACTIVE_HIGH>,    /* gpio7_10, CT CP HPD */
>>> +        <&gpio2 30 GPIO_ACTIVE_HIGH>,    /* gpio6_30, LS OE */
>>
>> Wrong gpio in the comment.
> 
> Uggh.. thanks for catching that.. should have been gpio2_30
> 
> will repost a v2 if there are no further comments at the end of the day..

Booting and HDMI works fine:

Tested-by: Tomi Valkeinen <tomi.valkeinen@ti.com>

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-09-02 11:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02  9:05 [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon
2016-09-02  9:05 ` [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations Nishanth Menon
2016-09-02 10:18   ` Sekhar Nori
2016-09-02 14:52     ` Nishanth Menon
2016-09-02  9:06 ` [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1 Nishanth Menon
2016-09-02  9:58   ` Tomi Valkeinen
2016-09-02 10:01     ` Nishanth Menon
2016-09-02 11:48       ` Tomi Valkeinen [this message]
2016-09-02 10:41   ` Sekhar Nori
2016-09-02 11:18     ` Tomi Valkeinen
2016-09-02 13:52     ` Robert Nelson
2016-09-02 15:01       ` Nishanth Menon
2016-09-02 15:06       ` Tony Lindgren
2016-09-06 10:10       ` Sekhar Nori
2016-09-06 20:05         ` Tony Lindgren
2016-09-07  5:09           ` Sekhar Nori
2016-09-02  9:14 ` [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon

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=f4cff876-4457-4548-31ad-3bbe43607f72@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=tony@atomide.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).