Skip to content

ARM: OMAP: clock data conversion to DT

Nishanth Menon linux-arm-kernel linux-devicetree linux-omap 2 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v7 Latest posting 2/20 of 36 patches 0 repliesNew
  2. v7 posting 1/22 of 36 patches 0 repliesSuperseded

Patches in v7 posting 2/2 No applies recorded yet

None of the 36 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v7 yet.

Read the v7 thread

Cover letter [PATCHv7 00/36] ARM: OMAP: clock data conversion to DT
Quoted 18 lines · Tony Lindgren
Quoted 17 lines · Tero Kristo
Quoted 10 lines · Tony Lindgren
Quoted 4 lines · Tero Kristo

Hi,

Just a gentle reminder, anybody have any comments on this series or should we start queuing stuff?

Well omap4 seems to work for me just fine, and omap3 in legacy mode. But looks like omap3 device tree based booting is breaking after I pulled in your test branch. I get the following on 3630 based dm3730.

Uart4 breaks because of the issue with basic DT blobs. You need at least this patch:

http://linux-kernel.2935.n7.nabble.com/RFC-PATCH-ARM-OMAP3630-Add-generic-machine-descriptor-td722791.html

Quoted 8 lines
Quoted 3 lines

... from Nishanth to get it to work right. Otherwise the clock init tries to use omap3430 clock data for omap3630 which leaves uart4 nodes out.

OK thanks yes that solves it, I was missing the compatible flag for my not quite ready test boards (3730-evm and zoom3). I'll apply Nishant's fix with some changes.

I will post out an RFC based on Olof's suggestion in a few mins. will be nice to see any deltas needed.

Signature · 2 lines
Regards,
Nishanth Menon