From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>,
Eric Miao <eric.y.miao@gmail.com>,
netdev@vger.kernel.org, linux-can@vger.kernel.org,
Wolfgang Grandegger <wg@grandegger.com>,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND] can: mcp251x: Replace power callbacks with regulator API
Date: Sat, 17 Aug 2013 21:59:10 +0200 [thread overview]
Message-ID: <520FD60E.4040709@pengutronix.de> (raw)
In-Reply-To: <20130817083014.a01144051b158c34ec7dd9d9@mail.ru>
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
On 08/17/2013 06:30 AM, Alexander Shiyan wrote:
[...]
>> Since DT conversion isn't finished, I still accept the board files.
>> But this patch should be split into two parts. One is for pxa, and the
>> other one is for net.
>
> Patch cannot be splitted because this can create hole which break git-bisect.
>
> In any case, I want to create a v2 with a more detailed description, and I
> have a supplementary question for the CAN subsystem maintainers.
> "Transciever power" is not used by any of the boards, can we remove it
> completely? This will greatly simplify driver.
Do you mean the former transceiver_enable() callback?
> struct mcp251x_platform_data {
> unsigned long oscillator_frequency;
> unsigned long irq_flags;
> - int (*board_specific_setup)(struct spi_device *spi);
> - int (*transceiver_enable)(int enable);
> - int (*power_enable) (int enable);
> };
Having a switchable transceiver is a quite common thing. So I'd like
that you keep it. The flexcan driver was just converted from a callback
to a regulator too. It already has device tree bindings and I'd like to
use these bindings as a standard for new drivers. From flexcan's dt
bindings:
> - xceiver-supply: Regulator that powers the CAN transceiver
which translates into:
> priv->reg_xceiver = devm_regulator_get(&pdev->dev, "xceiver");
Can you please use "xceiver" instead of "transceiver", so that future DT
binding will fit the scheme.
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: 259 bytes --]
next prev parent reply other threads:[~2013-08-17 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 12:00 [PATCH RESEND] can: mcp251x: Replace power callbacks with regulator API Alexander Shiyan
2013-08-09 7:37 ` Marc Kleine-Budde
2013-08-17 2:03 ` Haojian Zhuang
2013-08-17 2:19 ` Haojian Zhuang
2013-08-17 4:30 ` Alexander Shiyan
2013-08-17 4:37 ` Haojian Zhuang
2013-08-20 8:46 ` Marc Kleine-Budde
2013-08-21 0:46 ` Haojian Zhuang
2013-08-17 19:59 ` Marc Kleine-Budde [this message]
2013-08-17 21:10 ` Alexander Shiyan
2013-08-18 8:00 ` 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=520FD60E.4040709@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=shc_work@mail.ru \
--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).