All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegorslists@googlemail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	devicetree@vger.kernel.org, robh+dt@kernel.org,
	Tony Lindgren <tony@atomide.com>,
	Andrey Skvortsov <andrej.skvortzov@gmail.com>,
	hs@denx.de, Anton Glukhov <anton.a.glukhov@gmail.com>
Subject: Re: [PATCH v3 0/3] Adding DT support for TI HECC module
Date: Fri, 17 Feb 2017 10:23:33 +0100	[thread overview]
Message-ID: <CAGm1_kvN_SiFS69aKRsJ-Hm9bjgVskYiONh_bTUGLhRozrKF_A@mail.gmail.com> (raw)
In-Reply-To: <b6c8bfbe-1748-ee2c-2129-96e1bce9b324@pengutronix.de>

On Fri, Feb 17, 2017 at 9:51 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> On 02/17/2017 09:50 AM, Yegor Yefremov wrote:
>> On Fri, Feb 17, 2017 at 9:46 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>>> On 02/15/2017 03:48 PM, yegorslists@googlemail.com wrote:
>>>> From: Yegor Yefremov <yegorslists@googlemail.com>
>>>>
>>>> This is an attempt to revive DT support for TI HECC that was started in 2015 [1].
>>>>
>>>> Changes v2 -> v3:
>>>>   - rename compatible property to "ti,am3517-hecc" (though there is a stipped
>>>>     device named 3505, EMAC driver already uses am3517-emac name, so keep this
>>>>     property consistent)
>>>>   - use reg-names to specify different HECC I/O mapping (suggested by Tony Lindgren)
>>>>   - provide fallback offsets and sizes for board files
>>>
>>> Are there any board files using te_hecc intree? I don't see any on the
>>> first glance. What about making the driver DT only?
>>
>> Good idea. I aslo wanted to ask this. So this means we could
>> completely get rid of include/linux/can/platform/ti_hecc.h?
>
> If there isn't any in-tree user, thes yes.

Btw. what should we do about "@transceiver_switch: platform specific
callback fn for transceiver control"? Model it via something like
this:

enable-gpios = <&gpio6 15 GPIO_ACTIVE_HIGH>; /* gpio 175 */

Yegor

  reply	other threads:[~2017-02-17  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 14:48 [PATCH v3 0/3] Adding DT support for TI HECC module yegorslists
2017-02-15 14:48 ` [PATCH v3 1/3] ARM: dts: AM35x: Add hecc node yegorslists
2017-02-15 14:48 ` [PATCH v3 2/3] can: ti_hecc: Add TI HECC DT binding documentation yegorslists
2017-02-15 14:48 ` [PATCH v3 3/3] can: ti_hecc: Add DT support for TI HECC module yegorslists
     [not found] ` <1487170125-10815-1-git-send-email-yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-17  8:46   ` [PATCH v3 0/3] Adding " Marc Kleine-Budde
2017-02-17  8:50     ` Yegor Yefremov
     [not found]       ` <CAGm1_kuQ1skHayOKu16JdZ3Bah+=CqzZJ5e6j2VDj3WW5No2vw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-17  8:51         ` Marc Kleine-Budde
2017-02-17  9:23           ` Yegor Yefremov [this message]
2017-02-17  9:36             ` 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=CAGm1_kvN_SiFS69aKRsJ-Hm9bjgVskYiONh_bTUGLhRozrKF_A@mail.gmail.com \
    --to=yegorslists@googlemail.com \
    --cc=andrej.skvortzov@gmail.com \
    --cc=anton.a.glukhov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hs@denx.de \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.