Re: [PATCH v2 0/3] Adding DT support for TI HECC module
From: Tony Lindgren <hidden>
Date: 2017-01-12 15:44:23
Also in:
linux-can, linux-omap
Possibly related (same subject, not in this thread)
- 2017-01-16 · Re: [PATCH v2 0/3] Adding DT support for TI HECC module · Tony Lindgren <tony@atomide.com>
- 2017-01-16 · Re: [PATCH v2 0/3] Adding DT support for TI HECC module · Yegor Yefremov <hidden>
- 2017-01-12 · Re: [PATCH v2 0/3] Adding DT support for TI HECC module · Tony Lindgren <hidden>
- 2017-01-12 · Re: [PATCH v2 0/3] Adding DT support for TI HECC module · Yegor Yefremov <hidden>
- 2017-01-12 · Re: [PATCH v2 0/3] Adding DT support for TI HECC module · Yegor Yefremov <hidden>
* Yegor Yefremov [off-list ref] [170112 07:33]:
On Thu, Jan 12, 2017 at 8:59 AM, Yegor Yefremov [off-list ref] wrote:quoted
On Thu, Jan 12, 2017 at 1:47 AM, Tony Lindgren [off-list ref] wrote:quoted
* Yegor Yefremov [off-list ref] [170111 13:52]:quoted
On Wed, Jan 11, 2017 at 3:05 PM, [off-list ref] wrote:quoted
From: Yegor Yefremov <yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> This is an attempt to revive DT support for TI HECC that was started in 2015. I haven't changed much because not all questions could be fully answered: * Should HECC use "am3505" as compatible?I mean "ti,am3505-hecc"Yeah it should use the device name for the driver.I've looked at drivers/net/ethernet/ti/davinci_emac.c and there "ti,am3517-emac" will be used. Should we stick to am3517? am3505 won't be used in any dts[i] file.
If they are the same, then usually the earliest hardware naming can be used for later versions too. I don't know which was first am3517 or 3505. If you think "ti,am3517-hecc" makes sense I'm fine with that. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html