Message ID | d4897c4a92319527c46147244282803cd9f5a1ff.camel@v3.sk (mailing list archive) |
---|---|
State | Mainlined |
Commit | bae92f330aecba59bb5738e75ee25719f73a5c58 |
Headers | show |
Series | [GIT,PULL] soc/arm/dt: Marvell MMP Device Tree changes for v5.5 | expand |
On Thu, Oct 17, 2019 at 04:35:38PM +0200, Lubomir Rintel wrote: > Hi, > > Please pull the Device Tree changes for the MMP SoC. > > The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: > > Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/lkundrak/linux-mmp.git tags/mmp-dt-for-v5.5 > > for you to fetch changes up to 5c272bee843e12e4a3a2cc38881fdf31874806e0: > > ARM: dts: mmp3: Add MMP3 SoC dts file (2019-10-17 16:18:28 +0200) > > This supersedes the "[GIT PULL] ARM: soc: Marvell MMP changes for v5.5" pull > request. > > Thanks, > Lubo > > ---------------------------------------------------------------- > ARM: Marvell MMP Device Tree patches for v5.5 > > This tag includes binding documentation for various hardware found on Marvell > MMP3 SoC along a DTS file for said hardware. > > ---------------------------------------------------------------- > Lubomir Rintel (6): > dt-bindings: arm: cpu: Add Marvell MMP3 SMP enable method > dt-bindings: arm: Convert Marvell MMP board/soc bindings to json-schema > dt-bindings: arm: mrvl: Document MMP3 compatible string > dt-bindings: mrvl,intc: Add a MMP3 interrupt controller > dt-bindings: phy-mmp3-usb: Add bindings > ARM: dts: mmp3: Add MMP3 SoC dts file > > Documentation/devicetree/bindings/arm/cpus.yaml | 1 + > .../devicetree/bindings/arm/mrvl/mrvl.txt | 14 - > .../devicetree/bindings/arm/mrvl/mrvl.yaml | 35 ++ > .../bindings/interrupt-controller/mrvl,intc.txt | 14 +- > .../devicetree/bindings/phy/phy-mmp3-usb.txt | 13 + > arch/arm/boot/dts/mmp3.dtsi | 527 +++++++++++++++++++++ Hi, I only see a dtsi here. Do you have an early/partial dts for an actual piece of hardware that also can go in, so we get build coverage of the dtsi, etc? Merging this as-is, but please follow up with one if you can -- even if it's not complete yet. -Olof
On Mon, 2019-10-21 at 15:27 -0700, Olof Johansson wrote: > On Thu, Oct 17, 2019 at 04:35:38PM +0200, Lubomir Rintel wrote: > > Hi, > > > > Please pull the Device Tree changes for the MMP SoC. > > > > The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: > > > > Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) > > > > are available in the Git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/lkundrak/linux-mmp.git tags/mmp-dt-for-v5.5 > > > > for you to fetch changes up to 5c272bee843e12e4a3a2cc38881fdf31874806e0: > > > > ARM: dts: mmp3: Add MMP3 SoC dts file (2019-10-17 16:18:28 +0200) > > > > This supersedes the "[GIT PULL] ARM: soc: Marvell MMP changes for v5.5" pull > > request. > > > > Thanks, > > Lubo > > > > ---------------------------------------------------------------- > > ARM: Marvell MMP Device Tree patches for v5.5 > > > > This tag includes binding documentation for various hardware found on Marvell > > MMP3 SoC along a DTS file for said hardware. > > > > ---------------------------------------------------------------- > > Lubomir Rintel (6): > > dt-bindings: arm: cpu: Add Marvell MMP3 SMP enable method > > dt-bindings: arm: Convert Marvell MMP board/soc bindings to json-schema > > dt-bindings: arm: mrvl: Document MMP3 compatible string > > dt-bindings: mrvl,intc: Add a MMP3 interrupt controller > > dt-bindings: phy-mmp3-usb: Add bindings > > ARM: dts: mmp3: Add MMP3 SoC dts file > > > > Documentation/devicetree/bindings/arm/cpus.yaml | 1 + > > .../devicetree/bindings/arm/mrvl/mrvl.txt | 14 - > > .../devicetree/bindings/arm/mrvl/mrvl.yaml | 35 ++ > > .../bindings/interrupt-controller/mrvl,intc.txt | 14 +- > > .../devicetree/bindings/phy/phy-mmp3-usb.txt | 13 + > > arch/arm/boot/dts/mmp3.dtsi | 527 +++++++++++++++++++++ > > Hi, > > I only see a dtsi here. Do you have an early/partial dts for an actual piece of > hardware that also can go in, so we get build coverage of the dtsi, etc? > > Merging this as-is, but please follow up with one if you can -- even if it's > not complete yet. I'll send out one. It is indeed not complete, but it boots. I'm not sure about what name to use for the machine and the compatible string and therefore I'm thankful for suggestions. checkpatch.pl is currently unhappy about the compatible string, that can be fixed once we're sure compatible string is correct. Thank you for the pulls and the build fix. > -Olof Thank Lubo