24 May, 2019

4 commits


29 Mar, 2019

1 commit


13 Mar, 2019

1 commit


04 Mar, 2019

9 commits


25 Feb, 2019

1 commit


01 Feb, 2019

5 commits


30 Jan, 2019

1 commit


29 Jan, 2019

2 commits

  • Adding pinconf support is necessary to enable boot from SPI
    without breaking the eMMC. When booting from SPI, the ROM code
    leave pull downs on the eMMC pad.

    We need to set pinconf provided in DT to solve this

    Signed-off-by: Jerome Brunet
    Signed-off-by: Neil Armstrong
    [narmstrong: added missing comma in pinctrl-meson-axg-pmx.c]

    Jerome Brunet
     
  • The pinctrl supports to set any bit in input register on iMX6 if
    the MSB of input value is 0xff. But the driver uses signed int for
    input value, so when executing the codes below, it won't meet.
    Because this is arithmetic right shift.

    if (input_val >> 24 == 0xff)

    Fix the issue by changing the input_val, config_val and mux_mode to u32.

    Signed-off-by: Ye Li
    Reviewed-by: Fugang Duan
    Reviewed-by: Peng Fan

    Ye Li
     

24 Jan, 2019

2 commits


18 Jan, 2019

1 commit


16 Jan, 2019

1 commit


11 Jan, 2019

1 commit

  • This reverts commit a7f4b4b344396590845e6552c82829ef68ef9f89.

    As reported by Alex Kiernan the above optimization introduces a
    regression in the below use case where:

    1. Device has defined 'u-boot,dm-spl' property (@ eMMC DTS node)

    2. The device downloads its MLO/SPL via UART (not eMMC - the eMMC pinmux
    pins are NOT probed/configured in MLO/SPL).

    3. The loaded via UART MLO/SPL wants to load Linux from eMMC. In this case
    the DM core and pinctrl uclass checks 'u-boot,dm-spl' and don't
    configure pins (as it thinks that those were initialized in MLO/SPL).

    As we are very close to release - please revert this commit.

    Reported-by: Alex Kiernan
    Signed-off-by: Lukasz Majewski
    Reviewed-by: Simon Glass

    Lukasz Majewski
     

06 Jan, 2019

1 commit


03 Jan, 2019

3 commits

  • This patch adds a Kconfig option to enable the full pinctrl driver
    for the RK3399. This flag needs to be enabed in order to get the
    features of the full pinctrl driver compiled in (i.e. a .set_state()
    callback).

    Signed-off-by: Christoph Muellner
    Reviewed-by: Philipp Tomsich

    Christoph Muellner
     
  • The current pinctrl driver for the RK3399 has a range of qulity issues.
    E.g. it only implements the .set_state_simple() callback, it
    does not parse the available pinctrl information from the DTS
    (instead uses hardcoded values), is not flexible enough to cover
    devices without 'interrupt' field in the DTS (e.g. PWM),
    is not written generic enough to make code reusable among other
    rockchip SoCs...

    This patch addresses these issues by reimplementing the whole driver
    from scratch using the .set_state() callback.
    The new implementation covers all featurese of the old code
    (i.e. it supports pinmuxing and pullup/pulldown configuration).

    This patch has been tested on a RK3399-Q7 SoM (Puma).

    Signed-off-by: Christoph Muellner
    Reviewed-by: Philipp Tomsich

    Christoph Muellner
     
  • pinctrl_decode_pin_config_dm() is basically a feature-equivalent
    implementation of pinctrl_decode_pin_config(), which operates
    on struct udevice devices and uses the dev_read_*() API.

    Signed-off-by: Christoph Muellner
    Reviewed-by: Philipp Tomsich

    Christoph Muellner
     

01 Jan, 2019

2 commits


27 Dec, 2018

1 commit

  • This commit prevents from re-configuring pins if those were configured
    before relocation.

    Some pins - like UART or DDR must be setup before relocation
    (as they have 'u-boot,dm-pre-reloc' property set in DTS). Without this
    change, those pins are re-configured after relocation (pre_reloc_only = 0,
    so we do not "continue").
    Such behavior may be a problem for DDR PAD configuration, as they might
    be already leveled/tuned with original setup).

    Signed-off-by: Lukasz Majewski

    Lukasz Majewski
     

19 Dec, 2018

1 commit

  • This driver supports the pin and gpio controller found in the Ocelot and
    Luton SoCs.

    The driver was inspired from the pinctrl driver in Linux, but was
    simplified and was modified to allow supporting an other SoCs (Luton).

    For Ocelot and Luton the controller is the same, only the pins to program
    differ.

    Signed-off-by: Gregory CLEMENT
    Reviewed-by: Daniel Schwierzeck
    [changed to only descend into mscc/ dependent on CONFIG_PINCTRL_MSCC]
    Signed-off-by: Daniel Schwierzeck

    Gregory CLEMENT
     

08 Dec, 2018

1 commit


07 Dec, 2018

2 commits