[GIT,PULL] Allwinner Device Tree Changes for 5.3
mbox series

Message ID 459c0bad-c02e-40f0-9e56-1dcdad9c6591.lettre@localhost
State New
Headers show
Series
  • [GIT,PULL] Allwinner Device Tree Changes for 5.3
Related show

Pull-request

https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807

Message

Maxime Ripard June 21, 2019, 8:08 a.m. UTC
Hi,

Please pull the following changes for the next release.

Thanks!
Maxime

The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:

  Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807

for you to fetch changes up to 2269f0c15191af317d64115176a01bf303532af3:

  dt-bindings: pwm: Convert Allwinner PWM to a schema (2019-06-21 09:59:10 +0200)

----------------------------------------------------------------
Our usual bunch of patches:
  - Some work on the BPi M2-Berry to support various devices
  - Convert some bindings to a schema, and a lot of fixes reported by
    the schemas we introduced.
  - A few other fixes here and there

----------------------------------------------------------------
Chen-Yu Tsai (1):
      ARM: dts: sun8i: a83t: Add device node for CSI (Camera Sensor Interface)

Jernej Skrabec (1):
      ARM: dts: sun8i-h3: Fix wifi in Beelink X2 DT

Maxime Ripard (11):
      dt-bindings: bus: Convert Allwinner RSB to a schema
      ARM: dts: sun6i: Add default address and size cells for SPI
      ARM: dts: sun8i: a711: Change LRADC node names to avoid warnings
      ARM: dts: sun7i: icnova-swac: Fix the model vendor
      ARM: dts: gr8-evb: Fix RTC vendor
      ARM: dts: sun6i: Fix RTC node
      ARM: dts: sun6i: Add external crystals accuracy
      ARM: dts: sun8i: v3s: Fix the RTC node
      ARM: dts: sun8i: v3s: Add external crystals accuracy
      ARM: dts: sun8i: r40: Change the RTC compatible
      dt-bindings: pwm: Convert Allwinner PWM to a schema

Pablo Greco (7):
      ARM: dts: sun8i: r40: bananapi-m2-ultra: Add GPIO pin-bank regulator supplies
      ARM: dts: sun8i: v40: bananapi-m2-berry: Add GPIO pin-bank regulator supplies
      ARM: dts: sun8i: v40: bananapi-m2-berry: Enable GMAC ethernet controller
      ARM: dts: sun8i: v40: bananapi-m2-berry: Enable HDMI output
      ARM: dts: sun8i: v40: bananapi-m2-berry: Enable AHCI
      ARM: dts: sun8i: v40: bananapi-m2-berry: Add Bluetooth device node
      ARM: dts: sun8i: r40: bananapi-m2-ultra: Remove regulator-always-on

Priit Laes (1):
      ARM: dts: sun7i: olimex-lime2: Enable ac and power supplies


 Documentation/devicetree/bindings/arm/sunxi.yaml                   |   2 +-
 Documentation/devicetree/bindings/bus/allwinner,sun8i-a23-rsb.yaml |  79 ++++-
 Documentation/devicetree/bindings/bus/sunxi-rsb.txt                |  47 +---
 Documentation/devicetree/bindings/pwm/allwinner,sun4i-a10-pwm.yaml |  57 +++-
 Documentation/devicetree/bindings/pwm/pwm-sun4i.txt                |  24 +-
 arch/arm/boot/dts/sun5i-gr8-evb.dts                                |   2 +-
 arch/arm/boot/dts/sun6i-a31.dtsi                                   |  25 +-
 arch/arm/boot/dts/sun7i-a20-icnova-swac.dts                        |   3 +-
 arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts                    |   8 +-
 arch/arm/boot/dts/sun8i-a83t-tbs-a711.dts                          |   4 +-
 arch/arm/boot/dts/sun8i-a83t.dtsi                                  |  29 ++-
 arch/arm/boot/dts/sun8i-h3-beelink-x2.dts                          |   4 +-
 arch/arm/boot/dts/sun8i-r40-bananapi-m2-ultra.dts                  |   7 +-
 arch/arm/boot/dts/sun8i-r40.dtsi                                   |   3 +-
 arch/arm/boot/dts/sun8i-v3s.dtsi                                   |  13 +-
 arch/arm/boot/dts/sun8i-v40-bananapi-m2-berry.dts                  | 123 +++++++-
 16 files changed, 341 insertions(+), 89 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/bus/allwinner,sun8i-a23-rsb.yaml
 delete mode 100644 Documentation/devicetree/bindings/bus/sunxi-rsb.txt
 create mode 100644 Documentation/devicetree/bindings/pwm/allwinner,sun4i-a10-pwm.yaml
 delete mode 100644 Documentation/devicetree/bindings/pwm/pwm-sun4i.txt

Comments

Olof Johansson June 25, 2019, 11:41 a.m. UTC | #1
On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote:
> Hi,
> 
> Please pull the following changes for the next release.
> 
> Thanks!
> Maxime
> 
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> 
>   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807

You know, there's a timestamp in the tag too, no need to encode it in the name.

> 
> for you to fetch changes up to 2269f0c15191af317d64115176a01bf303532af3:
> 
>   dt-bindings: pwm: Convert Allwinner PWM to a schema (2019-06-21 09:59:10 +0200)
> 
> ----------------------------------------------------------------
> Our usual bunch of patches:
>   - Some work on the BPi M2-Berry to support various devices
>   - Convert some bindings to a schema, and a lot of fixes reported by
>     the schemas we introduced.
>   - A few other fixes here and there

Merged, thanks.


-Olof
Maxime Ripard June 25, 2019, 12:32 p.m. UTC | #2
Hi Olof,

On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote:
> On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote:
> > Hi,
> >
> > Please pull the following changes for the next release.
> >
> > Thanks!
> > Maxime
> >
> > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> >
> >   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> >
> > are available in the Git repository at:
> >
> >   https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807
>
> You know, there's a timestamp in the tag too, no need to encode it in the name.

Yeah, I've switched to some tooling to send them instead of doing them
manually, and having a timestamp was the easiest solution to avoid a
collision, but I guess having it down to the minute was a bit
overkill. Do you have any preference on this?

Thanks!
Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Olof Johansson June 25, 2019, 12:36 p.m. UTC | #3
On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>
> Hi Olof,
>
> On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote:
> > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote:
> > > Hi,
> > >
> > > Please pull the following changes for the next release.
> > >
> > > Thanks!
> > > Maxime
> > >
> > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> > >
> > >   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > >   https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807
> >
> > You know, there's a timestamp in the tag too, no need to encode it in the name.
>
> Yeah, I've switched to some tooling to send them instead of doing them
> manually, and having a timestamp was the easiest solution to avoid a
> collision, but I guess having it down to the minute was a bit
> overkill. Do you have any preference on this?

Main thing for me is that I can't tell from time timestamps if it's a
respin/new version, or a re-stamp, i.e. if it's something I should
care about or not.

I.e. it doesn't carry any useful signal for the consuming side and is
mostly noise.


-Olof
Maxime Ripard June 25, 2019, 2:55 p.m. UTC | #4
On Tue, Jun 25, 2019 at 02:36:30PM +0200, Olof Johansson wrote:
> On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> >
> > Hi Olof,
> >
> > On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote:
> > > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote:
> > > > Hi,
> > > >
> > > > Please pull the following changes for the next release.
> > > >
> > > > Thanks!
> > > > Maxime
> > > >
> > > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> > > >
> > > >   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > >   https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807
> > >
> > > You know, there's a timestamp in the tag too, no need to encode it in the name.
> >
> > Yeah, I've switched to some tooling to send them instead of doing them
> > manually, and having a timestamp was the easiest solution to avoid a
> > collision, but I guess having it down to the minute was a bit
> > overkill. Do you have any preference on this?
>
> Main thing for me is that I can't tell from time timestamps if it's a
> respin/new version, or a re-stamp, i.e. if it's something I should
> care about or not.
>
> I.e. it doesn't carry any useful signal for the consuming side and is
> mostly noise.

Ok, so you'd prefer something like <tag>, <tag>-2 if there's multiple,
subsequent, PR, and <tag>, <tag>-again if the latter replaces the former?

Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Olof Johansson June 27, 2019, 2:09 a.m. UTC | #5
On Tue, Jun 25, 2019 at 10:55 PM Maxime Ripard
<maxime.ripard@bootlin.com> wrote:
>
> On Tue, Jun 25, 2019 at 02:36:30PM +0200, Olof Johansson wrote:
> > On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> > >
> > > Hi Olof,
> > >
> > > On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote:
> > > > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote:
> > > > > Hi,
> > > > >
> > > > > Please pull the following changes for the next release.
> > > > >
> > > > > Thanks!
> > > > > Maxime
> > > > >
> > > > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> > > > >
> > > > >   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> > > > >
> > > > > are available in the Git repository at:
> > > > >
> > > > >   https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807
> > > >
> > > > You know, there's a timestamp in the tag too, no need to encode it in the name.
> > >
> > > Yeah, I've switched to some tooling to send them instead of doing them
> > > manually, and having a timestamp was the easiest solution to avoid a
> > > collision, but I guess having it down to the minute was a bit
> > > overkill. Do you have any preference on this?
> >
> > Main thing for me is that I can't tell from time timestamps if it's a
> > respin/new version, or a re-stamp, i.e. if it's something I should
> > care about or not.
> >
> > I.e. it doesn't carry any useful signal for the consuming side and is
> > mostly noise.
>
> Ok, so you'd prefer something like <tag>, <tag>-2 if there's multiple,
> subsequent, PR, and <tag>, <tag>-again if the latter replaces the former?

Yeah, that's what a lot of other maintainers do and it's something
that's been working pretty well.

Sometimes they use -v2 at the end for respins, i.e. dt-2-v2 etc. I
recommend deleting respun tags so we don't accidentally merge them (if
we didn't see the follow-up).



-Olof
Maxime Ripard June 27, 2019, 8:43 a.m. UTC | #6
On Thu, Jun 27, 2019 at 10:09:53AM +0800, Olof Johansson wrote:
> On Tue, Jun 25, 2019 at 10:55 PM Maxime Ripard
> <maxime.ripard@bootlin.com> wrote:
> >
> > On Tue, Jun 25, 2019 at 02:36:30PM +0200, Olof Johansson wrote:
> > > On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> > > >
> > > > Hi Olof,
> > > >
> > > > On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote:
> > > > > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote:
> > > > > > Hi,
> > > > > >
> > > > > > Please pull the following changes for the next release.
> > > > > >
> > > > > > Thanks!
> > > > > > Maxime
> > > > > >
> > > > > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> > > > > >
> > > > > >   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> > > > > >
> > > > > > are available in the Git repository at:
> > > > > >
> > > > > >   https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807
> > > > >
> > > > > You know, there's a timestamp in the tag too, no need to encode it in the name.
> > > >
> > > > Yeah, I've switched to some tooling to send them instead of doing them
> > > > manually, and having a timestamp was the easiest solution to avoid a
> > > > collision, but I guess having it down to the minute was a bit
> > > > overkill. Do you have any preference on this?
> > >
> > > Main thing for me is that I can't tell from time timestamps if it's a
> > > respin/new version, or a re-stamp, i.e. if it's something I should
> > > care about or not.
> > >
> > > I.e. it doesn't carry any useful signal for the consuming side and is
> > > mostly noise.
> >
> > Ok, so you'd prefer something like <tag>, <tag>-2 if there's multiple,
> > subsequent, PR, and <tag>, <tag>-again if the latter replaces the former?
>
> Yeah, that's what a lot of other maintainers do and it's something
> that's been working pretty well.
>
> Sometimes they use -v2 at the end for respins, i.e. dt-2-v2 etc. I
> recommend deleting respun tags so we don't accidentally merge them (if
> we didn't see the follow-up).

Ok, I'll adjust my program to do so next time then, thanks!
Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com