devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: "Caleb Robey" <c-robey@ti.com>,
	linux-omap@vger.kernel.org, "Jason Kridner" <jkridner@gmail.com>,
	"Lokesh Vutla" <lokeshvutla@ti.com>, "Jason Kridner" <jdk@ti.com>,
	"Faiz Abbas" <faiz_abbas@ti.com>,
	"Andreas Dannenberg" <dannenberg@ti.com>,
	"Jean-Jacques Hiblot" <jjhiblot@ti.com>,
	"Praneeth Bajjuri" <praneeth@ti.com>,
	"Andrew F . Davis" <afd@ti.com>, "Tom Rini" <trini@konsulko.com>,
	"Robert Nelson" <robertcnelson@gmail.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: am5729: beaglebone-ai: adding device tree
Date: Thu, 12 Dec 2019 09:04:52 -0800	[thread overview]
Message-ID: <20191212170452.GV35479@atomide.com> (raw)
In-Reply-To: <41c73bc1-99ae-6797-5bb7-7acc0f6518c0@ti.com>

* Grygorii Strashko <grygorii.strashko@ti.com> [191121 11:08]:
> 
> 
> On 21/11/2019 00:05, Caleb Robey wrote:
> > From: Jason Kridner <jdk@ti.com>
> > 
> > BeagleBoard.org BeagleBone AI is an open source hardware single
> > board computer based on the Texas Instruments AM5729 SoC featuring
> > dual-core 1.5GHz Arm Cortex-A15 processor, dual-core C66 digital
> > signal processor (DSP), quad-core embedded vision engine (EVE),
> > Arm Cortex-M4 processors, dual programmable realtime unit
> > industrial control subsystems and more. The board features 1GB
> > DDR3L, USB3.0 Type-C, USB HS Type-A, microHDMI, 16GB eMMC flash,
> > 1G Ethernet, 802.11ac 2/5GHz, Bluetooth, and BeagleBone expansion
> > headers.
> > 
> > For more information, refer to:
> > https://beaglebone.ai
> > 
> > This patch introduces the BeagleBone AI device tree.
> > 
> > Note that the device use the "ti,tpd12s016" component which is
> > software compatible with "ti,tpd12s015". Thus we only use the
> > latter driver.
> 
> Ah. thanks. I see my comments resolved here.
> no more comments to net part from my side.

Just FYI, Jason had one pending comment on the earlier version
about the compatible property to use.

So I'm assuming there will be a new version posted, tagging
this one as read.

Regards,

Tony

  reply	other threads:[~2019-12-12 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 22:05 [PATCH v2] ARM: dts: am5729: beaglebone-ai: adding device tree Caleb Robey
2019-11-21 11:07 ` Grygorii Strashko
2019-12-12 17:04   ` Tony Lindgren [this message]
2020-03-31 18:38     ` Drew Fustini
2020-03-31 18:46       ` Tony Lindgren
2020-03-31 20:30         ` Drew Fustini

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=20191212170452.GV35479@atomide.com \
    --to=tony@atomide.com \
    --cc=afd@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=c-robey@ti.com \
    --cc=dannenberg@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=faiz_abbas@ti.com \
    --cc=grygorii.strashko@ti.com \
    --cc=jdk@ti.com \
    --cc=jjhiblot@ti.com \
    --cc=jkridner@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=mark.rutland@arm.com \
    --cc=praneeth@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=trini@konsulko.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).