From: Alexander Aring <alex.aring@gmail.com>
To: Simon Vincent <simon.vincent@xsilon.com>
Cc: Alan Ott <alan@signal11.us>, Walter Mack <wmack@componentsw.com>,
linux-wpan@vger.kernel.org
Subject: Re: [PATCH wpan-next] ieee802154: mrf24j40: support for external rx/tx
Date: Tue, 23 Sep 2014 10:06:12 +0200 [thread overview]
Message-ID: <20140923080610.GB11396@omega> (raw)
In-Reply-To: <5421280E.2060203@xsilon.com>
On Tue, Sep 23, 2014 at 08:58:06AM +0100, Simon Vincent wrote:
> I was under the impression the patch had been signed off. Maybe I missed a
> mail...
mhh, I didn't see any signed-off or acked-by from alan. Maybe just cc
linux-wpan or me there.
> I can confirm the mrf24j40 works just fine using a DT.
>
Yes basically this works, because dt have some out of the box feature to
load devices at boottime by modulename.
Normally you have some compatible names for your device like:
static const struct of_device_id at86rf230_of_match[] = {
{ .compatible = "atmel,at86rf230", },
{ .compatible = "atmel,at86rf231", },
{ .compatible = "atmel,at86rf233", },
{ .compatible = "atmel,at86rf212", },
{ },
};
MODULE_DEVICE_TABLE(of, at86rf230_of_match);
the mrf24j40 works for dt and has no platform data or something else.
But it's different than make the driver dt-enabled. It's only working
because DT allows to load modules by modulenames.
- Alex
next prev parent reply other threads:[~2014-09-23 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 5:35 [PATCH wpan-next] ieee802154: mrf24j40: support for external rx/tx Walter Mack
2014-09-16 7:01 ` Alexander Aring
2014-09-16 20:13 ` Walter Mack
2014-09-16 20:20 ` Alexander Aring
2014-09-23 3:51 ` Alan Ott
2014-09-23 7:19 ` Alexander Aring
2014-09-23 7:58 ` Simon Vincent
2014-09-23 8:06 ` Alexander Aring [this message]
2014-09-24 6:11 ` Walter Mack
2014-09-24 6:35 ` Alexander Aring
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=20140923080610.GB11396@omega \
--to=alex.aring@gmail.com \
--cc=alan@signal11.us \
--cc=linux-wpan@vger.kernel.org \
--cc=simon.vincent@xsilon.com \
--cc=wmack@componentsw.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