linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] net: flexcan: add transceiver switch gpios support
Date: Thu, 28 Jun 2012 13:29:19 +0200	[thread overview]
Message-ID: <4FEC400F.8010506@pengutronix.de> (raw)
In-Reply-To: <20120628112111.GC22990@S2101-09.ap.freescale.net>

On 06/28/2012 01:21 PM, Shawn Guo wrote:
> On Thu, Jun 28, 2012 at 12:31:56PM +0200, Marc Kleine-Budde wrote:
>> Hmm I'm wondering if transceiver or phy is the correct name here. In
>> platform_data it's called transceiver_switch.
> 
> The transceiver_switch in platform_data names a function, while we are
> naming a couple gpios which happen to be access in that function.  It
> looks all correct to me.

I mean which name is more precise, do these gpio enable/standy a "phy"
or a "transceiver". For example:
http://www.nxp.com/documents/application_note/AN00094.pdf, this document
says: TJA1041/1041A high speed CAN transceiver.

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   |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120628/75c661b1/attachment.sig>

  reply	other threads:[~2012-06-28 11:29 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  3:21 [PATCH v2 0/2] flexcan driver updates Shawn Guo
2012-06-28  3:21 ` [PATCH v2 1/2] net: flexcan: clock-frequency is optional for device tree probe Shawn Guo
2012-06-28 11:23   ` Dong Aisheng
2012-06-28  3:21 ` [PATCH v2 2/2] net: flexcan: add transceiver switch gpios support Shawn Guo
2012-06-28  5:22   ` Lothar Waßmann
2012-06-28  5:30     ` Shawn Guo
2012-06-28  6:14   ` Hui Wang
2012-06-28  6:34     ` Shawn Guo
2012-06-28  7:01       ` Hui Wang
2012-06-28 10:32         ` Marc Kleine-Budde
2012-06-28 10:31   ` Marc Kleine-Budde
2012-06-28 11:21     ` Shawn Guo
2012-06-28 11:29       ` Marc Kleine-Budde [this message]
2012-06-28 11:41         ` Shawn Guo
2012-06-28 11:52           ` Shawn Guo
2012-06-28 12:05             ` Shawn Guo
2012-06-28 12:11               ` Dong Aisheng
2012-06-28 12:19             ` Lothar Waßmann
2012-06-28 12:07           ` Lothar Waßmann
2012-06-28 12:13             ` Shawn Guo
2012-06-28 12:24               ` Lothar Waßmann
2012-07-02  2:55                 ` Hui Wang
2012-06-28 12:08           ` Kurt Van Dijck
2012-06-28 12:10             ` Marc Kleine-Budde
2012-06-28 12:16             ` Shawn Guo
2012-06-28 11:39     ` Dong Aisheng
2012-06-28 11:33   ` Dong Aisheng
2012-06-28 11:46     ` Shawn Guo
2012-06-28 11:48       ` Dong Aisheng
2012-06-28 12:00         ` Shawn Guo
2012-06-28 12:02         ` Dong Aisheng
2012-06-28 12:19           ` Shawn Guo
2012-06-28 12:05       ` Marc Kleine-Budde
2012-06-28 12:18         ` Dong Aisheng
2012-06-28 12:32           ` Lothar Waßmann
2012-06-28 12:40             ` Shawn Guo
2012-06-28 12:47             ` Dong Aisheng
2012-06-28 12:39           ` Shawn Guo
2012-06-29  9:27           ` Marc Kleine-Budde

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=4FEC400F.8010506@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).