mbox series

[v2,00/11] Add support for HiHope RZ/G2M[N] Rev.3.0/4.0

Message ID 1593004330-5039-1-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.com
Headers show
Series Add support for HiHope RZ/G2M[N] Rev.3.0/4.0 | expand

Message

Prabhakar Mahadev Lad June 24, 2020, 1:11 p.m. UTC
Hi All,

This patch series adds supports for HiHope RZ/G2M[N] Rev.3.0/4.0
boards.

Patches are based on top of renesas-arm-dt-for-v5.9 branch [1].

[1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git

Changes for v2:
* Added Reviewed-by tag from Geert
* Renamed hihope-common-rev2.dtsi to hihope-rev2.dtsi
* Added comment wrt SW43 in r8a774a1-hihope-rzg2m-rev2-ex.dts
* Renamed hihope-common-rev4.dtsi to hihope-rev4.dtsi
* LED node names in hihope-common.dtsi are updated according to Rev.4.0
* Removed extra line from patch 10/11

Cheers,
Prabhakar

Lad Prabhakar (11):
  arm64: dts: renesas: r8a774a1-hihope-rzg2m[-ex/-ex-idk-1110wr]: Rename
    HiHope RZ/G2M boards
  arm64: dts: renesas: r8a774b1-hihope-rzg2n[-ex]: Rename HiHope RZ/G2N
    boards
  arm64: dts: renesas: hihope-common: Separate out Rev.2.0 specific into
    hihope-common-rev2.dtsi file
  arm64: dts: renesas: Add HiHope RZ/G2M[N] Rev.3.0/4.0 specific into
    common file
  arm64: dts: renesas: Add HiHope RZ/G2M Rev.3.0/4.0 main board support
  arm64: dts: renesas: Add HiHope RZ/G2M Rev.3.0/4.0 sub board support
  arm64: dts: renesas: hihope-rzg2-ex: Separate out lvds specific nodes
    into common file
  arm64: dts: renesas: Add HiHope RZ/G2M Rev.3.0/4.0 board with
    idk-1110wr display
  arm64: dts: renesas: Add HiHope RZ/G2N Rev.3.0/4.0 main board support
  arm64: dts: renesas: Add HiHope RZ/G2N Rev.3.0/4.0 sub board support
  arm64: dts: renesas: Add HiHope RZ/G2N Rev2.0/3.0/4.0 board with
    idk-1110wr display

 arch/arm64/boot/dts/renesas/Makefile          |  17 ++-
 .../arm64/boot/dts/renesas/hihope-common.dtsi |  71 +---------
 arch/arm64/boot/dts/renesas/hihope-rev2.dtsi  |  86 ++++++++++++
 arch/arm64/boot/dts/renesas/hihope-rev4.dtsi  | 124 ++++++++++++++++++
 .../boot/dts/renesas/hihope-rzg2-ex-lvds.dtsi |  52 ++++++++
 .../boot/dts/renesas/hihope-rzg2-ex.dtsi      |  37 ------
 .../r8a774a1-hihope-rzg2m-ex-idk-1110wr.dts   |  43 +-----
 .../dts/renesas/r8a774a1-hihope-rzg2m-ex.dts  |   6 +-
 ...a774a1-hihope-rzg2m-rev2-ex-idk-1110wr.dts |  15 +++
 .../renesas/r8a774a1-hihope-rzg2m-rev2-ex.dts |  20 +++
 .../renesas/r8a774a1-hihope-rzg2m-rev2.dts    |  37 ++++++
 .../dts/renesas/r8a774a1-hihope-rzg2m.dts     |   6 +-
 arch/arm64/boot/dts/renesas/r8a774a1.dtsi     |   2 +
 .../r8a774b1-hihope-rzg2n-ex-idk-1110wr.dts   |  15 +++
 .../dts/renesas/r8a774b1-hihope-rzg2n-ex.dts  |   5 +-
 ...a774b1-hihope-rzg2n-rev2-ex-idk-1110wr.dts |  15 +++
 .../renesas/r8a774b1-hihope-rzg2n-rev2-ex.dts |  15 +++
 .../renesas/r8a774b1-hihope-rzg2n-rev2.dts    |  41 ++++++
 .../dts/renesas/r8a774b1-hihope-rzg2n.dts     |   6 +-
 arch/arm64/boot/dts/renesas/r8a774b1.dtsi     |   2 +
 20 files changed, 456 insertions(+), 159 deletions(-)
 create mode 100644 arch/arm64/boot/dts/renesas/hihope-rev2.dtsi
 create mode 100644 arch/arm64/boot/dts/renesas/hihope-rev4.dtsi
 create mode 100644 arch/arm64/boot/dts/renesas/hihope-rzg2-ex-lvds.dtsi
 create mode 100644 arch/arm64/boot/dts/renesas/r8a774a1-hihope-rzg2m-rev2-ex-idk-1110wr.dts
 create mode 100644 arch/arm64/boot/dts/renesas/r8a774a1-hihope-rzg2m-rev2-ex.dts
 create mode 100644 arch/arm64/boot/dts/renesas/r8a774a1-hihope-rzg2m-rev2.dts
 create mode 100644 arch/arm64/boot/dts/renesas/r8a774b1-hihope-rzg2n-ex-idk-1110wr.dts
 create mode 100644 arch/arm64/boot/dts/renesas/r8a774b1-hihope-rzg2n-rev2-ex-idk-1110wr.dts
 create mode 100644 arch/arm64/boot/dts/renesas/r8a774b1-hihope-rzg2n-rev2-ex.dts
 create mode 100644 arch/arm64/boot/dts/renesas/r8a774b1-hihope-rzg2n-rev2.dts

Comments

Pavel Machek July 17, 2020, 8:36 a.m. UTC | #1
Hi!

Can we have node names consistent with other systems?

> +	leds {

> +		compatible = "gpio-leds";

> +

> +		bt_active_led {

> +			label = "blue:bt";

> +			gpios = <&gpio7  0 GPIO_ACTIVE_HIGH>;

> +			linux,default-trigger = "hci0-power";

> +			default-state = "off";

> +		};

> +

> +		wlan_active_led {

> +			label = "yellow:wlan";

> +			gpios = <&gpio7  1 GPIO_ACTIVE_HIGH>;

> +			linux,default-trigger = "phy0tx";

> +			default-state = "off";

> +		};

> +	};


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Prabhakar July 17, 2020, 9:18 a.m. UTC | #2
Hi Pavel,

On Fri, Jul 17, 2020 at 9:36 AM Pavel Machek <pavel@ucw.cz> wrote:
>

> Hi!

>

> Can we have node names consistent with other systems?

>

> > +     leds {

> > +             compatible = "gpio-leds";

> > +

> > +             bt_active_led {

> > +                     label = "blue:bt";

> > +                     gpios = <&gpio7  0 GPIO_ACTIVE_HIGH>;

> > +                     linux,default-trigger = "hci0-power";

> > +                     default-state = "off";

> > +             };

> > +

> > +             wlan_active_led {

> > +                     label = "yellow:wlan";

> > +                     gpios = <&gpio7  1 GPIO_ACTIVE_HIGH>;

> > +                     linux,default-trigger = "phy0tx";

> > +                     default-state = "off";

> > +             };

> > +     };

>

Could you please point me to an example system which you are referring to?

Cheers,
--Prabhakar Lad

> --

> (english) http://www.livejournal.com/~pavelmachek

> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html