05 Mar, 2018
1 commit
-
Thomas reported U-Boot failed to build host tools if libfdt-devel
package is installed because tools include libfdt headers from
/usr/include/ instead of using internal ones.This commit moves the header code:
include/libfdt.h -> include/linux/libfdt.h
include/libfdt_env.h -> include/linux/libfdt_env.hand replaces include directives:
#include -> #include
#include -> #includeReported-by: Thomas Petazzoni
Signed-off-by: Masahiro Yamada
19 Sep, 2017
2 commits
-
After Simon's patch, the dtoc can work with 64bit address,
so we need to fix reg number for it.
Depend on Simon's patch set:
https://patchwork.ozlabs.org/cover/807266/Signed-off-by: Kever Yang
Acked-by: Philipp Tomsich -
Update the Rockchip SDHCI wrapper to support a live device tree.
Signed-off-by: Philipp Tomsich
Reviewed-by: Simon Glass
Acked-by: Philipp TomsichVersion-changes: 2
- use the dev_read_addr_ptr function in rockchip_sdhci.c
11 Jul, 2017
1 commit
-
With the new dev_read functions available, we can convert the rockchip
architecture-specific drivers and common drivers used by these devices
over to the dev_read family of calls.This covers the dw_mmc and sdhci wrapper drivers for Rockchip.
Signed-off-by: Philipp Tomsich
Reviewed-by: Simon Glass
01 Jun, 2017
1 commit
-
These support the flat device tree. We want to use the dev_read_..()
prefix for functions that support both flat tree and live tree. So rename
the existing functions to avoid confusion.In the end we will have:
1. dev_read_addr...() - works on devices, supports flat/live tree
2. devfdt_get_addr...() - current functions, flat tree only
3. of_get_address() etc. - new functions, live tree onlyAll drivers will be written to use 1. That function will in turn call
either 2 or 3 depending on whether the flat or live tree is in use.Note this involves changing some dead code - the imx_lpi2c.c file.
Signed-off-by: Simon Glass
17 Mar, 2017
1 commit
-
Change some API in order to enable of-platdata.
Signed-off-by: Kever Yang
Reviewed-by: Simon Glass
Added rockchip tag:
Signed-off-by: Simon Glass
08 Feb, 2017
1 commit
-
At present devices use a simple integer offset to record the device tree
node associated with the device. In preparation for supporting a live
device tree, which uses a node pointer instead, refactor existing code to
access this field through an inline function.Signed-off-by: Simon Glass
23 Jan, 2017
1 commit
-
The sdhci controller assumes that the base clock frequency is fully supported by
the peripheral and doesn't support hardware limitations. The Linux kernel
distinguishes between base clock (max_clk) of the host controller and maximum
frequency (f_max) of the card interface. Use the same differentiation and allow
the platform to constrain the peripheral interface.Signed-off-by: Stefan Herbrechtsmeier
12 Jan, 2017
1 commit
-
Init the clock rate to max-frequency from dts with clock driver api.
Signed-off-by: Kever Yang
Reviewed-by: Jaehoon Chung
24 Sep, 2016
1 commit
-
These functions can be much simpler by squashing lines for immediate
return.For *_bind() callbacks, they will be a simple wrapper function of an
upper-level bind API.For mmc_set_{boot_bus_width,part_conf}, they will be a wrapper of
mmc_switch().Signed-off-by: Masahiro Yamada
Reviewed-by: Jaehoon Chung
05 Aug, 2016
1 commit
-
Some arguments don't need to pass to sdhci_setup_cfg.
Generic variable can be used in sdhci_setup_cfg, and some arguments are
already included in sdhci_host struct.It's enough that just pass the board specific things to sdhci_setup_cfg().
After removing the unnecessary arguments, it's more simpler than before.
It doesn't consider "Version" and "Capabilities" anymore in each SoC
driver.Signed-off-by: Jaehoon Chung
Reviewed-by: Simon Glass
26 Jul, 2016
1 commit
-
Rockchip rk3399 using arasan sdhci-5.1 controller.
This patch add the controller support to enable mmc device
with full driver-model support, tested on rk3399 evb board.According to my test result, this driver should be OK,
the command "part list mmc 0" can result in a right output,
but all the mmc command failed like this:
=> mmc info
No MMC device available
Command failed, result=1The result of get_mmc_num in cmd/mmc.c is always 0?
Signed-off-by: Kever Yang
Acked-by: Simon Glass