如何自动创建设备节点

Ⅰ LINUX设备节点

是这样的，之所以复有的制时候不需要你自己创建节点，因为有程序自动创建。
class_create和device_create，具体用法很简单，你自己查查就知道了。

还有，mknod都是在刚开始学习的时候用到，难道你以后写驱动都要手动建立设备节点吗？

Ⅱ 如何在udev自动创建设备节点

创建设备文件的方法：
第一种是使用mknod手工创建：mknod filename type major minor
第二种是自动创建设备节点：利用udev（mdev）来实现设备文件的自动创建，首先应保证支持udev（嵌入式系统用mdev），由busybox配置。
udev介绍
udev 运行在用户模式，而非内核中。udev 的初始化脚本在系统启动时创建设备节点，并且当插入新设备——加入驱动模块——在sysfs上注册新的数据后，udev会创新新的设备节点。
udev 是一个工作在用户空间的工具，它能根据系统中硬件设备的状态动态的更新设备文件，包括设备文件的创建，删除，权限等。这些文件通常都定义在/dev 目录下，但也可以在配置文件中指定。udev 必须内核中的sysfs和tmpfs支持，sysfs 为udev 提供设备入口和uevent 通道，tmpfs 为udev 设备文件提供存放空间。
注意，udev 是通过对内核产生的设备文件修改，或增加别名的方式来达到自定义设备文件的目的。但是，udev 是用户模式程序，其不会更改内核行为。也就是说，内核仍然会创建sda，sdb等设备文件，而udev可根据设备的唯一信息来区分不同的设备，并产生新的设备文件（或链接）。而在用户的应用中，只要使用新产生的设备文件

Ⅲ Android怎么生成设备节点

Android如何生成设备节点
在Android中，由于没有mdev和udev，所以它没有办法动态的生成设备节点，那么它是如何做的呢？
我们可以在system/core/init/下的init.c和devices.c中找到答案：
init.c中
int main(int argc, char **argv)
{
...
/* Get the basic filesystem setup we need put
* together in the initramdisk on / and then we'll
* let the rc file figure out the rest.
*/
mkdir("/dev", 0755);
mkdir("/proc", 0755);
mkdir("/sys", 0755);

mount("tmpfs", "/dev", "tmpfs", 0, "mode=0755");
mkdir("/dev/pts", 0755);
mkdir("/dev/socket", 0755);
mount("devpts", "/dev/pts", "devpts", 0, NULL);
mount("proc", "/proc", "proc", 0, NULL);
mount("sysfs", "/sys", "sysfs", 0, NULL);

for(;;) {
...
if (ufds[0].revents == POLLIN)
handle_device_fd(device_fd);

if (ufds[1].revents == POLLIN)
handle_property_set_fd(property_set_fd);
if (ufds[3].revents == POLLIN)
handle_keychord(keychord_fd);
}

return 0;
}

我们再来看看handle_device_fd()，该函数定义在devices.c中
void handle_device_fd(int fd)
{
...
handle_device_event(&uevent);
handle_firmware_event(&uevent);
}
}

而handle_device_event定义如下：
static void handle_device_event(struct uevent *uevent)
{
...
if(!strcmp(uevent->action, "add")) {
make_device(devpath, block, uevent->major, uevent->minor);
return;
}
...
}

make_device定义如下：
static void make_device(const char *path, int block, int major, int minor)
{
...
mode = get_device_perm(path, &uid, &gid) | (block S_IFBLK : S_IFCHR);
dev = (major $amp; ...
setegid(gid);
mknod(path, mode, dev);
chown(path, uid, -1);
setegid(AID_ROOT);
}

我们看看get_device_perm如下实现：
static mode_t get_device_perm(const char *path, unsigned *uid, unsigned *gid)
{
mode_t perm;

if (get_device_perm_inner(qemu_perms, path, uid, gid, &perm) == 0) {
return perm;
} else if (get_device_perm_inner(devperms, path, uid, gid, &perm) == 0) {
return perm;
} else {
struct listnode *node;
struct perm_node *perm_node;
struct perms_ *dp;

/* Check partners list. */
list_for_each(node, &devperms_partners) {
perm_node = node_to_item(node, struct perm_node, plist);
dp = &perm_node->dp;

if (dp->prefix) {
if (strncmp(path, dp->name, strlen(dp->name)))
continue;
} else {
if (strcmp(path, dp->name))
continue;
}
/* Found perm in partner list. */
*uid = dp->uid;
*gid = dp->gid;
return dp->perm;
}
/* Default if nothing found. */
*uid = 0;
*gid = 0;
return 0600;
}
}

我们最后可以看到在devperms中定义了要生成的设备节点：
static struct perms_ devperms[] = {
{ "/dev/null", 0666, AID_ROOT, AID_ROOT, 0 },
{ "/dev/zero", 0666, AID_ROOT, AID_ROOT, 0 },
{ "/dev/full", 0666, AID_ROOT, AID_ROOT, 0 },
{ "/dev/ptmx", 0666, AID_ROOT, AID_ROOT, 0 },
{ "/dev/tty", 0666, AID_ROOT, AID_ROOT, 0 },
{ "/dev/random", 0666, AID_ROOT, AID_ROOT, 0 },
{ "/dev/urandom", 0666, AID_ROOT, AID_ROOT, 0 },
{ "/dev/ashmem", 0666, AID_ROOT, AID_ROOT, 0 },
{ "/dev/binder", 0666, AID_ROOT, AID_ROOT, 0 },

/* logger should be world writable (for logging) but not readable */
{ "/dev/log/", 0662, AID_ROOT, AID_LOG, 1 },

/* the msm hw3d client device node is world writable/readable. */
{ "/dev/msm_hw3dc", 0666, AID_ROOT, AID_ROOT, 0 },

/* gpu driver for adreno200 is globally accessible */
{ "/dev/kgsl", 0666, AID_ROOT, AID_ROOT, 0 },

/* these should not be world writable */
{ "/dev/diag", 0660, AID_RADIO, AID_RADIO, 0 },
{ "/dev/diag_arm9", 0660, AID_RADIO, AID_RADIO, 0 },
{ "/dev/android_adb", 0660, AID_ADB, AID_ADB, 0 },
{ "/dev/android_adb_enable", 0660, AID_ADB, AID_ADB, 0 },
{ "/dev/ttyMSM0", 0600, AID_BLUETOOTH, AID_BLUETOOTH, 0 },
{ "/dev/ttyHS0", 0600, AID_BLUETOOTH, AID_BLUETOOTH, 0 },
{ "/dev/uinput", 0660, AID_SYSTEM, AID_BLUETOOTH, 0 },
{ "/dev/alarm", 0664, AID_SYSTEM, AID_RADIO, 0 },
{ "/dev/tty0", 0660, AID_ROOT, AID_SYSTEM, 0 },
{ "/dev/graphics/", 0660, AID_ROOT, AID_GRAPHICS, 1 },
{ "/dev/msm_hw3dm", 0660, AID_SYSTEM, AID_GRAPHICS, 0 },
{ "/dev/input/", 0660, AID_ROOT, AID_INPUT, 1 },
{ "/dev/eac", 0660, AID_ROOT, AID_AUDIO, 0 },
{ "/dev/cam", 0660, AID_ROOT, AID_CAMERA, 0 },
{ "/dev/pmem", 0660, AID_SYSTEM, AID_GRAPHICS, 0 },
{ "/dev/pmem_adsp", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/pmem_camera", 0660, AID_SYSTEM, AID_CAMERA, 1 },
{ "/dev/oncrpc/", 0660, AID_ROOT, AID_SYSTEM, 1 },
{ "/dev/adsp/", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/snd/", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/mt9t013", 0660, AID_SYSTEM, AID_SYSTEM, 0 },
{ "/dev/msm_camera/", 0660, AID_SYSTEM, AID_SYSTEM, 1 },
{ "/dev/akm8976_daemon",0640, AID_COMPASS, AID_SYSTEM, 0 },
{ "/dev/akm8976_aot", 0640, AID_COMPASS, AID_SYSTEM, 0 },
{ "/dev/akm8973_daemon",0640, AID_COMPASS, AID_SYSTEM, 0 },
{ "/dev/akm8973_aot", 0640, AID_COMPASS, AID_SYSTEM, 0 },
{ "/dev/bma150", 0640, AID_COMPASS, AID_SYSTEM, 0 },
{ "/dev/cm3602", 0640, AID_COMPASS, AID_SYSTEM, 0 },
{ "/dev/akm8976_pffd", 0640, AID_COMPASS, AID_SYSTEM, 0 },
{ "/dev/lightsensor", 0640, AID_SYSTEM, AID_SYSTEM, 0 },
{ "/dev/msm_pcm_out", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/msm_pcm_in", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/msm_pcm_ctl", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/msm_snd", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/msm_mp3", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/audience_a1026", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/tpa2018d1", 0660, AID_SYSTEM, AID_AUDIO, 1 },
{ "/dev/msm_audpre", 0660, AID_SYSTEM, AID_AUDIO, 0 },
{ "/dev/msm_audio_ctl", 0660, AID_SYSTEM, AID_AUDIO, 0 },
{ "/dev/htc-acoustic", 0660, AID_SYSTEM, AID_AUDIO, 0 },
{ "/dev/vdec", 0660, AID_SYSTEM, AID_AUDIO, 0 },
{ "/dev/q6venc", 0660, AID_SYSTEM, AID_AUDIO, 0 },
{ "/dev/snd/dsp", 0660, AID_SYSTEM, AID_AUDIO, 0 },
{ "/dev/snd/dsp1", 0660, AID_SYSTEM, AID_AUDIO, 0 },
{ "/dev/snd/mixer", 0660, AID_SYSTEM, AID_AUDIO, 0 },
{ "/dev/smd0", 0640, AID_RADIO, AID_RADIO, 0 },
{ "/dev/qemu_trace", 0666, AID_SYSTEM, AID_SYSTEM, 0 },
{ "/dev/qmi", 0640, AID_RADIO, AID_RADIO, 0 },
{ "/dev/qmi0", 0640, AID_RADIO, AID_RADIO, 0 },
{ "/dev/qmi1", 0640, AID_RADIO, AID_RADIO, 0 },
{ "/dev/qmi2", 0640, AID_RADIO, AID_RADIO, 0 },
/* CDMA radio interface MUX */
{ "/dev/ts0710mux", 0640, AID_RADIO, AID_RADIO, 1 },
{ "/dev/ppp", 0660, AID_RADIO, AID_VPN, 0 },
{ "/dev/tun", 0640, AID_VPN, AID_VPN, 0 },
{ NULL, 0, 0, 0, 0 },
};

Ⅳ android sensor怎样创建设备节点

在Android中，由于没有mdev和udev，所以它没有办法动态的生成设备节点，那么它是如何做的呢？

我们可以在system/core/init/下的init.c和devices.c中找到答案：

init.c中

在Android中，没有独立的类似于udev或者mdev的用户程序，这个功能集成到了init中做了。代码见：system/core/init/init.c文件，如下：

if (ufds[0].revents == POLLIN)

handle_device_fd(device_fd);

其中handle_device_fd(device_fd)函数在system/core/init/devices.c中实现，参数device_fd 由函数device_init（）->open_uevent_socket()->socket(PF_NETLINK, SOCK_DGRAM, NETLINK_KOBJECT_UEVENT)函数调用返回。

函数handle_device_fd(device_fd)中，根据传进来的device_fd参数，调用recv(fd, msg, UEVENT_MSG_LEN, 0)函数，将内核探测到的设备并通过NETLINK机制传过来的socket描述符转化成消息。接着调用parse_event(msg, &uevent);函数将消息翻译成uevent事件，并将改事件传递给handle_device_event（&uevent）函数。

handle_device_event（&uevent）函数中，依据参数uevent->subsystem类型创建dev下的相应目录，如：/dev/graphics。紧接着根据uevent->action是"add"还是"remove"来实现设备节点的创建与删除。如果uevent->action是"add"，则调用make_device(devpath, block, uevent->major, uevent->minor)函数生成设备节点。如果uevent->action是"remove"，则调用unlink(devpath)对设备节点进行删除。

Ⅳ linux鍔犺浇dts鐨勬椂鍊欎細鍒涘缓璁惧囪妭鐐瑰悧

From:http://m.blog.csdn.net/blog/liliyaya/9188193

1. 鍦\kernel\of\fdt.c 涓鏈夊備笅鍒濆嬪寲鍑芥暟 娉ㄩ噴涓婏細灞曞紑璁惧囨爲锛屽垱寤篸evice_nodes鍒板叏灞鍙橀噺allnodes涓

void __init unflatten_device_tree(void)
{
__unflatten_device_tree(initial_boot_params, &allnodes,
early_init_dt_alloc_memory_arch);

/* Get pointer to "/chosen" and "/aliasas" nodes for use everywhere */
of_alias_scan(early_init_dt_alloc_memory_arch);
}
unflatten_device_tree鍑芥暟琚玸etup_arch鍑芥暟璋冪敤锛
鍥犱负鎴戜滑浣跨敤寰楁槸arm骞冲彴鎵浠ュ瓨鍦\kernel\arch\arm\kernel\setup.c涓
void __init setup_arch(char **cmdline_p)
{
unflatten_device_tree()
}

setup_arch鍑芥暟鍦╧ernel鍚鍔ㄦ槸琚璋冪敤锛屽備笅鍚鍔╧ernel瀛樺湪\kernel\init\main.c涓
asmlinkage void __init start_kernel(void)
{
setup_arch(&command_line);
}

杩欎簺宸ヤ綔瀹屾垚瑙ｆ瀽DTS鏂囦欢銆備繚瀛樺埌鍏ㄥ眬閾捐〃allnodes涓銆

2銆佸湪makefile涓鏈夎繖娈佃瘽鏉ョ紪璇慸ts鏂囦欢锛

$(obj)/A20%.dtb: $(src)/dts/A20%.dts FORCE
$(call if_changed_dep,dtc)

$(obj)/A68M%.dtb: $(src)/dts/A68M%.dts FORCE
$(call if_changed_dep,dtc)

鍜.c鏂囦欢鐢熸垚.o鏂囦欢涓鏍 鍥炵敓鎴.dtb鏂囦欢銆傚湪
/home/liyang/workspace/SZ_JB-mr1-8628-bsp-1012/out/target/proct/msm8226/obj/KERNEL_OBJ/arch/arm/boot
鐩褰曚笅锛屼笌zimage涓涓鐩褰曘

3銆
鍦 board-8226.c涓鏈夊垵濮嬪寲鍑芥暟-->鍚鍔ㄨ嚜鍔ㄦ帀鐢
void __init msm8226_init(void)
{
of_platform_populate(NULL, of_default_bus_match_table, adata, NULL);
}

of_platform_populate鍦╧ernel\driver\of\platform.c涓瀹氫箟锛屽洖鏌ヨ

root = root ? of_node_get(root) : of_find_node_by_path("/");
for_each_child_of_node(root, child)
{
rc = of_platform_bus_create(child, matches, lookup, parent, true);
if (rc)
break;
}
of_node_put(root);

鍦ㄨ繖閲岀敤鍒板緱鍑芥暟of_find_node_by_path浼氭渶缁堣皟鐢ㄥ埌kernel\driver\of\base.c涓寰楀嚱鏁
struct device_node *of_find_node_by_path(const char *path)
{
閬嶅巻绗1姝ヤ腑寰梐llnodes鎵惧埌鏍硅妭鐐
}

of_platform_bus_create()鍑芥暟涓鍒涘缓寰楀唴瀹瑰瓨鍦ㄤ簡 adata涓銆

浠ヤ笅鍐呭逛负杞杞斤細

锛2锛変娇鐢―TS娉ㄥ唽鎬荤嚎璁惧囩殑杩囩▼

浠ラ珮閫8974骞冲彴涓轰緥锛屽湪娉ㄥ唽i2c鎬荤嚎鏃讹紝浼氳皟鐢ㄥ埌qup_i2c_probe()鎺ュ彛锛岃ユ帴鍙ｇ敤浜庣敵璇锋荤嚎璧勬簮鍜屾坊鍔爄2c閫傞厤鍣ㄣ傚湪鎴愬姛娣诲姞i2c閫傞厤鍣ㄥ悗锛屼細璋冪敤of_i2c_register_devices()鎺ュ彛銆傛ゆ帴鍙ｄ細瑙ｆ瀽i2c鎬荤嚎鑺傜偣鐨勫瓙鑺傜偣锛堟寕杞藉湪璇ユ荤嚎涓婄殑i2c璁惧囪妭鐐癸級锛岃幏鍙杋2c璁惧囩殑鍦板潃銆佷腑鏂鍙风瓑纭浠朵俊鎭銆傜劧鍚庤皟鐢╮equest_mole()鍔犺浇璁惧囧瑰簲鐨勯┍鍔ㄦ枃浠讹紝璋冪敤i2c_new_device()锛岀敓鎴恑2c璁惧囥傛ゆ椂璁惧囧拰椹卞姩閮藉凡鍔犺浇锛屼簬鏄痙rvier閲岄潰鐨刾robe鏂规硶灏嗚璋冪敤銆傚悗闈㈡祦绋嬪氨鍜屼箣鍓嶄竴鏍蜂簡銆
绠鑰岃█涔嬶紝Linux閲囩敤DTS鎻忚堪璁惧囩‖浠朵俊鎭鍚庯紝鐪佸幓浜嗗ぇ閲忔澘鏂囦欢鍨冨溇淇℃伅銆侺inux鍦ㄥ紑鏈哄惎鍔ㄩ樁娈碉紝浼氳В鏋怐TS鏂囦欢锛屼繚瀛樺埌鍏ㄥ眬閾捐〃allnodes涓锛屽湪鎺夌敤.init_machine鏃讹紝浼氳窡鎹產llnodes涓鐨勪俊鎭娉ㄥ唽骞冲彴鎬荤嚎鍜岃惧囥傚煎緱娉ㄦ剰鐨勬槸锛屽姞杞芥祦绋嬪苟涓嶆槸鎸夋壘浠庢爲鏍瑰埌鏍戝彾鐨勬柟寮忛掑綊娉ㄥ唽锛岃屾槸鍙娉ㄥ唽鏍硅妭鐐逛笅鐨勭涓绾у瓙鑺傜偣锛岀浜岀骇鍙婁箣鍚庣殑瀛愯妭鐐规殏涓嶆敞鍐屻侺inux绯荤粺涓嬬殑璁惧囧ぇ澶氶兘鏄鎸傝浇鍦ㄥ钩鍙版荤嚎涓嬬殑锛屽洜姝ゅ湪骞冲彴鎬荤嚎琚娉ㄥ唽鍚庯紝浼氭牴鎹產llnodes鑺傜偣鐨勬爲缁撴瀯锛屽幓瀵绘壘璇ユ荤嚎鐨勫瓙鑺傜偣锛屾墍鏈夌殑瀛愯妭鐐瑰皢琚浣滀负璁惧囨敞鍐屽埌璇ユ荤嚎涓娿