29 Jan, 2018

1 commit

  • The bcm283x family of SoCs have a GPIO controller that also acts as
    pinctrl controller.

    This patch introduces a new pinctrl driver that can actually properly mux
    devices into their device tree defined pin states and is now the primary
    owner of the gpio device. The previous GPIO driver gets moved into a
    subdevice of the pinctrl driver, bound to the same OF node.

    That way whenever a device asks for pinctrl support, it gets it
    automatically from the pinctrl driver and GPIO support is still available
    in the normal command line phase.

    Signed-off-by: Alexander Graf

    Alexander Graf
     

10 May, 2017

5 commits


29 Nov, 2016

1 commit

  • The rpi has a pretty simple way of resetting the whole system. All it takes
    is to poke a few registers at a well defined location in MMIO space.

    This patch adds support for the EFI loader implementation to allow an OS to
    reset and power off the system when we're outside of boot time.

    Signed-off-by: Alexander Graf

    Alexander Graf
     

07 Sep, 2016

1 commit

  • So far we could only tell the gpio framework that a GPIO was mapped as input or
    output, not as alternative function.

    This patch adds support for determining whether a function is mapped as
    alternative.

    Signed-off-by: Alexander Graf
    Reviewed-by: Simon Glass
    Acked-by: Stephen Warren

    Alexander Graf
     

27 Mar, 2016

1 commit

  • Currently, CONFIG_BCM2835 is defined for all BCM283x builds and _BCM2836
    is defined when building for that SoC. That means there isn't a single
    define that means "exactly BCM2835". This will complicate future patches
    where BCM2835-vs-anything-else needs to be determined simply.

    Modify the code to define one or the other of CONFIG_BCM2835/BCM2836 so
    future patches are simpler.

    Signed-off-by: Stephen Warren
    Reviewed-by: Tom Rini

    Stephen Warren
     

25 Feb, 2016

1 commit


06 Dec, 2015

1 commit

  • There are two numbering schemes for the RPi revision values; old and new
    scheme. The values within each scheme overlap. Hence, it doesn't make
    sense to have absolute/global names for the revision IDs. Get rid of the
    names and just use the raw revision/type values to set up the array of
    per-revision data.

    This change makes most sense when coupled with the next change. However,
    it's split out so that the mechanical cut/paste is separate from the
    logic changes for easier review and problem bisection.

    Signed-off-by: Stephen Warren

    Stephen Warren
     

19 Oct, 2015

1 commit


13 Aug, 2015

1 commit


28 May, 2015

2 commits


13 Apr, 2015

1 commit

  • According to Gordon Henderson's WiringPi library, there are some more
    Pi revision IDs out there. Add support for them.

    http://git.drogon.net/?p=wiringPi;a=blob_plain;f=wiringPi/wiringPi.c;hb=5edd177112c99416f68ba3e8c6c4db6ed942e796

    At least ID 0x13 is out in the wild:

    Reported-by: Chee-Yang Chau
    Signed-off-by: Stephen Warren

    Stephen Warren
     

28 Mar, 2015

1 commit