Am Mittwoch, den 20.03.2013, 11:52 +0100 schrieb Philipp Zabel:
> Hi, last time I posted was a bit close to the merge window, so I'm
> reposting now. Greg, Arnd, could you take the first two patches?
Ping,
can I do anything to help move this along?
regards
Philipp
> These patches add support to configure on-chip SRAM via device-tree
> node or platform data and to obtain the resulting genalloc pool from
> the struct device pointer or a phandle pointing at the device tree node.
> This allows drivers to allocate SRAM with the genalloc API without
> hard-coding the genalloc pool pointer.
>
> The on-chip SRAM on i.MX53 and i.MX6q can be registered via device tree
> and changed to use the simple generic SRAM driver:
>
> ocram: ocram@00900000 {
> compatible = "fsl,imx-ocram", "mmio-sram";
> reg = <0x00900000 0x3f000>;
> };
>
> A driver that needs to allocate SRAM buffers, like the video processing
> unit on i.MX53, can retrieve the genalloc pool from a phandle in the
> device tree using of_get_named_gen_pool(node, "iram", 0) from patch 1:
>
> vpu@63ff4000 {
> /* ... */
> iram = <&ocram>;
> };
>
> Changes since v8:
> - The sram driver now matches against the "mmio-sram" compatible string.
> - Removed a whitespace error in the device tree binding documentation.
>
> regards
> Philipp
>
> ---
> Documentation/devicetree/bindings/media/coda.txt | 30 ++++++
> Documentation/devicetree/bindings/misc/sram.txt | 16 +++
> arch/arm/boot/dts/imx53.dtsi | 5 +
> arch/arm/boot/dts/imx6q.dtsi | 6 ++
> drivers/media/platform/Kconfig | 1 -
> drivers/media/platform/coda.c | 45 +++++---
> drivers/misc/Kconfig | 9 ++
> drivers/misc/Makefile | 1 +
> drivers/misc/sram.c | 121
> ++++++++++++++++++++++
> include/linux/genalloc.h | 15 +++
> include/linux/platform_data/coda.h | 18 ++++
> lib/genalloc.c | 81 +++++++++++++++
> 12 files changed, 333 insertions(+), 15 deletions(-)
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
