- 28 4月, 2020 2 次提交
-
-
由 Heinrich Schuchardt 提交于
free() checks if its argument is NULL. Do not duplicate this check. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
The free() function checks if the argument is NULL. Do not duplicate this check. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
- 13 4月, 2020 4 次提交
-
-
由 Rayagonda Kokatanur 提交于
Base driver for Broadcom xHCI controllers Signed-off-by: NBharat Kumar Reddy Gooty <bharat.gooty@broadcom.com> Signed-off-by: NRayagonda Kokatanur <rayagonda.kokatanur@broadcom.com> Signed-off-by: NVladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>
-
由 Kever Yang 提交于
Use ofnode_ instead of fdt_ APIs so that the drivers can support live DT. This patch updates usb_get_dr_mode() and usb_get_maximum_speed() to use ofnode as parameter instead of fdt offset. And all the drivers who use these APIs update to use live dt APIs at the same time. Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
-
由 Kever Yang 提交于
Use dev_read_addr_ptr() instead of devfdt_get_addr() so that we can support live DT. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Reviewed-by: NRamon Fried <rfried.dev@gmail.com>
-
由 Kever Yang 提交于
The fdtdec.h is no use in this file, remove the include code. Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
-
- 10 4月, 2020 1 次提交
-
-
由 Marek Vasut 提交于
Rather than keeping the asynchronous schedule running always, keep it running only across USB mass storage transfers for now, as it seems that keeping it running all the time interferes with certain control transfers during device enumeration. Note that running the async schedule all the time should not be an issue, especially on EHCI HCD, as that one implements most of the transfers using async schedule. Note that we have usb_disable_asynch(), which however is utterly broken. The usb_disable_asynch() blocks the USB core from doing async transfers by setting a global flag. The async schedule should however be disabled per USB controller. Moreover, setting a global flag does not prevent the controller from using the async schedule, which e.g. the EHCI HCD does. This patch implements additional callback to the controller, which permits it to lock the async schedule and keep it running across multiple transfers. Once the schedule is unlocked, it must also be disabled. This thus prevents the async schedule from running outside of the USB mass storage transfers. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Lukasz Majewski <lukma@denx.de> Cc: Tom Rini <trini@konsulko.com> Tested-by: Tom Rini <trini@konsulko.com> [omap3_beagle, previously failing]
-
- 30 3月, 2020 3 次提交
-
-
由 Kever Yang 提交于
Use ofnode_ instead of fdt_ APIs so that the drivers can support live DT. This patch updates usb_get_dr_mode() and usb_get_maximum_speed() to use ofnode as parameter instead of fdt offset. And all the drivers who use these APIs update to use live dt APIs at the same time. Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
-
由 Kever Yang 提交于
Use dev_read_addr_ptr() instead of devfdt_get_addr() so that we can support live DT. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Reviewed-by: NRamon Fried <rfried.dev@gmail.com>
-
由 Kever Yang 提交于
The fdtdec.h is no use in this file, remove the include code. Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
-
- 18 3月, 2020 1 次提交
-
-
由 Andre Przywara 提交于
Some config symbols are found in *almost* every _defconfig file for Allwinner boards, because those options are actually a platform choice, and not a per-board decision. Some of these options are older, some have recently been added. Move those options to be set for all Allwinner boards in their respective Kconfig files. The rationales are as follows: - NR_DRAM_BANKS: All Allwinner SoC map DRAM at one contiguous region of address space only, starting at 1 GB. So it's always one bank. - SPL_{DOS,EFI}_PARTITION: The Allwinner SPL does only support raw MMC accesses, we don't care about filesystems or partitions in there, so there is no need to define those symbols at all. - USE_PREBOOT: We start USB early when a keyboard is configured, using the preboot env variable, so we need to set this variable. - SYS_RELOC_GD_ENV_ADDR: We don't specify any ENV_ADDR, so need this symbol to be set (according to 8d8ee47e). - SYS_USB_EVENT_POLL_VIA_INT_QUEUE: According to commit eab9433a, specifying this reduces the latency of the USB keyboard handling, so this was formerly enabled in config headers for all Allwinner boards. Signed-off-by: NAndre Przywara <andre.przywara@arm.com> Acked-by: NMaxime Ripard <mripard@kernel.org> Tested-by: Jagan Teki <jagan@amarulasolutions.com> # Amarula A64-Relic Reviewed-by: NJagan Teki <jagan@amarulasolutions.com>
-
- 02 3月, 2020 2 次提交
-
-
由 Seung-Woo Kim 提交于
After the commit 9b643e31 ("treewide: replace with error() with pr_err()"), there are pr_err() usages without line break. Add missing line breaks for pr_err() used in f_thor. Signed-off-by: NSeung-Woo Kim <sw0312.kim@samsung.com>
-
由 Andy Shevchenko 提交于
In case dfu command is being executed with timeout option, the timer may expire in the middle of DFU operation. If there is DFU request coming, we may simple reset timeout value to prevent aborting of ongoing DFU operation. Signed-off-by: NAndy Shevchenko <andriy.shevchenko@linux.intel.com> Tested-by: NFerry Toth <ftoth@exalondelft.nl>
-
- 19 2月, 2020 2 次提交
-
-
由 Masahiro Yamada 提交于
The implementation of dma_map_single() and dma_unmap_single() is exactly the same for all the architectures that support them. Factor them out to <linux/dma-mapping.h>, and make all drivers to include <linux/dma-mapping.h> instead of <asm/dma-mapping.h>. If we need to differentiate them for some architectures, we can move the generic definitions to <asm-generic/dma-mapping.h>. Add some comments to the helpers. The concept is quite similar to the DMA-API of Linux kernel. Drivers are agnostic about what is going on behind the scene. Just call dma_map_single() before the DMA, and dma_unmap_single() after it. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Masahiro Yamada 提交于
dma_unmap_single() takes the dma address, not virtual address. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
- 06 2月, 2020 2 次提交
-
-
由 Simon Glass 提交于
At present dm/device.h includes the linux-compatible features. This requires including linux/compat.h which in turn includes a lot of headers. One of these is malloc.h which we thus end up including in every file in U-Boot. Apart from the inefficiency of this, it is problematic for sandbox which needs to use the system malloc() in some files. Move the compatibility features into a separate header file. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
At present devres.h is included in all files that include dm.h but few make use of it. Also this pulls in linux/compat which adds several more headers. Drop the automatic inclusion and require files to include devres themselves. This provides a good indication of which files use devres. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NAnatolij Gustschin <agust@denx.de>
-
- 03 2月, 2020 1 次提交
-
-
由 Vignesh Raghavendra 提交于
Invalidate dcache line before accessing Setup Packet contents. Otherwise driver will see stale content on non coherent architecture. Signed-off-by: NVignesh Raghavendra <vigneshr@ti.com>
-
- 30 1月, 2020 1 次提交
-
-
由 Marek Szyprowski 提交于
Broadcom 2835 SoC requires special conversion of physical memory addresses for DMA purpose, so add needed wrappers to dwc2_udc_otg driver. Also extend the list of compatible devices with 'brcm,bcm2835-usb' entry. This allows to use USB gadget drivers (i.e. DFU) on Raspberry Pi4 boards. Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com> Reviewed-by: NLukasz Majewski <lukma@denx.de> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
- 26 1月, 2020 1 次提交
-
-
由 mingming lee 提交于
Using musb-new structure for mt85xx gadget driver. Add gadget driver dts for mt8518 SoCs. Signed-off-by: Nmingming lee <mingming.lee@mediatek.com>
-
- 25 1月, 2020 2 次提交
-
-
由 Simon Glass 提交于
At present panic() is in the vsprintf.h header file. That does not seem like an obvious choice for hang(), even though it relates to panic(). So let's put hang() in its own header. Signed-off-by: NSimon Glass <sjg@chromium.org> [trini: Migrate a few more files] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Simon Glass 提交于
This function has a very generic name which does not adequately describe its purpose. Rename it and move it to image.h, since it relates to reading a script from an image. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 20 1月, 2020 1 次提交
-
-
由 Vignesh Raghavendra 提交于
AM654 has DWC3 USB controller that is very similar to other TI SoCs. Add a new compatible to enable the same. Signed-off-by: NVignesh Raghavendra <vigneshr@ti.com> Reviewed-by: NMarek Vasut <marex@denx.de> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
- 18 1月, 2020 2 次提交
-
-
由 Simon Glass 提交于
At present panic() is in the vsprintf.h header file. That does not seem like an obvious choice for hang(), even though it relates to panic(). So let's put hang() in its own header. Signed-off-by: NSimon Glass <sjg@chromium.org> [trini: Migrate a few more files] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Simon Glass 提交于
This function has a very generic name which does not adequately describe its purpose. Rename it and move it to image.h, since it relates to reading a script from an image. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 08 1月, 2020 1 次提交
-
-
由 Simon Glass 提交于
These macros use __FILE__ which inserts the full path of the object file into U-Boot, thus increasing file size. Drop these usages. An older version of this patch was submitted here: http://patchwork.ozlabs.org/patch/1205784/Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 22 12月, 2019 2 次提交
-
-
由 Jagan Teki 提交于
DWC3 support phy interfaces like 8/16-bit UTMI+. phy interface initialization code would handle them properly along with UNKNOWN type by default if none of the user/board doesn't need to use the phy interfaces at all. The current code is masking the 8/16-bit UTMI+ interface bits globally which indeed effect the UNKNOWN cases, therefore it effects the platforms which are not using phy interfaces at all. So, handle the phy masking bits accordingly on respective interface type cases. Fixes: 6b7ebff0 ("usb: dwc3: Add phy interface for dwc3_uboot") Reported-by: NAndy Shevchenko <andy.shevchenko@gmail.com> Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
-
由 Vignesh Raghavendra 提交于
Since, commit 62f9b654 ("common: Move older CPU functions to their own header") cache ops functions are declared in a separate header. Include the same to avoid build warnings. Signed-off-by: NVignesh Raghavendra <vigneshr@ti.com>
-
- 03 12月, 2019 3 次提交
-
-
由 Simon Glass 提交于
Move these functions into the command.h header file which is a better fit. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Simon Glass 提交于
These functions are CPU-related and do not use driver model. Move them to cpu_func.h Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Simon Glass 提交于
Move this function header to serial.h since this function is clearly related to serial. The function itself stays in console.c since we don't have a single serial file. DM and non-DM each has a separate file so we would have to either create a new common serial file, or repeat the function in both serial.c and serial-uclass.c, neither of which seem worthwhile. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NTom Rini <trini@konsulko.com>
-
- 25 11月, 2019 2 次提交
-
-
由 Heinrich Schuchardt 提交于
Allow the unit test to pass full 8 byte scan code sequences to the USB keyboard emulation driver and to parse multi-byte escape sequences. The following features are not yet tested: * LED status * caps-lock * num-lock * numerical pad keys The following features are not yet implemented by the USB keyboard driver and therefore not tested: * modifiers for non-alpha-numeric keys, e.g. <SHIFT><TAB> and <ALT><F4> * some special keys, e.g. <PRINT> * some modifiers, e.g. <ALT> and <META> * alternative keyboard layouts Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Provide support for F1-F12, Insert, Delete, Home, End, Page Up, Page Down. As this leads to a size increase provide a customizing setting CONFIG_USB_KEYBOARD_FN_KEYS. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
- 23 11月, 2019 6 次提交
-
-
由 Jagan Teki 提交于
Add 0x330c for rk3399 gadget product number. Tested-by: NLevin Du <djw@t-chip.com.cn> Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
-
由 Jagan Teki 提交于
U-Boot has two different variants of dwc3 initializations, - with dm variant gadget, so the respective dm driver would call the dwc3_init in core. - with non-dm variant gadget, so the usage board file would call dwc3_uboot_init in core. The driver probe would handle all respective gadget properties including phy interface via phy_type property and then trigger dwc3_init for dm-variant gadgets. So, to support the phy interface for non-dm variant gadgets, the better option is dwc3_uboot_init since there is no dedicated controller for non-dm variant gadgets. This patch support for adding phy interface like 8/16-bit UTMI+ code for dwc3_uboot. This change used Linux phy.h enum list, to make proper code compatibility. Cc: Marek Vasut <marex@denx.de> Tested-by: NLevin Du <djw@t-chip.com.cn> Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NMarek Vasut <marex@denx.de> Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
-
由 Jagan Teki 提交于
Add 0x310c for rk3128 gadget product number. Tested-by: NLevin Du <djw@t-chip.com.cn> Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
-
由 Jagan Teki 提交于
Rockchip support differnet or common gadget product number between Rockchip SoCs like, 0x310a - rk3036 0x320a - rk3229, rk3288 0x330a - rk3328 So, select them on Kconfig based on platform specific config defined. This eventually drop the explicit configs defined in supporting board defconfig files. Tested-by: NLevin Du <djw@t-chip.com.cn> Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
-
由 Jagan Teki 提交于
Gadget vendor number, 0x2207 is common across all platfroms supported in Rockchip SoC. So, select the same number globally, if ARCH_ROCKCHIP. This eventually drop the explicit configs defined in supported board defconfig files. Tested-by: NLevin Du <djw@t-chip.com.cn> Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
-
由 Jagan Teki 提交于
Select the gadget manufacturer as 'Rockchip' for all rockchip platform SoC's. This eventually drop the explicit defined added on supported board defconfig files. Tested-by: NLevin Du <djw@t-chip.com.cn> Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
-
- 22 11月, 2019 1 次提交
-
-
由 Simon Goldschmidt 提交于
Since upgrading to gcc9, warnings are issued: "taking address of packed member of ‘...’ may result in an unaligned pointer value" Fix this by converting dwc2_fifo_read to use unaligned access since packed structures may be on an unaligned address, depending on USB hardware. Signed-off-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
-