linux-toradex.git/drivers/pinctrl/samsung, branch v4.10

pinctrl: samsung: Fix the width of PINCFG_TYPE_DRV bitfields for Exynos5433

2016-12-30T13:27:42+00:00

This patch fixes the wrong width of PINCFG_TYPE_DRV bitfields for Exynos5433
because PINCFG_TYPE_DRV of Exynos5433 has 4bit fields in the *_DRV
registers. Usually, other Exynos have 2bit field for PINCFG_TYPE_DRV.

Fixes: 3c5ecc9ed353 ("pinctrl: exynos: Add support for Exynos5433")
Cc: stable@vger.kernel.org
Cc: Tomasz Figa 
Cc: Krzysztof Kozlowski 
Cc: Sylwester Nawrocki 
Cc: Linus Walleij 
Cc: Kukjin Kim 
Cc: Javier Martinez Canillas 
Signed-off-by: Chanwoo Choi 
Signed-off-by: Linus Walleij

pinctrl: samsung: Add GPF support for Exynos5433

2016-11-15T08:42:44+00:00

This patch add the support of GPF[1-5] pin of Exynos5433 SoC. The GPFx need
to support the multiple memory map because the registers of GPFx are located
in the different domain.

Cc: Linus Walleij 
Cc: Rob Herring 
Cc: Mark Rutland 
Cc: Tomasz Figa 
Cc: Krzysztof Kozlowski 
Cc: Sylwester Nawrocki 
Cc: Kukjin Kim 
Cc: linux-gpio@vger.kernel.org
Signed-off-by: Joonyoung Shim 
Signed-off-by: Chanwoo Choi 
Signed-off-by: Linus Walleij

pinctrl: samsung: Add the support the multiple IORESOURCE_MEM for one pin-bank

2016-11-15T08:41:35+00:00

This patch supports the multiple IORESOURCE_MEM resources for one pin-bank.
In the pre-existing Exynos series, the registers of the gpio bank are included
in the one memory map. But, some gpio bank need to support the one more memory
map (IORESOURCE_MEM) because the registers of gpio bank are separated into
the different memory map.

For example,
The both ALIVE and IMEM domain have the different memory base address.
The GFP[1-5] of exynos5433 are composed as following:
- ALIVE domain : WEINT_* registers
- IMEM domain  : CON/DAT/PUD/DRV/CONPDN/PUDPDN register

Cc: Linus Walleij 
Cc: Rob Herring 
Cc: Mark Rutland 
Cc: Tomasz Figa 
Cc: Krzysztof Kozlowski 
Cc: Sylwester Nawrocki 
Cc: Kukjin Kim 
Cc: linux-gpio@vger.kernel.org
Suggested-by: Tomasz Figa 
Signed-off-by: Chanwoo Choi 
Reviewed-by: Krzysztof Kozlowski 
Signed-off-by: Linus Walleij

Merge branch 'fixes' into devel

2016-09-23T15:41:40+00:00

pinctrl: samsung: Remove an always false dev->of_node test

2016-09-12T13:45:16+00:00

samsung_pinctrl_probe() can be called only after matching
the driver by the compatible string so this already implies
a non null dev->of_node.  Remove the always false test
and related error trace. While at it drop another error log
in case of memory allocation failure - any errors are logged
by the memory subsystem.

Signed-off-by: Sylwester Nawrocki 
Reviewed-by: Krzysztof Kozlowski 
Signed-off-by: Linus Walleij

pinctrl: exynos: remove duplicate calls in irq handler

2016-08-22T12:06:29+00:00

Because chained_irq_enter() has already called chip->irq_mask() and
chip->irq_ack(), also chained_irq_exit() will call chip->irq_unmask(),
so it's not necessary to call chip->irq_*() here.

Signed-off-by: Perr Zhang 
Acked-by: Tomasz Figa 
Reviewed-by: Krzysztof Kozlowski 
[Hand-edited from whitespace damaged patch]
Signed-off-by: Linus Walleij

pinctrl: samsung: Suppress unbinding to prevent theoretical attacks

2016-05-30T07:41:49+00:00

Although unbinding a pinctrl driver requires root privileges but it
still might be used theoretically in certain attacks (by triggering NULL
pointer exception or memory corruption).

Samsung pincontrol drivers are essential for system operation so their
removal is not expected. They do not implement remove() driver callback
and they are not buildable as modules.

Suppression of the unbinding will prevent triggering NULL pointer
exception like this (Odroid XU3):

  $ echo 13400000.pinctrl > /sys/bus/platform/drivers/samsung-pinctrl/unbind
  $ cat /sys/kernel/debug/gpio

  Unable to handle kernel NULL pointer dereference at virtual address 00000c44
  pgd = ec41c000
  [00000c44] *pgd=6d448835, *pte=00000000, *ppte=00000000
  Internal error: Oops: 17 [#1] PREEMPT SMP ARM
    (samsung_gpio_get) from [] (gpiolib_seq_show+0x1b0/0x26c)
    (gpiolib_seq_show) from [] (seq_read+0x304/0x4b8)
    (seq_read) from [] (full_proxy_read+0x4c/0x64)
    (full_proxy_read) from [] (__vfs_read+0x2c/0x110)
    (__vfs_read) from [] (vfs_read+0x8c/0x110)
    (vfs_read) from [] (SyS_read+0x40/0x8c)
    (SyS_read) from [] (ret_fast_syscall+0x0/0x3c)

Suggested-by: Marek Szyprowski 
Signed-off-by: Krzysztof Kozlowski 
Reviewed-by: Javier Martinez Canillas 
Signed-off-by: Linus Walleij

pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range

2016-04-26T13:52:46+00:00

The range is registered into a linked list which can be referenced
throughout the lifetime of the driver. Ensure the range's memory is useful
for the same lifetime by adding it to the driver's private data structure.

The bug was introduced in the driver's initial commit, which was present in
v3.10.

Fixes: f0b9a7e521fa ("pinctrl: exynos5440: add pinctrl driver for Samsung EXYNOS5440 SoC")
Cc: stable@vger.kernel.org
Signed-off-by: Andrew Jeffery 
Acked-by: Tomasz Figa 
Reviewed-by: Krzysztof Kozlowski 
Signed-off-by: Linus Walleij

pinctrl: samsung: Use devm_pinctrl_register() for pinctrl registration

2016-04-20T22:03:11+00:00

Use devm_pinctrl_register() for pin control registration.

Signed-off-by: Laxman Dewangan 
Cc: Tomasz Figa 
Cc: Kukjin Kim 
Cc: Krzysztof Kozlowski 
Signed-off-by: Linus Walleij

pinctrl: exynos5440: Use devm_pinctrl_register() for pinctrl registration

2016-04-20T22:03:08+00:00

Use devm_pinctrl_register() for pin control registration.

Signed-off-by: Laxman Dewangan 
Cc: Tomasz Figa 
Cc: Kukjin Kim 
Cc: Krzysztof Kozlowski 
Signed-off-by: Linus Walleij