From: Andres Salomon <dilinger@queued.net>
To: Jens Frederich <jfrederich@gmail.com>
Cc: gregkh@linuxfoundation.org, jon.nettleton@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: olpc_dcon: provide detailed FB_OLPC_DCON help section
Date: Tue, 30 Jul 2013 11:48:45 -0700 [thread overview]
Message-ID: <20130730114845.15ce0307@dev.queued.net> (raw)
In-Reply-To: <1375207894-6106-1-git-send-email-jfrederich@gmail.com>
Acked-by: Andres Salomon <dilinger@queued.net>
On Tue, 30 Jul 2013
20:11:34 +0200 Jens Frederich <jfrederich@gmail.com> wrote:
> The FB_OLPC_DCON help section is to short according to checkpatch.pl.
> We want more information about the controller type, its task, its
> video pipeline position and so on.
>
> There are no style issues, remove checkpatch.pl TODO entry.
>
> Signed-off-by: Jens Frederich <jfrederich@gmail.com>
>
> diff --git a/drivers/staging/olpc_dcon/Kconfig
> b/drivers/staging/olpc_dcon/Kconfig index fe40e0b..2ff015d 100644
> --- a/drivers/staging/olpc_dcon/Kconfig
> +++ b/drivers/staging/olpc_dcon/Kconfig
> @@ -4,9 +4,14 @@ config FB_OLPC_DCON
> select I2C
> select BACKLIGHT_CLASS_DEVICE
> ---help---
> - Add support for the OLPC XO DCON controller. This
> controller is
> - only available on OLPC platforms. Unless you have one of
> these
> - platforms, you will want to say 'N'.
> + In order to support very low power operation, the XO
> laptop uses a
> + secondary Display CONtroller, or DCON. This secondary
> controller
> + is present in the video pipeline between the primary
> display
> + controller (integrate into the processor or chipset) and
> the LCD
> + panel. It allows the main processor/display controller to
> be
> + completely powered off while still retaining an image on
> the display.
> + This controller is only available on OLPC platforms.
> Unless you have
> + one of these platforms, you will want to say 'N'.
>
> config FB_OLPC_DCON_1
> bool "OLPC XO-1 DCON support"
> diff --git a/drivers/staging/olpc_dcon/TODO
> b/drivers/staging/olpc_dcon/TODO index 35f9cda..f378e84 100644
> --- a/drivers/staging/olpc_dcon/TODO
> +++ b/drivers/staging/olpc_dcon/TODO
> @@ -1,5 +1,4 @@
> TODO:
> - - checkpatch.pl cleanups
> - see if vx855 gpio API can be made similar enough to cs5535
> so we can share more code
> - allow simultaneous XO-1 and XO-1.5 support
prev parent reply other threads:[~2013-07-30 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 18:11 Jens Frederich
2013-07-30 18:48 ` Andres Salomon [this message]
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=20130730114845.15ce0307@dev.queued.net \
--to=dilinger@queued.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jfrederich@gmail.com \
--cc=jon.nettleton@gmail.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®