devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jorge Ventura <jorge.araujo.ventura-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Question about device tree and modalias
Date: Tue, 15 Oct 2013 09:35:55 -0500	[thread overview]
Message-ID: <20131015143544.GA32767@gmail.com> (raw)

I am beginning to study device tree and I have a question.
There is a drive available for the device enc28j60, an ethernet chip with spi interface. The drive has modalias "spi:enc28j60" what is used by the old linux device module to match with the plataform modalias.

I am including in the device tree:

    fragment@1 {
        target = <&spi1>;
        __overlay__ {

             #address-cells = <1>;
             #size-cells = <0>;
             status = "okay";
             pinctrl-names = "default";
             pinctrl-0 = <&spi1_pins_s0>;
             ti,pindir-d0-out-d1-in = <1>;

             spidev@1 {
                 spi-max-frequency = <24000000>;
                 reg = <0>;
                 compatible = "linux,spidev";

                 ethernet: enc28j60@0 {
                        compatible = "microchip,enc28j60";
                 };
             };
        };
    };

but the result for modalias is "platform:enc28j60@0.10" what doesn't match with "spi:enc28j60".

Someone can explain or point some tutorials to describe the correct way to migrate one drive to device tree model?

Sincerely,
Ventura
--
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

                 reply	other threads:[~2013-10-15 14:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131015143544.GA32767@gmail.com \
    --to=jorge.araujo.ventura-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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).