From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: devicetree@vger.kernel.org, Jason Kridner <jkridner@gmail.com>,
Neeraj Dantu <dantuguf14105@gmail.com>,
Neeraj Dantu <neeraj.dantu@octavosystems.com>,
linux-omap@vger.kernel.org,
Robert Nelson <robertcnelson@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] Add DT support for Octavo Systems OSD3358-SM-RED based on TI AM335x
Date: Thu, 12 Jul 2018 08:53:25 +0100 [thread overview]
Message-ID: <20180712075325.GH6920@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20180712053155.GP99251@atomide.com>
On Wed, Jul 11, 2018 at 10:31:55PM -0700, Tony Lindgren wrote:
> Hi,
>
> * Neeraj Dantu <dantuguf14105@gmail.com> [180711 15:13]:
> > OSD3358-SM-RED is a dev board for OSD335x System-in-Package(SiP) devices from
> > Octavo Systems.
> ...
> > - Fix HDMI encoder node name
>
> I think you got this the wrong way around :) See below.
>
> > +&i2c0 {
> > + hdmiencoder: tda19988 {
> > + compatible = "nxp,tda998x";
>
> tda19988: hdmiencoder {
> ...
> };
>
> So the generic type for the node. Please check the
> other devices for that too.
In the binding doc, we use "hdmi-encoder" for the node name.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 13.8Mbps down 630kbps up
According to speedtest.net: 13Mbps down 490kbps up
WARNING: multiple messages have this Message-ID (diff)
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] Add DT support for Octavo Systems OSD3358-SM-RED based on TI AM335x
Date: Thu, 12 Jul 2018 08:53:25 +0100 [thread overview]
Message-ID: <20180712075325.GH6920@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20180712053155.GP99251@atomide.com>
On Wed, Jul 11, 2018 at 10:31:55PM -0700, Tony Lindgren wrote:
> Hi,
>
> * Neeraj Dantu <dantuguf14105@gmail.com> [180711 15:13]:
> > OSD3358-SM-RED is a dev board for OSD335x System-in-Package(SiP) devices from
> > Octavo Systems.
> ...
> > - Fix HDMI encoder node name
>
> I think you got this the wrong way around :) See below.
>
> > +&i2c0 {
> > + hdmiencoder: tda19988 {
> > + compatible = "nxp,tda998x";
>
> tda19988: hdmiencoder {
> ...
> };
>
> So the generic type for the node. Please check the
> other devices for that too.
In the binding doc, we use "hdmi-encoder" for the node name.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 13.8Mbps down 630kbps up
According to speedtest.net: 13Mbps down 490kbps up
next prev parent reply other threads:[~2018-07-12 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 14:58 [PATCH v3] Add DT support for Octavo Systems OSD3358-SM-RED based on TI AM335x Neeraj Dantu
2018-07-11 14:58 ` Neeraj Dantu
2018-07-12 5:31 ` Tony Lindgren
2018-07-12 5:31 ` Tony Lindgren
2018-07-12 7:53 ` Russell King - ARM Linux [this message]
2018-07-12 7:53 ` Russell King - ARM Linux
2018-07-12 8:01 ` Russell King - ARM Linux
2018-07-12 8:01 ` Russell King - ARM Linux
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=20180712075325.GH6920@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=dantuguf14105@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jkridner@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=neeraj.dantu@octavosystems.com \
--cc=robertcnelson@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.