From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Wed, 27 Jun 2018 20:06:58 +0800
Subject: where and when the kernel destroy devices memory if there were
 no matched driver for it?
In-Reply-To: <1d14c59c-a67d-b948-c926-2acd01101089@163.com>
References: <CAPY=qRS7XY5C2qTQvmkQ9785tgGPPxnZp=cfsinL8BShL3MSvQ@mail.gmail.com>
 <563a11f9-f027-73b4-fa88-f51354ce02b3@163.com>
 <20180627055711.GA16232@kroah.com>
 <1d14c59c-a67d-b948-c926-2acd01101089@163.com>
Message-ID: <20180627120658.GA23418@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

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