All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Alexander Stein <alexander.stein@systec-electronic.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] DT: video: atmel_lcdc: Add example of fixed framebuffer memory
Date: Wed, 11 Mar 2015 17:39:25 +0100	[thread overview]
Message-ID: <55006FBD.80701@atmel.com> (raw)
In-Reply-To: <1425540938-20538-1-git-send-email-alexander.stein@systec-electronic.com>

Le 05/03/2015 08:35, Alexander Stein a écrit :
> This drivers allows a fixed framebuffer memory to be set by an additional
> IORESOURCE_MEM resource. Thus add an example to the DT documentation.
> 
> Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>

Queued in at91-4.1-dt. Thanks!

> ---
> Changes in v2:
> * Fix typo noticed by checkpatch.pl
> 
>  Documentation/devicetree/bindings/video/atmel,lcdc.txt | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/video/atmel,lcdc.txt b/Documentation/devicetree/bindings/video/atmel,lcdc.txt
> index f059dd0..ecb8da0 100644
> --- a/Documentation/devicetree/bindings/video/atmel,lcdc.txt
> +++ b/Documentation/devicetree/bindings/video/atmel,lcdc.txt
> @@ -10,7 +10,9 @@ Required properties:
>  	"atmel,at91sam9g45es-lcdc" ,
>  	"atmel,at91sam9rl-lcdc" ,
>  	"atmel,at32ap-lcdc"
> -- reg : Should contain 1 register ranges(address and length)
> +- reg : Should contain 1 register ranges(address and length).
> +	Can contain an additional register range(address and length)
> +	for fixed framebuffer memory. Useful for dedicated memories.
>  - interrupts : framebuffer controller interrupt
>  - display: a phandle pointing to the display node
>  
> @@ -38,6 +40,14 @@ Example:
>  
>  	};
>  
> +Example for fixed framebuffer memory:
> +
> +	fb0: fb@0x00500000 {
> +		compatible = "atmel,at91sam9263-lcdc";
> +		reg = <0x00700000 0x1000 0x70000000 0x200000>;
> +		[...]
> +	};
> +
>  Atmel LCDC Display
>  -----------------------------------------------------
>  Required properties (as per of_videomode_helper):
> 


-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Alexander Stein <alexander.stein@systec-electronic.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	"Kumar Gala" <galak@codeaurora.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] DT: video: atmel_lcdc: Add example of fixed framebuffer memory
Date: Wed, 11 Mar 2015 17:39:25 +0100	[thread overview]
Message-ID: <55006FBD.80701@atmel.com> (raw)
In-Reply-To: <1425540938-20538-1-git-send-email-alexander.stein@systec-electronic.com>

Le 05/03/2015 08:35, Alexander Stein a écrit :
> This drivers allows a fixed framebuffer memory to be set by an additional
> IORESOURCE_MEM resource. Thus add an example to the DT documentation.
> 
> Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>

Queued in at91-4.1-dt. Thanks!

> ---
> Changes in v2:
> * Fix typo noticed by checkpatch.pl
> 
>  Documentation/devicetree/bindings/video/atmel,lcdc.txt | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/video/atmel,lcdc.txt b/Documentation/devicetree/bindings/video/atmel,lcdc.txt
> index f059dd0..ecb8da0 100644
> --- a/Documentation/devicetree/bindings/video/atmel,lcdc.txt
> +++ b/Documentation/devicetree/bindings/video/atmel,lcdc.txt
> @@ -10,7 +10,9 @@ Required properties:
>  	"atmel,at91sam9g45es-lcdc" ,
>  	"atmel,at91sam9rl-lcdc" ,
>  	"atmel,at32ap-lcdc"
> -- reg : Should contain 1 register ranges(address and length)
> +- reg : Should contain 1 register ranges(address and length).
> +	Can contain an additional register range(address and length)
> +	for fixed framebuffer memory. Useful for dedicated memories.
>  - interrupts : framebuffer controller interrupt
>  - display: a phandle pointing to the display node
>  
> @@ -38,6 +40,14 @@ Example:
>  
>  	};
>  
> +Example for fixed framebuffer memory:
> +
> +	fb0: fb@0x00500000 {
> +		compatible = "atmel,at91sam9263-lcdc";
> +		reg = <0x00700000 0x1000 0x70000000 0x200000>;
> +		[...]
> +	};
> +
>  Atmel LCDC Display
>  -----------------------------------------------------
>  Required properties (as per of_videomode_helper):
> 


-- 
Nicolas Ferre

  reply	other threads:[~2015-03-11 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05  7:35 [PATCH v2 1/1] DT: video: atmel_lcdc: Add example of fixed framebuffer memory Alexander Stein
2015-03-11 16:39 ` Nicolas Ferre [this message]
2015-03-11 16:39   ` Nicolas Ferre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55006FBD.80701@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=alexander.stein@systec-electronic.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.