Date: Wed, 19 Aug 2020 10:03:44 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Alexander Mishin <mishin@mh.net.ru>, freebsd-arm@freebsd.org Subject: Re: Kmod driver at iicbus. attach() and config_intrhook(9) Message-ID: <3249fa7e-554a-83ef-57b2-7c38aa0b4591@FreeBSD.org> In-Reply-To: <7fabb65d99aaa74775c1daa91bffb873@mh.net.ru> References: <7fabb65d99aaa74775c1daa91bffb873@mh.net.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18/08/2020 22:05, Alexander Mishin wrote: > Hi > > I write a kmod driver for bh1750 light sensor with iic (almost wrote). > As usual, probe(), attach() and detach(). On attach() it runs TIMEOUT_TASK_INIT > for periodically write opecode, read result and place it to sysctl dev.bh1750.N > variables. It is all. > > But I see that some other devices (from /usr/src/sys/dev) uses CONFIG_INTRHOOK(9) > on attach() for initialize themselfs. > I wonder if I need this too? ...or maybe... when I might need it? This is usually needed when a driver needs to talk to its device while attaching. E.g., to set some initial configuration or to confirm device's identity, etc. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3249fa7e-554a-83ef-57b2-7c38aa0b4591>