Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 160
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 16 5月, 2017 1 次提交
  3. 24 11月, 2016 1 次提交
  5. 18 11月, 2016 1 次提交
  7. 16 9月, 2016 1 次提交
  9. 02 9月, 2016 2 次提交
  11. 25 8月, 2016 1 次提交
    • M
      ARM: dts: exynos: Use 'hpd-gpios' instead of 'hpd-gpio' · 05b01dd9
      由 Milo Kim 提交于 
      This patch enables getting a HPD GPIO descriptor quicker.
The exynos-hdmi driver uses "hpd" for HDMI hot plug detection.

	static int hdmi_resources_init(struct hdmi_context *hdata)
	{
		...
		hdata->hpd_gpio = devm_gpiod_get(dev, "hpd", GPIOD_IN);
		...
	}

This calls 'of_find_gpio()' and it generates the GPIO consumer ID by referring
GPIO suffix. So 'hpd-gpios' is preferred on getting a GPIO descriptor.

However, if the device tree uses 'hpd-gpio', then the exynos-hdmi driver
always retries to get a GPIO descriptor because the first GPIO suffix is not
'gpio' but 'gpios'. So you always see the debug message below.

	of_get_named_gpiod_flags: can't parse 'hpd-gpios' property of node '/soc/hdmi@14530000[0]'

Use the preferred property, 'hpd-gpios' instead of 'hpd-gpio'.
Acked-by: NRob Herring <robh@kernel.org>
Reviewed-by: NAndrzej Hajda <a.hajda@samsung.com>
Cc: devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-samsung-soc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: NMilo Kim <woogyom.kim@gmail.com>
Signed-off-by: NKrzysztof Kozlowski <krzk@kernel.org>
      05b01dd9
  13. 19 8月, 2016 1 次提交
  15. 08 6月, 2016 1 次提交
  17. 06 6月, 2016 2 次提交
  19. 30 5月, 2016 1 次提交
  21. 03 5月, 2016 1 次提交
  23. 27 4月, 2016 1 次提交
  25. 13 4月, 2016 1 次提交
  27. 28 1月, 2016 1 次提交
  29. 29 12月, 2015 1 次提交
  31. 08 10月, 2015 1 次提交
  33. 17 9月, 2015 4 次提交
  35. 14 8月, 2015 1 次提交
  37. 21 7月, 2015 4 次提交
  39. 03 6月, 2015 4 次提交
  41. 17 5月, 2015 2 次提交
  43. 13 5月, 2015 1 次提交
  45. 09 5月, 2015 2 次提交
  47. 27 2月, 2015 2 次提交
    • J
      ARM: dts: Mux XMMCnDATA[0] pad correctly for Exynos5420 boards · af6ad88a
      由 Javier Martinez Canillas 提交于 
      The Exynos5420 SoC has 3 sets of 8 pads used as data lines for the 3
MMC/SD/SDIO slots. These needs to be muxed as SD_n_DATA instead of a
GPIO or external interrupt to allow the MMC controller to communicate
with the attached cards or SDIO devices.

Which data lines needs to be muxed as SD_n_DATA depends on the bus
width used for data transfer:

* bus-width = <1> needs SD_n_DATA[0]
* bus-width = <4> needs SD_n_DATA[0-3]
* bus-width = <8> needs SD_n_DATA[0-7]

The Exynos5250-pinctrl.dtsi file that defines the groups of pins has
SD_n_DATA[0] muxed for both sdn_bus1 and sdn_bus4 so just one of them
needs to be included in the device node's pinctrl property.

But Exynos5420-pinctrl has a different definition and only includes
SD_n_DATA[1-3] for sdn_bus4. So for a bus-width = <4>, both sdn_bus1
and sdn_bus4 have to be in the dev pinctrl to mux all the needed pads.

It seems all Exynos5420 boards had just cargo cult the pinctrl lines
assuming that sdn_bus4 also included SD_n_DATA[0] and it only works
because the bootloader muxes the pads correctly. But that is not the
case for the devices not used by the bootloader such as WiFi modules.

Add sdn_bus1 too in the nodes pinctrl to not rely on the bootloader.
Suggested-by: NDoug Anderson <dianders@chromium.org>
Signed-off-by: NJavier Martinez Canillas <javier.martinez@collabora.co.uk>
Signed-off-by: NKukjin Kim <kgene@kernel.org>
      af6ad88a
    • M
      ARM: dts: add eMMC reset line for exynos5422-odroidxu3 · 1056a273
      由 Marek Szyprowski 提交于 
      This patch adds reset-gpios property to the eMMC slot, so the MMC driver
is able to properly reset eMMC card on system restart and thus fixes
system hang on software reboot.
Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: NKukjin Kim <kgene@kernel.org>
      1056a273
  49. 24 1月, 2015 2 次提交