| 04:52.03 | *** join/#elinux brianjaod1 (~brianjaod@209.181.82.6) |
| 12:04.48 | *** join/#elinux albert___ (~albert__@host-139-160-108-91.as7.ldn.uk.sharedband.net) |
| 12:12.00 | *** join/#elinux dijenerate (~dijenerat@host86-145-68-101.range86-145.btcentralplus.com) |
| 12:50.47 | *** join/#elinux albert___ (~albert__@host-139-160-108-91.as7.ldn.uk.sharedband.net) |
| 13:57.46 | *** join/#elinux albert___ (~albert__@host-139-160-108-91.as7.ldn.uk.sharedband.net) |
| 14:36.18 | *** join/#elinux albert___ (~albert__@host-139-160-108-91.as7.ldn.uk.sharedband.net) |
| 17:53.40 | *** join/#elinux axtronic (~axtronic@178.124.110.217) |
| 17:55.25 | *** part/#elinux axtronic (~axtronic@178.124.110.217) |
| 19:50.45 | *** join/#elinux bgamari (~bgamari@pool-108-8-241-102.spfdma.east.verizon.net) |
| 19:51.02 | bgamari | how does one determine whether the kernel has actually done anything with a dtb section? |
| 19:51.07 | bgamari | I'm trying to bring up an overlay |
| 19:51.18 | bgamari | but the pinctrl section is just being silently ignored |
| 20:06.39 | wmat | bgamari: check the pinctrl files after boot maybe |
| 20:07.03 | wmat | bgamari: cat $PINMUX? |
| 20:09.21 | wmat | bgamari: this is a useful tutorial: http://elinux.org/EBC_Exercise_11a_Device_Trees |
| 20:14.01 | bgamari | wmat, that's how I know it's being silently ignored |
| 20:14.02 | bgamari | wmat, there is no difference before and after I load the overlay |
| 20:14.47 | bgamari | wmat, I've seen it |
| 20:14.53 | wmat | no errors in dmesg? |
| 20:16.25 | bgamari | wmat, there is one |
| 20:16.34 | bgamari | [ 245.333449] adt7411 1-004b: successfully registered |
| 20:16.34 | bgamari | [ 245.350385] i2c i2c-1: Failed to register i2c client adt7411 at 0x4b (-16) |
| 20:16.44 | bgamari | it's totally unclear why however |
| 20:17.01 | bgamari | and shouldn't affect my pinctrl section |
| 20:17.43 | bgamari | I guess this is -EBUSY |
| 20:18.11 | bgamari | but despite the error the device appears to work |
| 20:20.00 | bgamari | wmat, otherwise there are several messages of the form |
| 20:20.00 | bgamari | [ 122.074889] of_get_named_gpio_flags exited with status 23 |
| 20:20.11 | bgamari | but judging from the source this is normal behavior |
| 20:21.40 | bgamari | I've tried shuffling the pinctrl-* attributes between different fragments to no avail |
| 20:21.51 | bgamari | It just utterly ignores them |
| 20:22.34 | bgamari | wmat, a pingroup would be created in the event of things working properly, no? |
| 20:23.15 | wmat | i'm not entirely sure, but I think so |
| 20:23.42 | wmat | are other dtb's recognized? |
| 20:24.05 | bgamari | the other sections in this particular file appear to work just fine |
| 20:24.08 | bgamari | just not pinctrl |
| 20:25.34 | bgamari | wmat, where exactly can pinctrl-* attributes be placed? |
| 20:30.13 | wmat | bgamari: is the pinctrl driver loaded? |
| 20:30.22 | bgamari | the debugfs files exist |
| 20:31.26 | bgamari | $ zgrep CONFIG_PINCTRL /proc/config.gz |
| 20:31.27 | bgamari | CONFIG_PINCTRL=y |
| 20:34.53 | bgamari | wmat, where exactly are pinctrl-* attributes allowed?" |
| 20:35.01 | bgamari | I've been unable to find this explicitly stated |
| 20:42.13 | wmat | I believe they're allowed in dts files or directly in the driver code |
| 20:42.38 | bgamari | wmat, By that I mean where in the devicetree? |
| 20:48.36 | wmat | in an overlay file perhaps, I'm sure I've seen them there |
| 20:50.57 | bgamari | wmat, yes, but in what nodes of the overlay? |
| 20:51.51 | wmat | no idea |
| 22:56.48 | *** part/#elinux brianjaod1 (~brianjaod@209.181.82.6) |