summaryrefslogtreecommitdiffstats
path: root/drivers
Commit message (Collapse)AuthorAgeFilesLines
* gpio: generic: fixup syncing with upstream Linux gpio-mmio driverAhmad Fatoum2021-05-311-1/+1
| | | | | | | | | | | | | Commit inadvertently brcm,bcm6345-gpio, wd,mbl-gpio, and ni,169445-nand-gpio, because "dat" was now requested twice. Fix this up. Tested on Erizo. Fixes: 8f9ef2d9ab ("gpio: generic: sync with upstream Linux gpio-mmio driver") Reported-by: Antony Pavlov <antonynpavlov@gmail.com> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210531065924.18966-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* mtd: spi-nor: Add support for gd25q16Michael Olbrich2021-05-251-0/+1
| | | | | | | | | | | | The entry is imported from Linux v5.12. It can befound on new versions of the Boundary Devices i.MX6 Quad Nitrogen6x boards. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de> Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210520154929.25131-1-m.olbrich@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* usb: dwc2: more precise and helpful message for dr_mode config issuesEnrico Jorns2021-05-181-2/+2
| | | | | | | | | | | | | | | | | | | With the previous message I misunderstood that the 'configuration mismatch' was caused by any entity forcing the dr_mode to 'host'/'device'. The actual intention however is to tell the user that the selected 'dr_mode' does not match the capabilities provided by the controller or the selected driver parts (USB_DWC2_HOST/USB_DWC2_GADGET). The updated warning message attempts to reflect this more explicitly. Also rename 'device' to 'peripheral' as it is named both in dtb and in macros that way. Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Acked-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210517124941.31301-1-ejo@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* usb: dwc2: do no print error message with dwc2_warn() macroEnrico Jorns2021-05-181-1/+1
| | | | | | | | | dwc2_warn() is intended for printing 'warning' messages and should thus call dev_warn() instead of dev_err(). Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Link: https://lore.barebox.org/20210517114519.28451-1-ejo@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/x86'Sascha Hauer2021-05-179-37/+1125
|\
| * watchdog: add support for Intel TCO watchdog timerAhmad Fatoum2021-05-033-0/+364
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Variants of the iTCO are integrated into many Intel southbridges. They are most often accessed via PCI. Add a driver for the variant found in the q35 QEMU machine. It should be straight forward to extend the itco_chipset_info array to support more variants in future as the need arises. To test, use: qemu-system-x86_64 -M q35 -global ICH9-LPC.noreboot=false The last option corresponds to a pin strap option, which can't be influenced from within the VM. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Link: https://lore.barebox.org/20210416062436.332665-5-ahmad@a3f.at Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * pci: add EFI PCI root bridge IO protocol driverAhmad Fatoum2021-05-035-0/+692
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | UEFI specifies two protocols for abstracting both the PCI host bus controller and for PCI devices. The protocol for PCI devices provides function pointers for accessing IO Port, Memory and PCI configuration space, among others. The protocol for bus controllers provides the ability to read the root bridge's PCI configuration space and to query resources. In barebox, we would want to reuse existing PCI drivers unmodified, so we utilize the root bridge protocol, unlike most other EFI payloads. We still utilize the PCI (device) IO protocol, but not for core functionality: EFI has already enumerated the bus for us and allocated the EFI handles. It thus makes sense to have the new pci device have the EFI handle as parent and the controller as grand parent instead of being sibling with the EFI handles. This is done with an early PCI fixup that patches the device's parent pointer after consulting the PCI IO GetLocation. Driver is written from scratch and hasn't seen heavy usage yet, so it should be used with care. It was written while consulting the UEFI 2.1D specification. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Link: https://lore.barebox.org/20210416062436.332665-4-ahmad@a3f.at Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * PCI: support PCI BIOS preassigned busesAhmad Fatoum2021-05-031-37/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When running under UEFI, barebox should no redo PCI enumeration, because the UEFI implementation will likely already have drivers that won't cope with e.g. BAR addresses changing. The user-visible effect of this is that likely the framebuffer will stop working because the UEFI driver won't be able to access it any longer. Support this configuration by changing the PCI code to consult the new pcibios_assign_all_busses(). When it's true, there is no change to previous behavior. When it's false, reconfiguration is omitted and instead current configuration is read back from the bus. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Link: https://lore.barebox.org/20210416062436.332665-3-ahmad@a3f.at Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | Merge branch 'for-next/usb-gadget'Sascha Hauer2021-05-173-8/+15
|\ \
| * | fastboot/dfu: use system partitions as fall backAhmad Fatoum2021-05-121-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the new system partitions infrastructure to have fastboot and DFU fall back to using the same partitions if the global.usbgadget.dfu_function and global.fastboot_partitions are not set, respectively. No functional change intended for configurations that have SYSTEM_PARTITIONS disabled. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210503114901.13095-13-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | file_list: make freeing a NULL pointer a no-opAhmad Fatoum2021-05-121-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | This makes code added into usbgadget in a later commit less verbose. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210503114901.13095-12-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | usb: gadget: dfu: change status message to info log levelAhmad Fatoum2021-05-121-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This used to be a printf, but was changed to pr_err in f6f521ec38ea ("usb: gadget: dfu: Rework print messages"). This is likely unintended as this is an expected output. Change it to pr_info. Fixes: f6f521ec38ea ("usb: gadget: dfu: Rework print messages") Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210503114901.13095-9-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | common: make FILE_LIST feature unconditionalAhmad Fatoum2021-05-121-2/+0
| |/ | | | | | | | | | | | | | | | | | | | | | | CONFIG_FILE_LIST controls whether the file_list_* family of functions are compiled. common/file-list.o does not register any initcalls and there is no code that is dependent on it being available: it's selected as required. This means linker GC can completely get rid of it if required, so drop the symbol. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210503114901.13095-16-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | Merge branch 'for-next/riscv'Sascha Hauer2021-05-1720-130/+2115
|\ \
| * | gpio: add SiFive GPIO controller supportAhmad Fatoum2021-05-103-0/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The SiFive GPIO controller is a straight forward generic gpio-mmio controller. Only difference is that the number of GPIOs is described by the number of interrupts in the device tree. Import the Linux v5.12 driver to support it. Tested with gpio-restart on qemu-system-riscv64 -M sifive_u. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210427202309.32077-10-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | gpio: generic: sync with upstream Linux gpio-mmio driverAhmad Fatoum2021-05-102-113/+324
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The gpio-mmio driver in Linux v5.12 has evolved quite a bit since the last sync. It now supports big endian byte order, 64-bit registers as well as controllers that have both a dirin and dirout register. The latter is particularly interesting, because it's required for the SiFive GPIO controller ported in a later patch. This commit also touches gpio-mpc8xxx used on the LS1046A. Because bit and byte endianness can now be configured separately, the driver needs adjustment. We don't seem to support any boards that have the peripheral as little-endian, but this is fixed by this commit. Comparing other bgpio_init users with Linux shows no need for further fixups. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210427202309.32077-9-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | gpio: gpio-generic-platform: remove unused non-DT supportAhmad Fatoum2021-05-101-21/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have nothing in-tree matching against either "basic-mmio-gpio" or "basic-mmio-gpio-be" and none should be added, because new platforms should probe from device tree. Remove the unused the non-DT support. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210427202309.32077-8-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | serial: implement SiFive UART supportAhmad Fatoum2021-05-033-0/+181
| | | | | | | | | | | | | | | | | | | | | | | | Import serial driver from Linux v5.11. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210427202309.32077-2-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | clk: add SiFive PRCI clock controller supportAhmad Fatoum2021-05-0312-0/+1518
| |/ | | | | | | | | | | | | | | | | | | | | Import U74 and U54 clock controller support from Linux v5.12. Unlike Linux, dependency wrpll-cln28hpc.c is compiled in unconditionally. Linker garbage collection will take care to omit it if unreferenced. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210427202309.32077-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | Merge branch 'for-next/misc'Sascha Hauer2021-05-171-8/+12
|\ \
| * | usb: storage: retry for up to 10s on lengthy HDD spin upAhmad Fatoum2021-05-071-8/+12
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some USB disks take notoriously long to spin up. They are seen by a bus scan, but they report ready only after a few seconds have passed. This is not a problem if vbus is enabled early on, so devices have had a chance to spin up. If vbus is first enabled as part of the usb scan, not enough time might have passed for the USB disk to be usable. This issue was observed on an i.MX6QP with following topology: usb: USB: scanning bus for devices... usb: 5 USB Device(s) found 1 ID 0000:0000 | u-boot EHCI Host Controller | +-2 ID 0424:2517 | +-5 ID 1058:2621 | Western Digital Elements 2621 ... Unplugging and replugging the USB disk and doing a second usb scan made the unit ready test succeed. Increasing the retry count during initialization has negative consequences for other cases, like when a device is unplugged while being probed (which already takes way too long). Instead, just for the case of a detected USB mass storage device that couldn't get ready initially: retry for 10s at initialization time before giving up. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20210416172646.26834-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | Merge branch 'for-next/mci'Sascha Hauer2021-05-171-1/+3
|\ \
| * | mci: mci-core: set the DEVFS_IS_MCI_MAIN_PART_DEV flagMarco Felsch2021-05-121-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | Set the new introduced flag to be able to check if the cdev is an mmc/mci device. Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Link: https://lore.barebox.org/20210510102523.7147-2-m.felsch@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | Merge branch 'for-next/imx'Sascha Hauer2021-05-174-4/+14
|\ \ \
| * | | mtd: nand: mxs: Enable edo mode switching for i.MX28Sascha Hauer2021-05-041-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | Without it we will never use the faster timing modes. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | clk: imx28: propagate rate change to parentsSascha Hauer2021-05-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The gate clocks need to be able to set their parent's clock rates so that drivers actually can change their clock rates. The same is done in Linux. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | clk: imx28: Set gpmi clock to gpmi_refSascha Hauer2021-05-041-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The GPMI is parented to ref_xtal (=24MHz) by default. Reparent it to ref_gpmi to get reasonable NAND speed. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | watchdog: imxwd: get and enable clockSteffen Trumtrar2021-05-031-0/+11
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | This it (at least) necessary for i.MX7s or otherwise barebox will hang when trying to access the registers of WDOG2/3/4. Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de> Link: https://lore.barebox.org/20210419123747.2373-1-s.trumtrar@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | Merge branch 'for-next/dts'Sascha Hauer2021-05-171-15/+0
|\ \ \
| * | | clk: imx8mp: Remove non existing pcie clocksSascha Hauer2021-05-171-15/+0
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adoption of Linux commit: | commit 1840518ae7de0e1eeb9075069cbe632fde16c88d | Author: Richard Zhu <hongxing.zhu@nxp.com> | Date: Mon Mar 15 16:17:47 2021 +0800 | | clk: imx8mp: Remove the none exist pcie clocks | | In the i.MX8MP PCIe design, the PCIe PHY REF clock comes from external | OSC or internal system PLL. It is configured in the IOMUX_GPR14 register | directly, and can't be contolled by CCM at all. | Remove the PCIE PHY clock from clock driver to clean up codes. | There is only one PCIe in i.MX8MP, remove the none exist second PCIe | related clocks. | Remove the none exsits clocks IDs together. | | Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com> | Reviewed-by: Jason Liu <jason.hui.liu@nxp.com> | Signed-off-by: Abel Vesa <abel.vesa@nxp.com> Needed for upcoming dts update to v5.13-rc1 Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | Merge branch 'for-next/at91'Sascha Hauer2021-05-176-476/+643
|\ \ \
| * | | mci: atmel_mci: add PBL supportOleksij Rempel2021-05-036-476/+643
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | Move most of the atmel_mci code to atmel_mci_common.c and introduce atmel_mci_pbl.c for the PBL part. Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de> Link: https://lore.barebox.org/20210423142829.29468-2-o.rempel@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | mci: atmel-sdhci: FIx compiler warningSascha Hauer2021-05-121-1/+1
| |/ |/| | | | | | | | | | | gck_rate is tested for negative values. Use a signed type to let this work as expected. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | usb: dwc2: Fix wait for mode timeoutSascha Hauer2021-05-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The timeout waiting for host mode should be 110ms instead of 110us. The timeout is the same as in Linux now and the same it was before fdd30cc251. It takes 49ms to go to host mode on the Raspberry Pi 3b, so host mode stopped working with 26459ab780 which removed an additional 100ms delay before dwc2_wait_for_mode() was actually called. Fixes: fdd30cc251 ("usb: dwc2: Rework dwc2_wait_for_mode to use wait_on_timeout") Fixes: 26459ab780 ("usb: dwc2: Rework wait for host mode during core reset") Reported-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | Revert "mtd: nand_bbt: Skip bad blocks when searching for the BBT in NAND"Sascha Hauer2021-05-071-4/+0
|/ | | | | | | | | | This reverts commit 94f2da7d81cfd83685af24967e89347e7aea2ccb. Patch is reverted in Linux because it caused a regression on i.MX27, see http://lists.infradead.org/pipermail/linux-mtd/2021-April/086124.html Do the same for barebox. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/virtio'Sascha Hauer2021-04-154-0/+301
|\
| * input: virtio_input: add sound supportAhmad Fatoum2021-04-131-3/+102
| | | | | | | | | | | | | | | | | | | | Virtio input devices have an output channel for LEDs and a beeper. Register a sound card for the beeper if sound support is compiled in and the virtualized device reports sound support via the event config bits. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * input: add virtio input driverAhmad Fatoum2021-04-133-0/+199
| | | | | | | | | | | | | | | | | | | | | | We already support Linux event codes, because they are used in the device tree bindings for e.g. gpio-keys. Virtio input devices report events using the same codes, so a driver just has to shovel the codes from virtqueue into the input layer. Do so. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * input: console: skip unmappable keysAhmad Fatoum2021-03-301-0/+3
| | | | | | | | | | | | | | | | | | | | | | The input console is in charge of turning input events to barebox console keycodes. The keymap array it uses to do so has NR_KEYS entries. Keycodes with values >= NR_KEYS can thus not be mapped. Ignore them instead of evaluating arbitrary memory contents beyond the buffer. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | Merge branch 'for-next/misc'Sascha Hauer2021-04-1514-329/+325
|\ \
| * | mtd: nand_bbt: Skip bad blocks when searching for the BBT in NANDStefan Riedmueller2021-04-141-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | The blocks containing the bad block table can become bad as well. So make sure to skip any blocks that are marked bad when searching for the bad block table. Signed-off-by: Stefan Riedmueller <s.riedmueller@phytec.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | pwm: add pwm-atmel from Linux kernel 4.14Sam Ravnborg2021-04-133-0/+296
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This add the pwm-atmel.c file from kernel 4.14, modified for barebox use. The code is modelled over pwm-mxs. pwm-atmel is required to support PWM's used on a board with AT91SAM9263 - controlling backlight and contrast. Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
| * | atmel_lcdfb: fix atmel,lcd-wiring-mode; BGR => BRGSam Ravnborg2021-04-131-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | Fix spelling error that prevented us from getting the atmel,lcd-wiring-mode The Bindings mandate the use of BRG. Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
| * | mtd: fix possible overflow during mtd size multiplicationAhmad Fatoum2021-03-254-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | LGTM[1] flags a couple of places where we write a 32-bit multiplication result into a 64-bit destination. While it might very well be that there are more places in need of fixing to support flashes bigger than 4G, fixing these issues is easy and reduces the noise. Do so. [1]: https://lgtm.com/projects/g/saschahauer/barebox/alerts/?mode=list Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | clk: imx: clk-pllv1: fix wrong PLL recalc on i.MX1/i.MX21Ahmad Fatoum2021-03-251-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding -Wtype-limits to the build correctly detects that the first branch (mfn < 0) is never taken as mfn is unsigned. Import the Linux v5.11 bits that correctly checks the sign of the sign/magnitude integer. Unlike Linux, we don't need to check whether it's an i.MX1 or i.MX21 here, because an #ifdef earlier normalizes the value to be aligned with the i.MX27's. This however means that a multi-image barebox wasn't and will remain not able to properly target both <= i.MX21 and newer SoCs at the same time. This is just build-time tested. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | net: phy: at803x: fix incorrect use of FIELD_PREPAhmad Fatoum2021-03-251-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | FIELD_PREP expects mask datatype to be a constant unsigned long. The mask constant already has the correct datatype, so pass it directly. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | x86: drop legacy (PC BIOS) boot in favor of EFIAhmad Fatoum2021-03-253-312/+0
| |/ | | | | | | | | | | | | | | | | | | | | | | | | The 16-bit port has experienced bitrot and failed to compile with more recent linkers for at least a year. Fixing the linker error is insufficient to restore a barebox that can boot to shell. This continued breakage likely means that there are no users interested in updating. As new x86 projects should be using MACH_EFI_GENERIC anyway, retire support for 16-bit legacy boot (MACH_X86_GENERIC). Acked-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | Merge branch 'for-next/gpio'Sascha Hauer2021-04-1510-15/+419
|\ \
| * | gpio: pl061: implement gpio_ops::get_directionAhmad Fatoum2021-04-131-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | This makes gpioinfo on board that incorporate it more useful. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Link: https://lore.pengutronix.de/20210410105110.2080785-1-ahmad@a3f.at Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | watchdog: add GPIO watchdog driverAhmad Fatoum2021-04-133-0/+150
| | | | | | | | | | | | | | | | | | | | | This is a straight port from Linux v5.11. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Link: https://lore.pengutronix.de/20210410103511.2073504-5-ahmad@a3f.at