From: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
linux-fbdev-devel@lists.sourceforge.net,
Jan Altenberg <jan.altenberg@linutronix.de>,
Andrew Victor <andrew@sanpeople.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Patrice Vilchez <patrice.vilchez@rfo.atmel.com>
Subject: Re: [PATCH] atmel_lcdfb: Fix STN LCD support
Date: Wed, 20 Jun 2007 14:10:45 +0200 [thread overview]
Message-ID: <46791945.6090203@rfo.atmel.com> (raw)
In-Reply-To: <20070619094752.1b7ba108@dhcp-255-175.norway.atmel.com>
Haavard Skinnemoen :
> On Fri, 15 Jun 2007 10:50:12 +0200
> Nicolas Ferre <nicolas.ferre@rfo.atmel.com> wrote:
>
>> From: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
>>
>> Fixes STN LCD support for the atmel_lcdfb framebuffer driver.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
>
> Looks correct to me. Although...
>
>> Index: b/drivers/video/Kconfig
>> ===================================================================
>> --- a/drivers/video/Kconfig 2007-05-14 11:02:16.000000000 +0200
>> +++ b/drivers/video/Kconfig 2007-06-13 11:04:10.000000000 +0200
>> @@ -701,6 +701,16 @@
>> Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
>> to let frame buffer in external SDRAM.
>>
>> +config FB_ATMEL_STN
>> + bool "Use a STN display with AT91/AT32 LCD Controller"
>> + depends on FB_ATMEL && ARCH_AT91SAM9261
>> + default n
>> + help
>> + Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
>> + Controller. Say N if you want to connect a TFT.
>> +
>> + If unsure, say N.
>> +
>
> I don't think it's appropriate to include chip-specific options here.
> This option will not affect the driver at all, it will only affect the
> board-specific setup code, so IMO it should be under Platform-specific
> options or something like that.
True in a "code centric" point of view. I do not think it is very usable
to move this switch in the board setup : The user will have to check if
an option is appearing in the board menu while he select the Atmel LCD
driver. He is supposed to have already selected the chip'n'board he is
using.
Moreover, this option will not show its nose until the board that
implements it is not included in depends.
(It is basically the same case with the option just above, with the very
same arguments).
> Also, the text says AT91/AT32 but it depends on one particular AT91
> chip.
Ok, will move it to a board switch (MACH_AT91SAM9261EK for instance).
This will grow as STN configuration will be implemented for boards.
Regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2007-06-20 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 8:50 [PATCH] atmel_lcdfb: Fix STN LCD support Nicolas Ferre
2007-06-15 9:14 ` Jan Altenberg
2007-06-19 7:47 ` Haavard Skinnemoen
2007-06-20 12:10 ` Nicolas Ferre [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-12 13:54 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=46791945.6090203@rfo.atmel.com \
--to=nicolas.ferre@rfo.atmel.com \
--cc=adaplas@gmail.com \
--cc=andrew@sanpeople.com \
--cc=hskinnemoen@atmel.com \
--cc=jan.altenberg@linutronix.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.vilchez@rfo.atmel.com \
/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).