- 08 5月, 2018 9 次提交
-
-
由 Jaehoon Chung 提交于
Add the MMC_TRACE config in Kconfig. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Jaehoon Chung 提交于
Add the debug message for checking the mmc clock status. It's helpful to debug the controlling clock. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Jaehoon Chung 提交于
mmc_set_clock() function has the disable argument as bool type. When mmc_set_clock is called, it might be passed to "true" or "false". But it's too confusion whether clock is enabled or disabled with only "true" and "false". To prevent the confusion, replace to MMC_CLK_ENABLE/DISABLE macro from true/false. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Jaehoon Chung 提交于
max77686 pmic is supporting with max77686.c under pmic/ and regulator/ direnctroy. Remove pmic_max77686.c what didn't use anywhere. Instead, enable CONFIG_DM_REGULATOR_MAX77686 and CONFIG_DM_PMIC_MAX77686. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Lokesh Vutla 提交于
Currently CPU_V7 kconfig symbol supports only ARMv7A architectures under armv7 folder. This led to a misconception of creating separate folders for armv7m and armv7r. There is no reason to create separate folder for other armv7 based architectures when it can co-exist with few Kconfig symbols. As a first step towards a common folder, rename CPU_V7 as CPUV7A. Later separate Kconfig symbols can be added for CPU_V7R and CPU_V7M and can co exist in the same folder. Reviewed-by: NTom Rini <trini@konsulko.com> Tested-by: NMichal Simek <michal.simek@xilinx.com> Suggested-by: NAlexander Graf <agraf@suse.de> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Masahiro Yamada 提交于
The syscon implementation in U-Boot is different from that in Linux. Thus, DT files imported from Linux do not work for U-Boot. In U-Boot driver model, each node is bound to a dedicated driver that is the most compatible to it. This design gets along with the concept of DT, and the syscon in Linux originally worked like that. However, Linux commit bdb0066df96e ("mfd: syscon: Decouple syscon interface from platform devices") changed the behavior because it is useful to let a device bind to another driver, but still work as a syscon provider. That change had happened before U-Boot initially supported the syscon driver by commit 6f98b750 ("dm: Add support for generic system controllers (syscon)"). So, the U-Boot's syscon works differently from the beginning. I'd say this is mis-implementation given that DT is not oriented to a particular project, but Linux is the canon of DT in practice. The problem typically arises in the combination of "syscon" and "simple-mfd" compatibles. In Linux, they are orthogonal, i.e., the order between "syscon" and "simple-mfd" does not matter at all. Assume the following compatible. compatible = "foo,bar-syscon", "syscon", "simple-mfd"; In U-Boot, this device node is bound to the syscon driver (driver/core/syscon-uclass.c) since the "syscon" is found to be the most compatible. Then, syscon_get_regmap() succeeds. However, compatible = "foo,bar-syscon", "simple-mfd", "syscon"; does not work because this node is bound to the simple-bus driver (drivers/core/simple-bus.c) in favor of "simple-mfd" compatible. The compatible string "syscon" is just dismissed. Moreover, compatible = "foo,bar-syscon", "syscon"; works like the first case because the syscon driver populates the child devices. This is wrong because populating children is the job of "simple-mfd" (or "simple-bus"). This commit ports syscon_node_to_regmap() from Linux. This API does not require the given node to be bound to a driver in any way. Reported-by: NKunihiko Hayashi <hayashi.kunihiko@socionext.com> Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Masahiro Yamada 提交于
Currently, regmap_init_mem() takes a udevice. This requires the node has already been associated with a device. It prevents syscon/regmap from behaving like those in Linux. Change the first argumenet to take a device node. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Acked-by: NNeil Armstrong <narmstrong@baylibre.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Masahiro Yamada 提交于
device_is_compatible() takes udevice, but there is no such a helper that takes ofnode. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Masahiro Yamada 提交于
Putting zero length array at the end of struct is a common technique to embed arbitrary length of members. There is no good reason to let regmap_alloc_count() branch by "if (count <= 1)". As far as I understood the code, regmap->base is an alias of regmap->ranges[0].start, but it is not helpful but make the code just ugly. Rename regmap_alloc_count() to regmap_alloc() because the _count suffix seems pointless. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: NSimon Glass <sjg@chromium.org> [trini: fixup cpu_info-rcar.c] Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 07 5月, 2018 2 次提交
-
-
由 Tom Rini 提交于
When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us. In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style. This commit changes all instances where we have multiple licenses (in these cases, dual license) declared in the SPDX-License-Identifier tag. In this case we change from listing "LICENSE-A LICENSE-B" or "LICENSE-A or LICENSE-B" or "(LICENSE-A OR LICENSE-B)" to "LICENSE-A OR LICENSE-B" as per the Linux Kernel style document. Note that parenthesis are allowed so when they were used before we continue to use them. Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com> Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us. In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style. This commit changes all instances where we have a single declared license in the tag as both the before and after are identical in tag contents. There's also a few places where I found we did not have a tag and have introduced one. Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 02 5月, 2018 5 次提交
-
-
由 Marek Vasut 提交于
The R8A7792 does not have the USB extal, so drop it. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
由 Heinrich Schuchardt 提交于
As ret is not set when calling max77693_get_vcell() there is no need to check ret again. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Hannes Schmelzer 提交于
The 'SDHCI_QUIRK_NO_HISPD_BIT' is used wrong here. The purpose of this quirk is to tell the sdhci-driver that the IP-core doesn't have a "high- speed-enable" bit in its registers. With this commit we change this to the correct quirk: SDHCI_QUIRK_BROKEN_HISPD_MODE Signed-off-by: NHannes Schmelzer <hannes.schmelzer@br-automation.com>
-
由 Hannes Schmelzer 提交于
Some IP-core implementations of the SDHCI have different troubles on the silicon where they are placed. On ZYNQ platform for example Xilinx doesn't accept the hold timing of an eMMC chip which operates in High-Speed mode and must be forced to operate in non high-speed mode. To get rid of this "SDHCI_QUIRK_BROKEN_HISPD_MODE" is introduced. For more details about this refer to the Xilinx answer-recor #59999 https://www.xilinx.com/support/answers/59999.html This commit: - doesn't set HISPD bit on the host-conroller - reflects this fact within the host-controller capabilities Upon this the layer above (mmc-driver) can setup the card correctly. Otherwise the MMC card will be switched into high-speed mode and causes possible timing violation on the host-controller side. Signed-off-by: NHannes Schmelzer <oe5hpm@oevsv.at> Signed-off-by: NHannes Schmelzer <hannes.schmelzer@br-automation.com>
-
由 Peng Fan 提交于
sd_read_ssr returns 0, means no error. Fixes: 5b2e72f3("mmc: read ssr only if MMC write support is enabled") Signed-off-by: NPeng Fan <peng.fan@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: Jean-Jacques Hiblot <jjhiblot@ti.com>
-
- 01 5月, 2018 2 次提交
-
-
由 Heinrich Schuchardt 提交于
An unsigned int is always >= 0. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
We should not make the same assignement twice. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
- 29 4月, 2018 3 次提交
-
-
由 Patrice Chotard 提交于
Uart status register is named USART_ISR on STM32F7, STM32H7 and STM32MP1 SoCs family, but USART_SR only on STM32F4 SoCs. Use USART_ISR_ prefix instead of USART_SR_ . Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
-
由 Patrice Chotard 提交于
Enable uart overrun feature which allows to benefits of uart FIFO usage. Previously overrun management was disabled, this has to effect to bypassed the uart FIFO usage even if FIFO was enabled. In particular configuration, for example when video console is enabled, copy/pasting a long command line in console results in corruption. This is due to the fact that a lot of time is consumed in flushing the cache during frame buffer update, so uart chars are not read fast enough. By using uart FIFO and managing overrun, long command line can by copy/paste in console without being corrupted. Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
-
由 Alex Kiernan 提交于
If SPL serial support is disabled nothing brings in sprintf, snprintf or simple_strtoul: env/built-in.o: In function `regex_callback': env/attr.c:128: undefined reference to `sprintf' disk/built-in.o: In function `blk_get_device_by_str': disk/part.c:386: undefined reference to `simple_strtoul' disk/part.c:395: undefined reference to `simple_strtoul' disk/built-in.o: In function `blk_get_device_part_str': disk/part.c:522: undefined reference to `simple_strtoul' disk/built-in.o: In function `part_set_generic_name': disk/part.c:704: undefined reference to `sprintf' drivers/built-in.o: In function `init_peripheral_ep': drivers/usb/musb-new/musb_gadget.c:1826: undefined reference to `sprintf' drivers/built-in.o: In function `musb_core_init': drivers/usb/musb-new/musb_core.c:1451: undefined reference to `snprintf' Add those dependencies here. Signed-off-by: NAlex Kiernan <alex.kiernan@gmail.com>
-
- 28 4月, 2018 3 次提交
-
-
由 Tuomas Tynkkynen 提交于
Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>
-
由 Tom Rini 提交于
We have a large number of places where while we historically referenced gd in the code we no longer do, as well as cases where the code added that line "just in case" during development and never dropped it. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Adam Ford 提交于
This converts the following to Kconfig: CONFIG_SPI This partly involves updating code that assumes that CONFIG_SPI implies things that are specific to the MPC8xx SPI driver. For now, just update the CONFIG tests. This also involves reworking the default for CONFIG_SYS_DEF_EEPROM_ADDR so that we don't set it when we cannot make a reasonable default, as it does not cause any compile failures. Signed-off-by: NAdam Ford <aford173@gmail.com> Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 27 4月, 2018 1 次提交
-
-
由 Tien Fong Chee 提交于
Commit 2baa9972 ("arm: socfpga: Add FPGA driver support for Arria 10") Polling on wrong cleared bit. Fix with correct polling on bit is set. Fixes: 2baa9972 ("arm: socfpga: Add FPGA driver support for Arria 10") Signed-off-by: NTien Fong Chee <tien.fong.chee@intel.com>
-
- 26 4月, 2018 8 次提交
-
-
由 Christophe Kerello 提交于
In case usb configuration is unknown (cdev->config == NULL), non standard request should not be processed. Remove also the cdev->config check below which will never happen. This issue was seen using ums feature. Signed-off-by: NChristophe Kerello <christophe.kerello@st.com> Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
-
由 Neil Armstrong 提交于
When no PHYs are declared in the dwc3 node, the phy init fails. This patch checks if the "phys" property is presend and reports the error returned by dev_count_phandle_with_args(). This patchs also fixes the styles issues added in last commit. This patch should fix the DWC3 support on the UniPhier SoC family. Fixes: 7c839ea7 ("usb: host: dwc3: Add support for multiple PHYs") Reported-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: NNeil Armstrong <narmstrong@baylibre.com>
-
由 Lukasz Majewski 提交于
After this change the DM FEC ETH driver can be also reused on some imx53 devices. Signed-off-by: NLukasz Majewski <lukma@denx.de>
-
由 Lukasz Majewski 提交于
Without this commit we do have an explicit dependency on CONFIG_PHYLIB when one wants to set PHY ADDR on a iMX board (FEC + driver model). This shall be changed to CONFIG_FEC_MXC_PHYADDR, as only when we do have it set, we shall mask out other devices. As a side effect, when CONFIG_FEC_MXC_PHYADDR is not set, we scan PHY bus for connected PHY devices. Signed-off-by: NLukasz Majewski <lukma@denx.de>
-
由 Kever Yang 提交于
Parse of data in dedicated api instead of in probe(). The clk_set_rate() may be called before the clk driver is probed, after core support set default clock. This patch fix system abort issue since: f4fcba5c clk: implement clk_set_defaults() Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-sytems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-sytems.com>
-
由 Kever Yang 提交于
Parse of data in dedicated api instead of in probe(). The clk_set_rate() may be called before the clk driver is probed, after core support set default clock. This patch fix system abort issue since: f4fcba5c clk: implement clk_set_defaults() Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-sytems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-sytems.com>
-
由 Kever Yang 提交于
Parse of data in dedicated api instead of in probe(). The clk_set_rate() may be called before the clk driver is probed, after core support set default clock. This patch fix system abort issue since: f4fcba5c clk: implement clk_set_defaults() Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
由 Philipp Tomsich 提交于
The DM driver for ockchip timer blocks is also applicable to the RK3188 and RK3288 timer blocks: add 'rockchip,rk3188-timer' and 'rockchip,rk3288-timer' to its compatible list to support devices claiming compatibility with these. Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
- 25 4月, 2018 3 次提交
-
-
由 Wadim Egorov 提交于
The generic ehci-driver (ehci-generic.c) will try to enable the clocks listed in the DTSI. If this fails (e.g. due to clk_enable not being implemented in a driver and -ENOSYS being returned by the clk-uclass), the driver will bail our and print an error message. This implements a minimal clk_enable for the RK3288 and supports the clocks mandatory for the EHCI controllers; as these are enabled by default we simply return success. Signed-off-by: NWadim Egorov <w.egorov@phytec.de> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
由 Philipp Tomsich 提交于
Throughput tests have shown the sunxi_mmc driver to take over 10s to read 10MB from a fast eMMC device due to excessive delays in polling loops. This commit restructures the main polling loops to use get_timer(...) to determine whether a (millisecond) timeout has expired. We choose not to use the wait_bit function, as we don't need interruptability with ctrl-c and have at least one case where two bits (one for an error condition and another one for completion) need to be read and using wait_bit would have not added to the clarity. The observed speedup in testing on a A31 is greater than 10x (e.g. a 10MB write decreases from 9.302s to 0.884s). Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Signed-off-by: NMaxime Ripard <maxime.ripard@bootlin.com> Tested-by: NMylène Josserand <mylene.josserand@bootlin.com> Acked-by: NJagan Teki <jagan@openedev.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
With clang-4.0 and later we see: warning: logical not is only applied to the left hand side of this bitwise operator [-Wlogical-not-parentheses] if ((!gd->flags & GD_FLG_RELOC)) ^ ~ And while the compiler suggests adding parenthesis around gd->flags, a reading of the code says that we want to know when GD_FLG_RELOC is not set and then return. Cc: Simon Glass <sjg@chromium.org> Cc: Anatolij Gustschin <agust@denx.de> Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 24 4月, 2018 1 次提交
-
-
由 Marek Vasut 提交于
Staticize the function since it's only used in mmc.c . Signed-off-by: NMarek Vasut <marek.vasut@gmail.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: Tom Rini <trini@konsulko.com>
-
- 23 4月, 2018 3 次提交
-
-
由 Masahiro Yamada 提交于
The last clock consumer in SPL, SD/eMMC driver, gave up using the clock driver. The clock driver is only used in U-Boot proper. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Masahiro Yamada 提交于
The size of SPL is hitting the limit (64KB) for uniphier_v7_defconfig. When booting from SD/eMMC, obviously its clock has been properly set up by the boot ROM. Acutually, no need to re-initialize the clock in SPL. Using a clock driver would generalize the SoC specific code, but solving the memory footprint problem would win. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Masahiro Yamada 提交于
I need to differentiate the clock handling for uniphier-sd. Move it to each driver's probe function from the tmio common code so that renesas-sdhi will not be affected. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-