ARM: dts: OMAP3: Add GPMC controller and NAND memory to Overo
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 of 2 patches 0 repliesNew
1 of 2 patches is in this archive. The cover letter announces 2.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | ARM: dts: OMAP3: Add GPMC controller | +0 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] ARM: dts: OMAP3: Add GPMC controller and NAND memory to Overo
Quoted 11 lines · Florian Vaussard
Hello,
This is more an RFC serie, as an issue is still unclear to me. Building on the work of Daniel Mack for the GPMC controller (staged in Tony's tree [1]), it was easy to add the GPMC controller to OMAP3.
The issue comes from the Overo on-board NAND, as the amount of flash depends on the revision. Currently, partitions are handled in the board file using
MTDPART_SIZ_FULL, but looking at the ofpart parser, the size given to the parser must be fixed.
Quoted 4 lines
So how should we handle such case? Having several dtsi depending on the Overo's revision would be a mess to my sense, considering the non-conditional include inside the expansion boards' dts. Or would it make sense to extend the DT binding for partitions?
Yes makes sense to extend the binding to use the full flash memory if the size can be probed.
Regards,
Tony