From: hong.xu@atmel.com (Hong Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] AT91: Add VSYNC pin definition for AT91SAM9263 silicon
Date: Wed, 25 May 2011 17:15:53 +0800 [thread overview]
Message-ID: <4DDCC8C9.3080102@atmel.com> (raw)
In-Reply-To: <20110525073933.GH863@game.jcrosoft.org>
Hi,
On 05/25/2011 03:39 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 14:31 Wed 25 May , Hong Xu wrote:
>> On Atmel's AT91SAM9263-EK board, the LCD panel does not need VSYNC
>> signal. But this signal is useful for the boards from other
>> vendors, as suggested by Nicholas Kinar.
>>
>> This small patch adds the VSYNC pin definition by default.
>>
>> Reported-by: Nicholas Kinar<n.kinar@usask.ca>
>> Signed-off-by: Hong Xu<hong.xu@atmel.com>
>> ---
>> arch/arm/mach-at91/at91sam9263_devices.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/mach-at91/at91sam9263_devices.c b/arch/arm/mach-at91/at91sam9263_devices.c
>> index fb5c23a..7dab33e 100644
>> --- a/arch/arm/mach-at91/at91sam9263_devices.c
>> +++ b/arch/arm/mach-at91/at91sam9263_devices.c
>> @@ -832,6 +832,7 @@ void __init at91_add_device_lcdc(struct atmel_lcdfb_info *data)
>> if (!data)
>> return;
>>
>> + at91_set_A_periph(AT91_PIN_PC0, 0); /* LCDVSYNC */
> this must be optionnal
>
> we need to update this with somethink like done on avr32
>
hm.. PC0 in SAM9263 has only "A" function (LCD VSYNC). As long as this
pin is not used as GPIO, it's harmless to enable its peripheral function.
I just had a quick look at the AVR32 code without catching your
"something like on AVR32". In AVR32, all ATMEL_LCDC_*_*BIT has "VSYNC"
defined.
BR,
Eric
next prev parent reply other threads:[~2011-05-25 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 6:31 [PATCH] AT91: Add VSYNC pin definition for AT91SAM9263 silicon Hong Xu
2011-05-25 7:39 ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-25 9:15 ` Hong Xu [this message]
2011-05-27 7:27 ` Jean-Christophe PLAGNIOL-VILLARD
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=4DDCC8C9.3080102@atmel.com \
--to=hong.xu@atmel.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).