linux-toradex.git/arch/arc/kernel/devtree.c, branch v3.14.3

arc: remove unnecessary prom.h includes

2013-10-10T01:04:01+00:00

Remove unnecessary prom.h includes in preparation to remove prom.h.

Signed-off-by: Rob Herring 
Acked-by: Vineet Gupta 
Acked-by: Grant Likely

arc: use common of_flat_dt_match_machine

2013-10-10T01:03:55+00:00

Convert arc to use the common of_flat_dt_match_machine function.

Signed-off-by: Rob Herring 
Acked-by: Vineet Gupta

arc: use early_init_dt_scan

2013-10-09T16:38:08+00:00

Convert arc to use new early_init_dt_scan function.

Signed-off-by: Rob Herring 
Acked-by: Vineet Gupta

arc: use unflatten_and_copy_device_tree

2013-10-09T16:38:03+00:00

Use the common unflatten_and_copy_device_tree to copy the built-in FDT
out of init section.

Signed-off-by: Rob Herring 
Acked-by: Vineet Gupta 
Acked-by: Grant Likely

of: consolidate definition of early_init_dt_alloc_memory_arch()

2013-08-28T20:18:32+00:00

Most architectures use the same implementation. Collapse the common ones
into a single weak function that can be overridden.

Signed-off-by: Grant Likely

ARC: make a copy of flat DT

2013-02-26T08:55:18+00:00

The flat DT (currently embedded in vmlinux) is in .init section.
The unflattened/binary tree doesn't copy strings through and references
them from orig flat DT - which could cause catestrohpy if of_* APIs are
called post init, say from a driver which is a loadable module.

Reported-by: James Hogan 
Signed-off-by: Vineet Gupta

ARC: [Review] Multi-platform image #2: Board callback Infrastructure

2013-02-15T17:46:13+00:00

The orig platform code orgnaization was singleton design pattern - only
one platform (and board thereof) would build at a time.

Thus any platform/board specific code (e.g. irq init, early init ...)
expected by ARC common code was exported as well defined set of APIs,
with only ONE instance building ever.

Now with multiple-platform build requirement, that design of code no
longer holds - multiple board specific calls need to build at the same
time - so ARC common code can't use the API approach, it needs a
callback based design where each board registers it's specific set of
functions, and at runtime, depending on board detection, the callbacks
are used from the registry.

This commit adds all the infrastructure, where board specific callbacks
are specified as a "maThine description".

All the hooks are placed in right spots, no board callbacks registered
yet (with MACHINE_STARt/END constructs) so the hooks will not run.

Next commit will actually convert the platform to this infrastructure.

Signed-off-by: Vineet Gupta 
Cc: Arnd Bergmann 
Acked-by: Arnd Bergmann

ARC: [DeviceTree] Convert some Kconfig items to runtime values

2013-02-15T17:45:56+00:00

* mem size now runtime configured (prev CONFIG_ARC_PLAT_SDRAM_SIZE)
* core cpu clk runtime configured (prev CONFIG_ARC_PLAT_CLK)

Signed-off-by: Vineet Gupta 
Cc: Arnd Bergmann 
Cc: Grant Likely

ARC: [DeviceTree] Basic support

2013-02-15T17:45:55+00:00

This is minimal infrastructure needed for devicetree work.
It uses an a sample "skeleton" devicetree - embedded in kernel image -
to print the board, manufacturer by parsing the top-level "compatible"
string.

As of now we don't need any additional "board" specific "machine_desc".

TODO: support interpreting the command line as boot-loader passed dtb

Signed-off-by: Vineet Gupta 
Cc: Arnd Bergmann 
Cc: Grant Likely 
Cc: devicetree-discuss@lists.ozlabs.org
Cc: Rob Herring 
Cc: James Hogan 
Reviewed-by: Rob Herring 
Reviewed-by: James Hogan