Linux drivers development - Revision history

WikiSysop: /* Adding your own drivers */

2013-09-04T15:55:52Z

Adding your own drivers

← Older revision		Revision as of 17:55, 4 September 2013
Line 10:		Line 10:
	You can select, in the linux "menuconfig / xconfig" tool, which Armadeus drivers you want to add on your target.		You can select, in the linux "menuconfig / xconfig" tool, which Armadeus drivers you want to add on your target.
	<pre class="host">		<pre class="host">
	$ make ~~linux26~~-menuconfig		$ make linux-menuconfig
	</pre>		</pre>

Line 30:		Line 30:
	or		or
	<pre class="host">		<pre class="host">
	$ make ~~linux26~~		$ make linux
	</pre>		</pre>

	Only ''make ~~linux26~~'' will install the modules in the target rootfs image		Only ''make linux'' will install the modules in the target rootfs image

	== i.MX register access from driver ==		== i.MX register access from driver ==

Salocin68 at 19:28, 1 August 2010

2010-08-01T19:28:07Z

← Older revision		Revision as of 21:28, 1 August 2010
Line 49:		Line 49:
	* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html		* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html
	* http://lwn.net/Articles/driver-porting/		* http://lwn.net/Articles/driver-porting/

	~~{{LanguageBar\|Linux_drivers_development\|Développement de pilotes linux\|Linux Treiber Entwicklung}}~~

JulienB: direct access to registers with Macro is deprecated

2009-08-05T16:48:35Z

direct access to registers with Macro is deprecated

← Older revision		Revision as of 18:48, 5 August 2009
Line 37:		Line 37:
	== i.MX register access from driver ==		== i.MX register access from driver ==

	To access i.MX registers from your driver, please use the ~~macros defined in:~~		To access i.MX registers from your driver, please use the ''readw/readl/writew/writel'' helper functions.
	~~<source lang="c">~~		Take a look at at ''arch/arm/mach-mx2/apf27.c'' or ''arch/arm/mach-imx/apf9328.c'' to have examples.
	~~#include <mach~~/~~imx-regs~~.h>
	</~~source>~~

	~~<strike>For example (access to PWM control register):<~~/~~strike>~~
	~~<source lang="~~c">
	/~~* enable the PWM *~~/
	~~PWMC \|= PWMC_EN;~~
	</~~source>~~

	==Debug==		==Debug==

JulienB: /* Adding your own drivers */

2009-08-05T16:46:15Z

Adding your own drivers

← Older revision		Revision as of 18:46, 5 August 2009
Line 19:		Line 19:

	Here is the way to add custom drivers:		Here is the way to add custom drivers:
	* in ''~~armadeus/~~target/linux/modules/'', add a directory for your driver (ex ''toto/'')		* change current dir to your armadeus view
	* put reference to this directory in the ''~~armadeus/~~target/linux/modules/Makefile'' and ''~~armadeus/~~target/linux/modules/Kconfig'' files		* in ''target/linux/modules/'', add a directory for your driver (ex ''toto/'')
	* in ''toto/'' put your driver source code and create 2 files, ''Kconfig'' and ''Makefile''. (Use ''~~armadeus/~~target/linux/modules/gpio/Makefile'' & ''Kconfig'' as examples.)		* put reference to this directory in the ''target/linux/modules/Makefile'' and ''target/linux/modules/Kconfig'' files
			* in ''toto/'' put your driver source code and create 2 files, ''Kconfig'' and ''Makefile''. (Use ''target/linux/modules/gpio/Makefile'' & ''Kconfig'' as examples.)

	To compile all the custom modules, either launch:		To compile all the custom modules, either launch:
	<pre class="host">		<pre class="host">
	$ make -C ~~armadeus/~~target/linux/modules/		$ make -C target/linux/modules/
	</pre>		</pre>
	or		or
Line 32:		Line 33:
	</pre>		</pre>

	~~only~~ ''make linux26'' will install the modules in the target rootfs image		Only ''make linux26'' will install the modules in the target rootfs image

	== i.MX register access from driver ==		== i.MX register access from driver ==

JulienB at 20:23, 11 February 2009

2009-02-11T20:23:23Z

← Older revision		Revision as of 22:23, 11 February 2009
Line 9:		Line 9:
	Our custom drivers build is integrated to the Linux build system (kbuild).		Our custom drivers build is integrated to the Linux build system (kbuild).
	You can select, in the linux "menuconfig / xconfig" tool, which Armadeus drivers you want to add on your target.		You can select, in the linux "menuconfig / xconfig" tool, which Armadeus drivers you want to add on your target.
			<pre class="host">
	$ make linux26-menuconfig		$ make linux26-menuconfig
			</pre>

			<pre class="config">
			Device Drivers --->
			Armadeus specific drivers --->
			</pre>

	Here is the way to add custom drivers:		Here is the way to add custom drivers:
	* in ''armadeus/target/linux/modules/'', add a directory for ~~you~~ driver (ex ''toto/'')		* in ''armadeus/target/linux/modules/'', add a directory for your driver (ex ''toto/'')
	* put reference to this directory in the ''armadeus/target/linux/modules/Makefile'' and ''armadeus/target/linux/modules/Kconfig'' files		* put reference to this directory in the ''armadeus/target/linux/modules/Makefile'' and ''armadeus/target/linux/modules/Kconfig'' files
	* in ''toto/'' put your driver source code and create 2 files, ''Kconfig'' and ''Makefile''. (Use ''armadeus/target/linux/modules/gpio/Makefile'' & ''Kconfig'' as examples.)		* in ''toto/'' put your driver source code and create 2 files, ''Kconfig'' and ''Makefile''. (Use ''armadeus/target/linux/modules/gpio/Makefile'' & ''Kconfig'' as examples.)

	To compile all the custom modules, either launch:		To compile all the custom modules, either launch:
			<pre class="host">
	$ make -C armadeus/target/linux/modules/		$ make -C armadeus/target/linux/modules/
			</pre>
	or		or
			<pre class="host">
	$ make linux26		$ make linux26
			</pre>

	only ''make linux26'' will install the modules in target rootfs image		only ''make linux26'' will install the modules in the target rootfs image

	== i.MX register access from driver ==		== i.MX register access from driver ==
Line 30:		Line 41:
	</source>		</source>

	For example (access to PWM control register):		<strike>For example (access to PWM control register):</strike>
	<source lang="c">		<source lang="c">
	/* enable the PWM */		/* enable the PWM */
Line 37:		Line 48:

	==Debug==		==Debug==
	Activate debug messages (from pr_debug() function) on console:		* Activate debug messages (from pr_debug() function) on console:
			<pre class="apf">
	# echo 8 > /proc/sys/kernel/printk		# echo 8 > /proc/sys/kernel/printk
			</pre>

	== Useful Links ==		== Useful Links ==
Line 44:		Line 57:
	* http://lwn.net/Articles/driver-porting/		* http://lwn.net/Articles/driver-porting/

	~~<br>[[Image:FrenchFlag.png]][[Fr:~~Développement de pilotes linux \| ~~Cette page en Français]]~~		{{LanguageBar\|Linux_drivers_development\|Développement de pilotes linux\|Linux Treiber Entwicklung}}

JulienB: /* i.MX register access from driver */

2008-12-16T17:31:38Z

i.MX register access from driver

← Older revision		Revision as of 19:31, 16 December 2008
Line 26:		Line 26:

	To access i.MX registers from your driver, please use the macros defined in:		To access i.MX registers from your driver, please use the macros defined in:
	#include <~~arch/arm~~/imx-regs.h>		<source lang="c">
			#include <mach/imx-regs.h>
			</source>

	For example (access to PWM control register):		For example (access to PWM control register):
	//enable the PWM		<source lang="c">
	PWMC \|= PWMC_EN;		/* enable the PWM */
			PWMC \|= PWMC_EN;
			</source>

	==Debug==		==Debug==

JulienB: /* Adding your own drivers */

2008-12-16T17:24:43Z

Adding your own drivers

← Older revision		Revision as of 19:24, 16 December 2008
Line 8:		Line 8:

	Our custom drivers build is integrated to the Linux build system (kbuild).		Our custom drivers build is integrated to the Linux build system (kbuild).
	You can select, in the linux "menuconfig"/"xconfig" tool, which Armadeus		You can select, in the linux "menuconfig / xconfig" tool, which Armadeus drivers you want to add on your target.
	drivers you want to add on your target. ~~(only gpio, ppdev & ps2keyboard are~~		$ make linux26-menuconfig
	~~integrated yet).~~

	Here is the way to add custom drivers:		Here is the way to add custom drivers:
	* in armadeus/target/linux/modules/, add a directory for you driver (ex toto/)		* in ''armadeus/target/linux/modules/'', add a directory for you driver (ex ''toto/'')
	* put reference to this directory in the armadeus/target/linux/modules/Makefile and armadeus/target/linux/modules/Kconfig files		* put reference to this directory in the ''armadeus/target/linux/modules/Makefile'' and ''armadeus/target/linux/modules/Kconfig'' files
	* in toto/ put your driver source code and create 2 files, Kconfig and Makefile. (Use armadeus/target/linux/modules/gpio/Makefile & Kconfig as examples.)		* in ''toto/'' put your driver source code and create 2 files, ''Kconfig'' and ''Makefile''. (Use ''armadeus/target/linux/modules/gpio/Makefile'' & ''Kconfig'' as examples.)

	To compile the modules, either launch:		To compile all the custom modules, either launch:
	* "make~~" in~~ armadeus/target/linux/modules/ ~~directory~~		$ make -C armadeus/target/linux/modules/
	or		or
	* "make ~~linux" in armadeus/~~		$ make linux26

	only "make ~~linux"~~ will install the modules in target rootfs image		only ''make linux26'' will install the modules in target rootfs image

	== i.MX register access from driver ==		== i.MX register access from driver ==

NicolasC at 05:51, 27 July 2007

2007-07-27T05:51:06Z

← Older revision		Revision as of 07:51, 27 July 2007
Line 40:		Line 40:
	* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html		* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html
	* http://lwn.net/Articles/driver-porting/		* http://lwn.net/Articles/driver-porting/

			<br>[[Image:FrenchFlag.png]][[Fr:Développement de pilotes linux \| Cette page en Français]]

JulienB: /* Driver compilation */

2007-03-24T16:15:20Z

Driver compilation

← Older revision		Revision as of 18:15, 24 March 2007
Line 5:		Line 5:
	* Linux Device Drivers (3rd edition) book: http://lwn.net/Kernel/LDD3/		* Linux Device Drivers (3rd edition) book: http://lwn.net/Kernel/LDD3/

	== ~~Driver compilation~~ ==		== Adding your own drivers ==

	Our custom drivers build is integrated to the Linux build system (kbuild).		Our custom drivers build is integrated to the Linux build system (kbuild).

JulienB: /* Useful Links */

2007-03-24T16:13:41Z

Useful Links

← Older revision		Revision as of 18:13, 24 March 2007
Line 32:		Line 32:
	//enable the PWM		//enable the PWM
	PWMC \|= PWMC_EN;		PWMC \|= PWMC_EN;

			==Debug==
			Activate debug messages (from pr_debug() function) on console:
			# echo 8 > /proc/sys/kernel/printk

	== Useful Links ==		== Useful Links ==
	* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html		* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html
	* http://lwn.net/Articles/driver-porting/		* http://lwn.net/Articles/driver-porting/