From: Nishanth Menon <nm@ti.com>
To: Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: omap3505: HECC support and DT ?
Date: Thu, 11 Dec 2014 10:04:07 -0600 [thread overview]
Message-ID: <5489C077.6070806@ti.com> (raw)
In-Reply-To: <CAL8zT=izk+xk=v0M0F5DSgSySaGvkPWWZdCd43i8Z6bwQt7MAg@mail.gmail.com>
On 12/11/2014 08:44 AM, Jean-Michel Hautbois wrote:
> Hi !
>
> I have a custom board with a AM3505.
> I am trying to use linux 3.18 and I have difficulties making it work.
> What is needed in order to get it declared in DT ?
usually look at examples of an board file closely resembling the one
that you are working on and look at the commit that introduced it..
usually just Makefile and dts is needed.
> Is it still needed to have a board-am3517-myboard.c ?
ideally not. even for devices that are yet to be "dtfied" they
platform data goes to arch/arm/mach-omap2/pdata-quirks.c
See arch/arm/boot/dts/am3517-craneboard.dts as an example.
>
> I have a few drivers like that I need to bring up (a Micrel KSZ8873
> for example) where the drivers exist, but a DT binding seems to be
> missing.
without checking the status of micrel driver in question, generically
speaking: not all drivers in linux kernel have been converted to
device tree. if your board uses one such driver, it is usually
strongly recommended to convert such a driver to DT and then integrate.
> But I may have missed the information, hence my question :).
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: omap3505: HECC support and DT ?
Date: Thu, 11 Dec 2014 10:04:07 -0600 [thread overview]
Message-ID: <5489C077.6070806@ti.com> (raw)
In-Reply-To: <CAL8zT=izk+xk=v0M0F5DSgSySaGvkPWWZdCd43i8Z6bwQt7MAg@mail.gmail.com>
On 12/11/2014 08:44 AM, Jean-Michel Hautbois wrote:
> Hi !
>
> I have a custom board with a AM3505.
> I am trying to use linux 3.18 and I have difficulties making it work.
> What is needed in order to get it declared in DT ?
usually look at examples of an board file closely resembling the one
that you are working on and look at the commit that introduced it..
usually just Makefile and dts is needed.
> Is it still needed to have a board-am3517-myboard.c ?
ideally not. even for devices that are yet to be "dtfied" they
platform data goes to arch/arm/mach-omap2/pdata-quirks.c
See arch/arm/boot/dts/am3517-craneboard.dts as an example.
>
> I have a few drivers like that I need to bring up (a Micrel KSZ8873
> for example) where the drivers exist, but a DT binding seems to be
> missing.
without checking the status of micrel driver in question, generically
speaking: not all drivers in linux kernel have been converted to
device tree. if your board uses one such driver, it is usually
strongly recommended to convert such a driver to DT and then integrate.
> But I may have missed the information, hence my question :).
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-12-11 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 14:44 omap3505: HECC support and DT ? Jean-Michel Hautbois
2014-12-11 14:44 ` Jean-Michel Hautbois
2014-12-11 16:04 ` Nishanth Menon [this message]
2014-12-11 16:04 ` Nishanth Menon
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=5489C077.6070806@ti.com \
--to=nm@ti.com \
--cc=jean-michel.hautbois@vodalys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 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.