From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "Anton.Glukhov" <anton.a.glukhov@gmail.com>, hs@denx.de
Cc: linux-kernel@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
"Anant Gole" <anantgole@ti.com>,
devicetree@vger.kernel.org, netdev@vger.kernel.org,
linux-can@vger.kernel.org, "Tony Lindgren" <tony@atomide.com>,
"Wolfgang Grandegger" <wg@grandegger.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] net, can, ti_hecc: add DT support for the ti,hecc controller
Date: Tue, 20 Oct 2015 17:18:45 +0200 [thread overview]
Message-ID: <56265B55.2070203@pengutronix.de> (raw)
In-Reply-To: <56265947.8050008@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
On 10/20/2015 05:09 PM, Anton.Glukhov wrote:
>>> It's OMAP3 based arch, but HECC is implemented only in AM3505 and AM3517 SoCs.
>>> So, I'm confused about what's "name" should I use.
>>
>> Which SoC was available first? Pick that.
> What do you mean available? I know only that HECC appear in AM3505 and AM3517. Nowhere else.
Available on the market. Which one was produced first or was soldered
first to some PCB?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2015-10-20 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 6:39 [PATCH] net, can, ti_hecc: add DT support for the ti,hecc controller Heiko Schocher
2015-10-19 6:58 ` Marc Kleine-Budde
2015-10-19 7:27 ` Heiko Schocher
2015-10-19 7:31 ` Marc Kleine-Budde
2015-10-20 14:57 ` Anton.Glukhov
2015-10-20 15:05 ` Marc Kleine-Budde
2015-10-20 15:09 ` Anton.Glukhov
2015-10-20 15:18 ` Marc Kleine-Budde [this message]
2015-10-20 15:20 ` Marc Kleine-Budde
[not found] ` <56265BC4.8080403-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-10-20 15:38 ` Anton.Glukhov
2015-10-22 1:30 ` Rob Herring
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=56265B55.2070203@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anantgole@ti.com \
--cc=anton.a.glukhov@gmail.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=hs@denx.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tony@atomide.com \
--cc=wg@grandegger.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).