All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	devicetree@vger.kernel.org, robh+dt@kernel.org,
	mark.rutland@arm.com, linux@armlinux.org.uk,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Use macros to describe gpios on rockchip platform
Date: Fri, 30 Dec 2016 13:31:27 +0100	[thread overview]
Message-ID: <1558490.gPc1QP0JTO@phil> (raw)
In-Reply-To: <1477140706-6886-1-git-send-email-andy.yan@rock-chips.com>

Am Samstag, 22. Oktober 2016, 20:51:46 CET schrieb Andy Yan:
> As patch 150696e2e3a4("Add GPIO pin index definition for rockchip pinctrl")
> has been applied, now we can use these macros to describe the corresponding
> gpio ranther than hard code numbers, this will make the dts easier to read
> and write.
> 
> Some ideas from Krzysztof's patch on EXYNOS[0].
> 
> [0]https://lkml.org/lkml/2016/9/4/71
> 
> 
> 
> Andy Yan (2):
>   ARM: dts: rockchip: use pin constants to describe gpios
>   ARM64: dts: rockchip: use pin constants to describe gpios

applied to dts branches for 4.11
I've also adapted the gpio interrupts accordingly inside the patches.


Thanks
Heiko

WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Use macros to describe gpios on rockchip platform
Date: Fri, 30 Dec 2016 13:31:27 +0100	[thread overview]
Message-ID: <1558490.gPc1QP0JTO@phil> (raw)
In-Reply-To: <1477140706-6886-1-git-send-email-andy.yan@rock-chips.com>

Am Samstag, 22. Oktober 2016, 20:51:46 CET schrieb Andy Yan:
> As patch 150696e2e3a4("Add GPIO pin index definition for rockchip pinctrl")
> has been applied, now we can use these macros to describe the corresponding
> gpio ranther than hard code numbers, this will make the dts easier to read
> and write.
> 
> Some ideas from Krzysztof's patch on EXYNOS[0].
> 
> [0]https://lkml.org/lkml/2016/9/4/71
> 
> 
> 
> Andy Yan (2):
>   ARM: dts: rockchip: use pin constants to describe gpios
>   ARM64: dts: rockchip: use pin constants to describe gpios

applied to dts branches for 4.11
I've also adapted the gpio interrupts accordingly inside the patches.


Thanks
Heiko

  parent reply	other threads:[~2016-12-30 12:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22 12:51 [PATCH 0/2] Use macros to describe gpios on rockchip platform Andy Yan
2016-10-22 12:51 ` Andy Yan
2016-10-22 12:51 ` Andy Yan
2016-10-22 12:54 ` [PATCH 1/2] ARM: dts: rockchip: use pin constants to describe gpios Andy Yan
2016-10-22 12:54   ` Andy Yan
     [not found] ` <1477140706-6886-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-10-22 12:59   ` [PATCH 2/2] ARM64: " Andy Yan
2016-10-22 12:59     ` Andy Yan
2016-10-22 12:59     ` Andy Yan
2016-12-30 12:31 ` Heiko Stuebner [this message]
2016-12-30 12:31   ` [PATCH 0/2] Use macros to describe gpios on rockchip platform Heiko Stuebner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1558490.gPc1QP0JTO@phil \
    --to=heiko@sntech.de \
    --cc=andy.yan@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.