- Jul 05, 2016
-
-
Hans de Goede authored
The blue led on the Mele A1000 is wired to light up as soon as the board has powered (it will be on while the gpio is still in input / floating mode), also its location on the top-set box clearly signals "power led". Until now we've been treating this as a generic usr function led, which means that when you plug power into the top-set box, the power-led lights and then turns off as soon as the kernel loads, which looks wrong. This renames the led from a1000:blue:usr to a1000:blue:pwr and marks it as default on, fixing this. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by:
Chen-Yu Tsai <wens@csie.org>
-
Hans de Goede authored
The Polaroid mid2809pxe04 tablet uses an sdio esp8089 wifi chip, so ehci0 is not used and should be disabled. Signed-off-by:
-
Hans de Goede authored
Now that we've all the necessary bits in place we can enable full otg support on these tablets. Signed-off-by:
-
Hans de Goede authored
Now that we've all the necessary bits in place we can enable full otg support on these tablets. Signed-off-by:
-
Hans de Goede authored
Add a node describing the drivebus regulator which is an (optional) part of the axp221/axp223 pmic. Since this regulator may not be available at all depending on the board, mark it as disabled by default. Signed-off-by:
-
Hans de Goede authored
Add a node describing the (optional) usbpower-supply of the axp221 / axp223 pmic. Signed-off-by:
-
Hans de Goede authored
Use of these as regulators conflicts with use of the gpio pins as gpios, so disabled the ldo_io# regulators by default, this avoids the regulator core touching them when the pins are used as gpios. Signed-off-by:
-
Aleksei Mamlin authored
No functional change. Re-order sun7i pinctrl nodes alphabetically. Signed-off-by:
Aleksei Mamlin <mamlinav@gmail.com> Signed-off-by:
-
Aleksei Mamlin authored
No functional change. Re-order sun4i pinctrl nodes alphabetically. Signed-off-by:
-
Hans de Goede authored
Update the simplefb nodes for hdmi / tv-encoder out to point to tcon0_ch1 instead of tcon0_ch0 as tcon clock. While at it fix the clocks lines being longer than 80 chars. Signed-off-by:
-
Hans de Goede authored
Update the simplefb nodes for hdmi / tv-encoder out to point to tcon0_ch1 instead of tcon0_ch0 as tcon clock. While at it fix the clocks lines being longer than 80 chars. Signed-off-by:
-
Hans de Goede authored
It seems that recent kernels have a shorter timeout when scanning for ethernet phys causing us to hit a timeout on boards where the phy's regulator gets enabled just before scanning, which leads to non working ethernet. A 10ms startup delay seems to be enough to fix it, this commit adds a 20ms startup delay just to be safe. This has been tested on a sun4i-a10-a1000 and sun5i-a10s-wobo-i5 board, both of which have non-working ethernet on recent kernels without this fix. Cc: stable@vger.kernel.org Signed-off-by:
-
Chen-Yu Tsai authored
sunxi-common-regulators.dtsi provided dummy regulators vcc3v0, vcc3v3, vcc5v0. 3.0V/3.3V and 5.0V are commonly used voltages in Allwinner devices. These dummy regulators provide a stand-in when bindings that require one, but the real regulator is not supported yet. Since these are no longer needed, we can drop the include file. Signed-off-by:
-
Chen-Yu Tsai authored
sunxi-common-regulators.dtsi provided dummy regulators vcc3v0, vcc3v3, vcc5v0. 3.0V/3.3V and 5.0V are commonly used voltages in Allwinner devices. These dummy regulators provide a stand-in when bindings that require one, but the real regulator is not supported yet. Since these are no longer needed, we can drop the include file by copying over reg_usb1_vbus. Signed-off-by:
-
Hans de Goede authored
It seems that the wifi chip is powered by both ldo3 and ldo4 tied together and that using only one results in the wifi-chip dropping of the USB bus sometimes. Ideally we would have a proper way of modelling this (this is being worked on), but currently we do not. This is not an issue since we need to keep these regulators always-on anyways, due to these boards crashing when ldo3/4 get turned back on after having been turned off. Signed-off-by:
-
Chen-Yu Tsai authored
The BPI-M2+ is an H3 development board. It is a smaller form factor than the original BPI-M2, with the new H3 SoC. It has 1GB DRAM, 8GB eMMC, a micro SD card slot, HDMI output, 2 USB host connector and 1 USB OTG connector, an IR receiver, WiFi+BT based on Ampak AP6212. The board also has a 3 pin header for (debug) UART, a 40 pin GPIO header based on the Raspberry Pi B+, but the peripheral signals are not the same, and an FPC connector for connecting BPI's camera. Signed-off-by:
-
Chen-Yu Tsai authored
Add uart1 pins for 4 pin (RX/TX/RTS/CTS) mode. Signed-off-by:
-
Chen-Yu Tsai authored
Move uart0 pins to sort the list of pin settings in alphabetical order. Signed-off-by:
-
Chen-Yu Tsai authored
The AXP809 PMIC is the primary PMIC. It provides various supply voltages for the SoC and other peripherals. The PMIC's interrupt line is connected to NMI pin of the SoC. Signed-off-by:
-
Chen-Yu Tsai authored
The AXP809 PMIC is the primary PMIC. It provides various supply voltages for the SoC and other peripherals. The PMIC's interrupt line is connected to NMI pin of the SoC. Signed-off-by:
-
Chen-Yu Tsai authored
The AXP809 PMIC is used with the Allwinner A80 SoC, along with an AXP806 PMIC as a slave. This patch adds a dtsi file for all the common bindings and default values unrelated to board design. Currently this is just listing all the regulator nodes. The regulators are initialized based on their device node names. Signed-off-by:
-
Michal Suchanek authored
spi2 is available on the UEXT connector Signed-off-by:
Michal Suchanek <hramrach@gmail.com> [Maxime: Fixed the node order] Signed-off-by:
-
Michal Suchanek authored
Used on A10s Olinuxino. Signed-off-by:
-
Chen-Yu Tsai authored
Q8 form factor A13 tablets have a 7" LCD panel. Unfortunately we don't know the exact model of the panel. Just pick a panel with display timings close to what we know. Signed-off-by:
-
Chen-Yu Tsai authored
The Q8 tablets use the audio codec to provide audio output via a headphone jack or a small mono speaker. A GPIO output is used to control speaker amp. The tablets may or may not have an internal microphone. Signed-off-by:
-
Chen-Yu Tsai authored
On the A13 Q8 tablets, the PMIC's USB power supply (VBUS) is connected to the external OTG port. This can be used to provide power and OTG VBUS sensing. Signed-off-by:
-
Chen-Yu Tsai authored
The output pin of LDO is also a GPIO pin, and the on/off settings of the regulator are actually pinmux settings. Disable it by default so it doesn't conflict with GPIO usage. Signed-off-by:
-
Maxime Ripard authored
Most of the display engine is shared between the R8 and the A13. Move the common parts to the Á13 DTSI. Signed-off-by: -
Maxime Ripard authored
The RGB bus can be used in several configurations, one of which being the RGB666. Add a pinctrl group for that case. Acked-by:
-
Priit Laes authored
Enable the display and TCON clocks that are needed to drive the display engine, tcon and TV encoders. Signed-off-by:
Priit Laes <plaes@plaes.org> Signed-off-by:
-
Priit Laes authored
Enable the display and TCON clocks that are needed to drive the display engine, tcon and TV encoders. Signed-off-by:
-
- Jun 29, 2016
-
-
Hans de Goede authored
Fix pll3x2 and pll7x2 not having a parent clock, specifically this fixes the kernel turning of pll3 while simplefb is using it when uboot has configured things to use pll3x2 as lcd ch clk parent. Signed-off-by:
-
- Jun 22, 2016
-
-
Hans de Goede authored
Now that we've a clock node describing pll3 we must add it to the simplefb nodes clocks lists to avoid it getting turned off when simplefb is used. This fixes the screen going black when using simplefb. Signed-off-by:
-
- Jun 16, 2016
-
-
Boris Brezillon authored
The sun4i-timer driver registers its sched_clock only if the machine is compatible with "allwinner,sun5i-a13", "allwinner,sun5i-a10s" or "allwinner,sun4i-a10". Add the missing "allwinner,sun5i-a13" string to the machine compatible. Signed-off-by:
Boris Brezillon <boris.brezillon@free-electrons.com> Fixes: 465a225f ("ARM: sun5i: Add C.H.I.P DTS") Cc: <stable@vger.kernel.org> Signed-off-by:
-
- May 30, 2016
-
-
Linus Torvalds authored
-
- May 29, 2016
-
-
George Spelvin authored
The self-test was updated to cover zero-length strings; the function needs to be updated, too. Reported-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
George Spelvin <linux@sciencehorizons.net> Fixes: fcfd2fbf ("fs/namei.c: Add hashlen_string() function") Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
-
George Spelvin authored
The original name was simply hash_string(), but that conflicted with a function with that name in drivers/base/power/trace.c, and I decided that calling it "hashlen_" was better anyway. But you have to do it in two places. [ This caused build errors for architectures that don't define CONFIG_DCACHE_WORD_ACCESS - Linus ] Signed-off-by:
Guenter Roeck <linux@roeck-us.net> Fixes: fcfd2fbf ("fs/namei.c: Add hashlen_string() function") Signed-off-by:
-
Mikulas Patocka authored
The HPFS filesystem used generic_show_options to produce string that is displayed in /proc/mounts. However, there is a problem that the options may disappear after remount. If we mount the filesystem with option1 and then remount it with option2, /proc/mounts should show both option1 and option2, however it only shows option2 because the whole option string is replaced with replace_mount_options in hpfs_remount_fs. To fix this bug, implement the hpfs_show_options function that prints options that are currently selected. Signed-off-by:
Mikulas Patocka <mpatocka@redhat.com> Cc: stable@vger.kernel.org Signed-off-by:
-
Mikulas Patocka authored
Commit c8f33d0b ("affs: kstrdup() memory handling") checks if the kstrdup function returns NULL due to out-of-memory condition. However, if we are remounting a filesystem with no change to filesystem-specific options, the parameter data is NULL. In this case, kstrdup returns NULL (because it was passed NULL parameter), although no out of memory condition exists. The mount syscall then fails with ENOMEM. This patch fixes the bug. We fail with ENOMEM only if data is non-NULL. The patch also changes the call to replace_mount_options - if we didn't pass any filesystem-specific options, we don't call replace_mount_options (thus we don't erase existing reported options). Fixes: c8f33d0b ("affs: kstrdup() memory handling") Signed-off-by:
-
Mikulas Patocka authored
Commit ce657611 ("hpfs: kstrdup() out of memory handling") checks if the kstrdup function returns NULL due to out-of-memory condition. However, if we are remounting a filesystem with no change to filesystem-specific options, the parameter data is NULL. In this case, kstrdup returns NULL (because it was passed NULL parameter), although no out of memory condition exists. The mount syscall then fails with ENOMEM. This patch fixes the bug. We fail with ENOMEM only if data is non-NULL. The patch also changes the call to replace_mount_options - if we didn't pass any filesystem-specific options, we don't call replace_mount_options (thus we don't erase existing reported options). Fixes: ce657611 ("hpfs: kstrdup() out of memory handling") Signed-off-by:
-
