From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: shawn.guo@linaro.org, linux-can@vger.kernel.org,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH 2/3] flexcan: Use a regulator to control the CAN transceiver
Date: Wed, 12 Jun 2013 11:40:52 +0200 [thread overview]
Message-ID: <51B84224.2040807@pengutronix.de> (raw)
In-Reply-To: <1370916778-4406-2-git-send-email-festevam@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
On 06/11/2013 04:12 AM, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Instead of using a GPIO to turn on/off the CAN transceiver, it is better to
> use a regulator as some systems may use a PMIC to power the CAN transceiver.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> Marc/Shawn,
>
> Only boot tested. I haven't tested CAN operation.
Can you test on real hardware? I don't have access to an evk until Monday.
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: 263 bytes --]
next prev parent reply other threads:[~2013-06-12 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 2:12 [PATCH 1/3] ARM: imx: prepare for removal of flexcan_platform_data Fabio Estevam
2013-06-11 2:12 ` [PATCH 2/3] flexcan: Use a regulator to control the CAN transceiver Fabio Estevam
2013-06-12 9:40 ` Marc Kleine-Budde [this message]
2013-06-14 3:55 ` Fabio Estevam
2013-06-11 2:12 ` [PATCH 3/3] flexcan: Remove platform file Fabio Estevam
2013-06-12 9:41 ` [PATCH 1/3] ARM: imx: prepare for removal of flexcan_platform_data 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=51B84224.2040807@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=shawn.guo@linaro.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).