Siarhei Siamashka <[email protected]> writes: > On Fri, 16 Jan 2015 23:30:11 +0100 > Jens Thiele <[email protected]> wrote: > >> with kernel sunxi-3.4.103 (sunxi-3.4 branch) and CONFIG_CMA=y (as in >> sun7i_defconfig) i have no mmc device. >> >> hardware: >> a20 olinuxino micro >> >> [ 3.494360] [mmc-msg] sw_mci_init >> [ 3.503435] [mmc-msg] MMC host used card: 0x9, boot card: 0x0, io_card 8 >> [ 3.513585] [mmc-err] alloc dma des failed >> [ 3.522066] [mmc-err] sunxi-mmc.0: Failed to get resouce. >> [ 3.530705] [mmc-err] alloc dma des failed >> [ 3.539168] [mmc-err] sunxi-mmc.3: Failed to get resouce. >> >> should sun7i_defconfig be adjusted (is CONFIG_CMA=y)? >> other hints? > > You can check whether you have initrd enabled, it might be clashing > with the CMA area reservation. If CMA is enabled but fails to > initialize, then mmc fails too.
bull's eye using initrd indeed thanks! > If this is the case, then just move initrd to a different location in > RAM. will have a look (or maybe not - see below). >> all using mainline now? > > As for "using", this depends on whether you want full cedar and mali > acceleration right now. mali and cedar are not important for my usage. things i am still missing in mainline: - dpms support - audio via: http://linux-sunxi.org/Linux_mainlining_effort https://groups.google.com/forum/#!topic/linux-sunxi/svXhZ_GFxsA Message-ID: <20140702173537.9698.50825.stgit@studio> " This is first pass at a mainline driver for the A20 on-chip codec. This patch will boot and install the ALSA SOC driver. But it won't play any music. Something is wrong in either the DMA or clock code. Anyone want to give this a try and see if you can figure out what is wrong? The patch sits on top of Emilio's DMA driver for the A20. " > But as for "developing", the 3.4 kernel is de-facto in the "critical > bugfixes only" mode since at least half a year ago. New features are > not likely to appear in 3.4, and the known non-critical limitations > are not likely to be lifted. > > This does not mean that it is forbidden to contribute to 3.4 though. > Anyone is welcome to submit 3.4 patches, as long as (s)he finds at > least one reviewer for them. Please note that even if the patches > are posted to the mailing list, not everyone is eager to waste time > reviewing 3.4 patches today. thanks for clearing that up for me. => i will try to stop wasting my time with 3.4 as far as i understand maybe i could use a hack to switch the lcd off (fake dpms) via the sysfs gpio interface for now? looking at the sunxi 3.4 code and the newer u-boot code i think i would have to change 2+1 gpios? in u-boot: " static void sunxi_lcdc_panel_enable(void) { int pin; /* * Start with backlight disabled to avoid the screen flashing to * white while the lcd inits. */ pin = sunxi_name_to_gpio(CONFIG_VIDEO_LCD_BL_EN); if (pin != -1) { gpio_request(pin, "lcd_backlight_enable"); gpio_direction_output(pin, 0); } pin = sunxi_name_to_gpio(CONFIG_VIDEO_LCD_BL_PWM); if (pin != -1) { gpio_request(pin, "lcd_backlight_pwm"); /* backlight pwm is inverted, set to 1 to disable backlight */ gpio_direction_output(pin, 1); } /* Give the backlight some time to turn off and power up the panel. */ mdelay(40); pin = sunxi_name_to_gpio(CONFIG_VIDEO_LCD_POWER); if (pin != -1) { gpio_request(pin, "lcd_power"); gpio_direction_output(pin, 1); } } " I think the pins for A20 OLinuXino MICRO + A13-LCD10TS would be: CONFIG_VIDEO_LCD_POWER="PH8" CONFIG_VIDEO_LCD_BL_EN="PH7" CONFIG_VIDEO_LCD_BL_PWM="PB2" will read [1] and try with mainline kernel. Does that make sense? Any side-effects? jens PS: Sorry, for the noise. [1] http://linux-sunxi.org/GPIO#Accessing_the_GPIO_pins_through_sysfs_with_mainline_kernel -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
