DirkS
Posts: 10304
Joined: Tue Jun 19, 2012 9:46 pm
Location: Essex, UK

Re: New device tree kernel is in testing

Thu Dec 25, 2014 1:21 pm

Are device tree parameters local to each overlay parsing?
In other words, can I have two overlays loaded using the same parameter names?
See https://github.com/raspberrypi/document ... parameters
Overlay parameters are only in scope until the next overlay is loaded
I think that suggests that they are indeed local.

Gr
Dirk.

notro
Posts: 695
Joined: Tue Oct 16, 2012 6:21 pm
Location: Drammen, Norway

Re: New device tree kernel is in testing

Thu Dec 25, 2014 2:06 pm

Yes it does, thanks.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Thu Dec 25, 2014 2:21 pm

Yes, DirkS, that is correct. Also, when resolving parameters, the overlay namespace is searched before the base namespace.

BTW, Happy Christmas all!

notro
Posts: 695
Joined: Tue Oct 16, 2012 6:21 pm
Location: Drammen, Norway

Re: New device tree kernel is in testing

Thu Dec 25, 2014 7:12 pm

Now I have the Adafruit PiTFT display working as well.
This was tricky since the touch controller also acts as an interrupt controller.
After a day of digging, I had it working with two patches.

Overlay: https://github.com/notro/fbtft/blob/mas ... verlay.dts

IRQ patch: https://github.com/raspberrypi/linux/is ... t-68107979

And this dts patch:

Code: Select all

diff --git a/arch/arm/boot/dts/bcm2708-rpi-b-plus.dts b/arch/arm/boot/dts/bcm2708-rpi-b-plus.dts
index d9886c3..5a61521 100644
--- a/arch/arm/boot/dts/bcm2708-rpi-b-plus.dts
+++ b/arch/arm/boot/dts/bcm2708-rpi-b-plus.dts
@@ -13,6 +13,8 @@
 		i2s  = &i2s;
 		gpio = &gpio;
 		sound = &sound;
+		soc = &soc;
+		intc = &intc;
 	};
 
 	sound: sound {
diff --git a/arch/arm/boot/dts/bcm2708-rpi-b.dts b/arch/arm/boot/dts/bcm2708-rpi-b.dts
index 167b22b..724e824 100644
--- a/arch/arm/boot/dts/bcm2708-rpi-b.dts
+++ b/arch/arm/boot/dts/bcm2708-rpi-b.dts
@@ -13,6 +13,8 @@
 		i2s  = &i2s;
 		gpio = &gpio;
 		sound = &sound;
+		soc = &soc;
+		intc = &intc;
 	};
 
 	sound: sound {
diff --git a/arch/arm/boot/dts/bcm2708.dtsi b/arch/arm/boot/dts/bcm2708.dtsi
index 4b86aaa..3981b39 100644
--- a/arch/arm/boot/dts/bcm2708.dtsi
+++ b/arch/arm/boot/dts/bcm2708.dtsi
@@ -11,7 +11,7 @@
 		bootargs = "";
 	};
 
-	soc {
+	soc: soc {
 		compatible = "simple-bus";
 		#address-cells = <1>;
 		#size-cells = <1>;

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Thu Dec 25, 2014 7:23 pm

Cool. For future reference, you could have managed without the 'soc' patches because I also implemented "target-path" - an alternative to "target" that takes a full path string instead of a reference to a label - but I'm happy to add it for completeness.

notro
Posts: 695
Joined: Tue Oct 16, 2012 6:21 pm
Location: Drammen, Norway

Re: New device tree kernel is in testing

Thu Dec 25, 2014 7:45 pm

Like this?

Code: Select all

target-path = "/soc";
Is this part of the DT overlay standard (does it work on the BBB also) ?

For other readers: All platform devices will need to use this target.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Thu Dec 25, 2014 7:52 pm

Yes, it is a common (standard?) feature, supported on BBB.

sbp
Posts: 128
Joined: Wed Sep 26, 2012 7:54 pm

Re: New device tree kernel is in testing

Fri Dec 26, 2014 2:56 pm

DougieLawson wrote:
PhilE wrote:On which kernel did the RTL8188CU dongle last work reliably? Have you tried without device tree? So far it doesn't sound like it belongs here.
It works OK on 3.12.34.

There's a whole lot of new code in the 3.18 kernel for the Realtek WiFi dongles and that could be a real show stopper if you try to move forwards from 3.12 to 3.18 for the mainstream kernel. That Edimax 7811 dongle is one of the "recommended" ones that are sold by lots of the Foundation's favourite suppliers.

I've not looked at when that new code crept into the kernel source tree.
I have exact same problem with the new 3.18 kernel and my edimax realtek wifi dongle. (I had it working fine with kernel 3.14 and 3.16 kernels). As already stated this is a very popular wifi dongle so it would be important to fix.
It seems to connect and then momentarily drops the connection again (and then continues this cycle).

User avatar
DougieLawson
Posts: 38510
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: New device tree kernel is in testing

Fri Dec 26, 2014 7:07 pm

Thanks sbp for confirming that. So it isn't something I've done when I built my own kernel & dtb.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

I'll do your homework for you for a suitable fee.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

vvn2023
Posts: 33
Joined: Fri Dec 19, 2014 6:42 am

Re: New device tree kernel is in testing

Mon Dec 29, 2014 3:52 am

Hi,

i want to write the regulator info into the overlay files.

Is it possible to write that?

vvn2023
Posts: 33
Joined: Fri Dec 19, 2014 6:42 am

Re: New device tree kernel is in testing

Mon Dec 29, 2014 6:35 am

Hi,

i am facing this problem where i went wrong i dont know?

Code: Select all

snd-rpi-wsp sound: ASoC: CODEC DAI wm5102-aif1 not registered
snd-rpi-wsp sound: Failed to register card: -517
Platform sound: Driver snd-rpi-wsp requests probe deferral
snd-rpi-wsp snd-rpi-wsp.0: ASoC: CODEC DAI wm5102-aif1 not registered
snd-rpi-wsp snd-rpi-wsp.0: Failed to register card: -517
Platform snd-rpi-wsp.0: Driver snd-rpi-wsp requests probe deferral
snd-rpi-wsp sound: ASoC: CODEC DAI wm5102-aif1 not registered
snd-rpi-wsp sound: Failed to register card: -517

can u please suggest me how to do?
i did the same as the hifiberry machine driver but dont know where i went wrong? :(

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Mon Dec 29, 2014 8:25 am

It's telling you that the codec is not registered. This suggests that the codec driver has not loaded. Have you read the troubleshooting section of the documentation? Is the driver loaded? Does it have MODULE_DEVICE_TABLE(of, ...) ?

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Mon Dec 29, 2014 9:42 am

And to save time, please attach the .dts file.

vvn2023
Posts: 33
Joined: Fri Dec 19, 2014 6:42 am

Re: New device tree kernel is in testing

Mon Dec 29, 2014 10:47 am

Hi,
I added this in my machine driver probe as the hifiberry doing the same, but i am getting errors as below

Code: Select all

if (pdev->dev.of_node) {
	    struct device_node *i2s_node;
	    struct snd_soc_dai_link *dai = &snd_rpi_wsp_dai[0];
	    i2s_node = of_parse_phandle(pdev->dev.of_node,
					"i2s-controller", 0);

	    if (i2s_node) {
		dai->cpu_dai_name = NULL;
		dai->cpu_of_node = i2s_node;
		dai->platform_name = NULL;
		dai->platform_of_node = i2s_node;
	    }
	
	}

errors:

Code: Select all

[    6.649231] bcm2708_i2c_init_pinmode(1,2)
[    6.870042] bcm2708_i2c_init_pinmode(1,3)
[    7.267050] bcm2708_i2c 20804000.i2c: BSC1 Controller at 0x20804000 (irq 79) (baudrate 100000)
[    7.846888] VVN,dai->cpu_of_node->name i2s
[    8.028324] snd-rpi-wsp sound: ASoC: CODEC DAI wm5102-aif1 not registered
[    8.234258] snd-rpi-wsp sound: Failed to register card: -517
[    8.343478] random: nonblocking pool is initialized
[    8.442658] platform sound: Driver snd-rpi-wsp requests probe deferral
[    8.625013] VVN,dai->cpu_of_node->name i2s
[    8.638218] snd-rpi-wsp snd-rpi-wsp.0: ASoC: CODEC DAI wm5102-aif1 not registered
[    8.651885] snd-rpi-wsp sound: ASoC: Failed to create card debugfs directory
[    8.670186] snd-rpi-wsp sound: ASoC: CODEC DAI wm5102-aif1 not registered
[    8.698145] snd-rpi-wsp sound: Failed to register card: -517
[    8.720522] platform sound: Driver snd-rpi-wsp requests probe deferral
[    8.863046] snd-rpi-wsp snd-rpi-wsp.0: Failed to register card: -517
[    8.968174] platform snd-rpi-wsp.0: Driver snd-rpi-wsp requests probe deferral
[   11.913443] EXT4-fs (mmcblk0p6): re-mounted. Opts: (null)
[   12.382133] EXT4-fs (mmcblk0p6): re-mounted. Opts: (null)
[   13.143309] VVN,dai->cpu_of_node->name i2s
[   13.172507] snd-rpi-wsp sound: ASoC: Failed to create card debugfs directory
[   13.214182] snd-rpi-wsp sound: ASoC: CODEC DAI wm5102-aif1 not registered
[   13.255918] snd-rpi-wsp sound: Failed to register card: -517
[   13.288187] platform sound: Driver snd-rpi-wsp requests probe deferral
[   13.317236] snd-rpi-wsp snd-rpi-wsp.0: ASoC: Failed to create card debugfs directory
[   13.358249] snd-rpi-wsp snd-rpi-wsp.0: ASoC: CODEC DAI wm5102-aif1 not registered
[   13.358271] snd-rpi-wsp snd-rpi-wsp.0: Failed to register card: -517
[   13.358323] platform snd-rpi-wsp.0: Driver snd-rpi-wsp requests probe deferral
[   13.358519] VVN,dai->cpu_of_node->name i2s
[   13.358566] snd-rpi-wsp sound: ASoC: Failed to create card debugfs directory
[   13.358587] snd-rpi-wsp sound: ASoC: CODEC DAI wm5102-aif1 not registered
[   13.358599] snd-rpi-wsp sound: Failed to register card: -517
[   13.358628] platform sound: Driver snd-rpi-wsp requests probe deferral
[   13.998745] Unable to handle kernel NULL pointer dereference at virtual address 0000004c

I have no idea where it is going wrong.

I added the .of_match_table = in the codec driver also

Can u please help me in this?

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Mon Dec 29, 2014 11:33 am

If you don't answer my questions this is going to take a very long time.

I think the problem is with the codec. Is the codec device driver module loaded? I suspect it isn't.

Please upload the .dts file and the parts of the codec driver that refer to the compatible string.

Search /lib/modules/<version>/alias.module for the codec compatible string, and show what you find.

User avatar
DougieLawson
Posts: 38510
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: New device tree kernel is in testing

Mon Dec 29, 2014 11:39 am

PhilE wrote:
Please upload the .dts file and the parts of the codec driver that refer to the compatible string.
You do realise that the forum upload facility has been seriously broken and it isn't easy to use.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

I'll do your homework for you for a suitable fee.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

vvn2023
Posts: 33
Joined: Fri Dec 19, 2014 6:42 am

Re: New device tree kernel is in testing

Mon Dec 29, 2014 11:55 am

Compatible strings:
alias i2c:wm5102 arizona_i2c
alias spi:wm5102 arizona_spi
alias platform:wm5102-codec snd_soc_wm5102
alias of:N*T*Cwlf,wm5102* snd_soc_rpi_wsp


As the codec is not loading. Getting some probe error while its loading.

I am unable to upload the file, so i am sharing here.

The overlay file is:

Code: Select all


// Definitions for Wolfson audio card
/dts-v1/;


/ {
	compatible = "brcm,bcm2708";

	[email protected] {
		target = <&sound>;
		__overlay__ {
			compatible = "wlf,wm5102";
			i2s-controller = <&i2s>;
			status = "okay";
		};
	};

	[email protected] {
		target = <&i2s>;
		__overlay__ {
			status = "okay";
		};
	};

	[email protected] {
		target = <&i2c1>;
		__overlay__ {
			#address-cells = <1>;
			#size-cells = <0>;
			status = "okay";

			[email protected] {
				#sound-dai-cells = <0>;
				compatible = "wlf,wm8804";
				reg = <0x3b>;
				status = "okay";
			};
		};
	};
};



I am trying to debug the codec probe.

The table of match code in the codec driver is :

Code: Select all

static const struct of_device_id snd_rpi_wm5102_of_match[] = {
{ .compatible = "wlf,wm5102", },
	{},
};

static struct platform_driver wm5102_codec_driver = {
	.driver = {
		.name = "wm5102-codec",
		.owner = THIS_MODULE,
		.of_match_table = snd_rpi_wm5102_of_match,
	},
	.probe = wm5102_probe,
	.remove = wm5102_remove,
};


Is everything ok?
Can u help me where i am getting wrong
Last edited by vvn2023 on Mon Dec 29, 2014 12:19 pm, edited 2 times in total.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Mon Dec 29, 2014 12:00 pm

All items requested are text, and the vvn2023 has been doing fine uploading logs so far.

vvn2023
Posts: 33
Joined: Fri Dec 19, 2014 6:42 am

Re: New device tree kernel is in testing

Mon Dec 29, 2014 12:17 pm

Hi,

The table of match code in the codec driver is :

Code: Select all

static const struct of_device_id snd_rpi_wm5102_of_match[] = {
{ .compatible = "wlf,wm5102", },
	{},
};

static struct platform_driver wm5102_codec_driver = {
	.driver = {
		.name = "wm5102-codec",
		.owner = THIS_MODULE,
		.of_match_table = snd_rpi_wm5102_of_match,
	},
	.probe = wm5102_probe,
	.remove = wm5102_remove,
};


Is everything ok?

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Mon Dec 29, 2014 2:07 pm

I'm confused about the components in your sound card. Your .dts file refers to the wm5102, a huge device which appears to contain many DACs and ADCs, and also the wm8804, a simpler i2s->spdif transceiver. The wm8804 is shown as being an i2c device, but the wm5102 appears to have no connectivity.

Either your system is very complex, or you have cut-and-pasted the wm8804 section from the hifiberry-digi overlay and not modified it.

Try not to confuse/conflate the codec driver and the driver for the sound card as a whole. The codec driver should be generic, and not tied to a particular application/design. The codec is likely to rely on i2c connectivity for control, so it should be instantiated in the i2c1 node just like the wm8804 codec. The sound card driver is what should appear in the sound node. It ties together the codec(s) and the connectivity (i2s, i2c) - look at the relationship between the hifiberry-digi driver and the wm8804 driver. Is this what you have called "rpi-wsp" or "snd-rpi-wsp"? I can't see any reference to that driver in what you have uploaded, except for the dmesg output. Are you loading it explicitly from /etc/modules or using modprobe? If so, that shouldn't be necessary.

So:

1) Can you clarify the components and connectivity?

2) Either add another child to the i2c1 node for wm5102, or replace the wm8804 node with something describing the wm5102. You will probably need to change the 3b/0x3b to something else.

3) Instantiate the sound card, not the codec, in the <sound> section. This will remove the need to load it explicitly. Don't forget that the sound card driver will need the same mechanisms (MODULE_DEVICE_TABLE, .of_match_table) as the codec.

ryuu123
Posts: 5
Joined: Mon Dec 29, 2014 2:25 pm

Re: New device tree kernel is in testing

Mon Dec 29, 2014 2:43 pm

Hi, I'm new to DT.

My buildrooted kernel 3.18.1 boot fine with A+ and DT.
I've some question.

1) DT supports onboard led?
bcm2708-rpi-b-plus.dts and fdtdumped bcm2708-rpi-b-plus.dtb doesn't contain led section.
With these dtb I can't see /sys/class/leds/XXXX.
When I add following code to dts, /sys/class/leds/ACT is populated but led still dark.

Code: Select all

        leds {
                compatible = "gpio-leds";

                act {
                        label = "ACT";
                        gpios = <&gpio 16 1>;
                        /* default-state = "keep"; */
                        linux,default-trigger = "heartbeat";
                };
        };
With kernel 3.18.1, I’ve never see onboard led blinking(w/ or without DT).

2) initramfs address populating support
In config.txt “initramfs initramf.gz followKernel” works only without DT.
Without DT, ATAG_INITRD2 is correct, but with DT tag_initrd is not correctly setup. I guess.
“initramfs initramf.gz 0x00a00000” and following DT not work.

Code: Select all

        chosen {
                linux,initrd-start = <0x00a00000>;
                linux,initrd-end   = <0x10F10000>;
        };
3) With my A+, DT doesn’t load automatically, but load with config.txt
Not default to use DT?

I disable DT just now….

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Mon Dec 29, 2014 5:00 pm

Hi ryuu123,

Although you say you are new to DT, your use cases are relatively advanced and may have shown up some holes in the developing DT support.

1) There is no reason why LEDs shouldn't work with DT. It isn't something we've been focusing on so far, but I will investigate when I return from my break.

2) initramfs+DT is a combination I haven't tried (actually, so is initramfs+anything). I do know that using DT disables the ATAGs support, but your DT alternatives look plausible.

3) I don't know why your A+ wouldn't use DT automatically. The very latest firmware (one hour old) includes better diagnostics. Update again, add "dtdebug=1", reboot, then run "sudo vcdbg log msg" and look for DT-related messages. If you post them here I can interpret them for you.

ktb
Posts: 1447
Joined: Fri Dec 26, 2014 7:53 pm

Re: New device tree kernel is in testing

Mon Dec 29, 2014 9:49 pm

Here is a log from my B+. Note: I do have a mini fan attached to GPIO pins 1 and 6.

sudo vcdbg log msg:

Code: Select all

001195.268: Read command line from file 'cmdline.txt'
coherent_pool=6M smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ip=192.168.1.11::192.168.1.1

001205.811: Loading 'kernel.img' from SD card
001445.679: Loading 'bcm2708-rpi-b-plus.dtb' from SD card
001460.529: Loading 'initrd.img-3.18.1+' from SD card
001896.122: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
004110.954: vchiq_core: vchiq_init_state: slot_zero = 0x48800000, is_master = 1
004115.866: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
004120.363: gpioman: gpioman_get_pin_num: pin LEDS_RUNNING not defined
004120.391: gpioman: gpioman_get_pin_num: pin LEDS_NAND_ACTIVITY not defined
004120.415: gpioman: gpioman_get_pin_num: pin LEDS_USB_ACTIVITY not defined
004120.437: gpioman: gpioman_get_pin_num: pin LEDS_FATAL_ERROR not defined
004120.460: gpioman: gpioman_get_pin_num: pin LEDS_APP_OK not defined
004120.483: gpioman: gpioman_get_pin_num: pin LEDS_APP_FAILED not defined
004120.506: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_AUTH not defined
004120.529: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_UNAUTH not defined
004120.553: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_ON not defined
004120.577: gpioman: gpioman_get_pin_num: pin LEDS_DVI_ON not defined
004120.604: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_HPD_UP not defined
004120.625: gpioman: gpioman_get_pin_num: pin LEDS_REMOTE_CONTROL not defined
004120.647: gpioman: gpioman_get_pin_num: pin LEDS_ARM_CONTROLLED not defined
004121.156: TV service:host side not connected, dropping notification 0x00000002, 0x00000002, 0x00000027
/boot/config.txt

Code: Select all

# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

framebuffer_depth=32

# uncomment for composite PAL
#sdtv_mode=2

# defines the TV standard for composite output (default=0{NTSC})
#sdtv_mode=0

# defines the aspect ratio for composite output (default=1[4:3] or 2{14:9} or 3{16:9})
#sdtv_aspect=3

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# Enables the ignoring of EDID/display data if your display doesn't have an accurate EDID
#hdmi_ignore_edid=0xa5000080

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=2
#hdmi_mode=39

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2

hdmi_force_mode=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
config_hdmi_boost=5

#uncomment to overclock the arm. 700 MHz is the default.
arm_freq=950
core_freq=450
sdram_freq=450
gpu_freq=325
over_voltage=6

#gpu_mem=128

gpu_mem_256=112
gpu_mem_512=368
cma_lwm=16
cma_hwm=32
cma_offline_start=16

dispmanx_offline=1

avoid_safe_mode=1

# initramfs generated using initramfs-tools
initramfs initrd.img-3.18.1+

#device_tree=bcm2708-rpi-b-plus.dtb

# Uncomment some or all of these to enable the optional hardware interfaces
#device_tree_param=i2c1=on
#device_tree_param=i2s=on
#device_tree_param=spi=on

# Uncomment one of these lines to enable an audio interface
#device_tree_overlay=hifiberry-dac
#device_tree_overlay=hifiberry-dacplus
#device_tree_overlay=hifiberry-digi
#device_tree_overlay=iqaudio-dac
#device_tree_overlay=iqaudio-dacplus

# Uncomment this to enable the lirc-rpi module
#device_tree_overlay=lirc-rpi

# Uncomment this to override the defaults for the lirc-rpi module
#device_tree_param=gpio_out_pin=16
#device_tree_param=gpio_in_pin=17
#device_tree_param=gpio_in_pull=down

#device_tree_param=gpio_out_pin=1
#device_tree_param=gpio_in_pin=6

# Video codec licenses
decode_MPG2=0xeee74410
decode_WVC1=0xed7332b0

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2784
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: New device tree kernel is in testing

Mon Dec 29, 2014 10:04 pm

@ktb What is your question?

ktb
Posts: 1447
Joined: Fri Dec 26, 2014 7:53 pm

Re: New device tree kernel is in testing

Mon Dec 29, 2014 10:43 pm

Oh, I didn't have a question, but thank you. I thought my log (containing entries such as "gpioman: gpioman_get_pin_num: pin LEDS_RUNNING not defined") might be helpful to the above LED situation.

Return to “Advanced users”