| Age | Commit message (Collapse) | Author |
|---|
|
dev_read_addr_ptr had different semantics depending on whether OF_LIVE was
enabled. This patch converts both implementations to return NULL on error,
and converts all call sites which check for FDT_ADDR_T_NONE to check for
NULL instead. This patch also removes the call to map_physmem, since we
have dev_remap_addr* for those semantics.
Signed-off-by: Sean Anderson <[email protected]>
Reviewed-by: Bin Meng <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
|
|
Move this uncommon header out of the common header.
Signed-off-by: Simon Glass <[email protected]>
|
|
Due to the pinctrl hardware of MT7622 is difference from others
SoC which using the common part of mediatek pinctrl.
So we need to modify the common part of mediatek pinctrl.
Signed-off-by: Sam Shih <[email protected]>
Reviewed-by: Ryder Lee <[email protected]>
|
|
This patch add Pinctrl driver for MediaTek MT7622 SoC.
Signed-off-by: Sam Shih <[email protected]>
Reviewed-by: Ryder Lee <[email protected]>
|
|
Add Pinctrl driver for MediaTek MT8512 SoC.
Signed-off-by: mingming lee <[email protected]>
|
|
Add Pinctrl driver for MediaTek MT8518 SoC.
Signed-off-by: mingming lee <[email protected]>
|
|
Fix the following warning when CONFIG_PINCONF=n:
drivers/pinctrl/mediatek/pinctrl-mtk-common.c:35:36:
warning: ‘mtk_drive’ defined but not used [-Wunused-const-variable=]
static const struct mtk_drive_desc mtk_drive[] = {
^~~~~~~~~
Signed-off-by: Fabien Parent <[email protected]>
|
|
Add Pinctrl driver for MediaTek MT8516 SoC.
Signed-off-by: Fabien Parent <[email protected]>
Acked-by: Ryder Lee <[email protected]>
|
|
This patch adds pinctrl support for MT7623 SoC. And most of the
structures are used to hold the hardware configuration for each
pin.
Signed-off-by: Ryder Lee <[email protected]>
Tested-by: Matthias Brugger <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
|
|
This patch adds pinctrl support for MT7629 SoC. The IO core found on
the SoC has the registers for pinctrl, pinconf and gpio mixed up in
the same register range. Hence the driver also implements the gpio
functionality through UCLASS_GPIO.
This also creates a common file as there might be other chips that use
the same binding and driver, then being a little more abstract could
help in the long run.
Signed-off-by: Ryder Lee <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
|
