From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: where and when the kernel destroy devices memory if there were no matched driver for it?
Date: Wed, 27 Jun 2018 20:06:58 +0800 [thread overview]
Message-ID: <20180627120658.GA23418@kroah.com> (raw)
In-Reply-To: <1d14c59c-a67d-b948-c926-2acd01101089@163.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Jun 27, 2018 at 04:57:56PM +0800, kipade wrote:
> If so, I make a driver was compiled as module and inserted by insmod
> after some time the system booted, the driver could find the device if it
> did not compiled as module. But, the fact is, my driver could not find
> its device which was created during booting from device tree.
I don't know, sorry, you are going to have to be a lot more specific.
Do you see the device in /sys/devices/ ? If so, are you sure your
driver probe function is called? If not, then work on fixing that.
Do you have a pointer to your driver code anywhere we can review it to
see what you are trying to do?
thanks,
greg k-h
next prev parent reply other threads:[~2018-06-27 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 14:14 clk: timestamps Subhashini Rao Beerisetty
2018-06-27 5:52 ` where and when the kernel destroy devices memory if there were no matched driver for it? kipade
2018-06-27 5:57 ` Greg KH
2018-06-27 8:57 ` kipade
2018-06-27 12:06 ` Greg KH [this message]
2018-06-27 7:47 ` clk: timestamps Yann Droneaud
2018-06-27 8:42 ` Subhashini Rao Beerisetty
2018-06-27 20:50 ` valdis.kletnieks at vt.edu
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=20180627120658.GA23418@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).