mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Documentation: framebuffer: remove note about lack of backlight support
Date: Mon, 4 Oct 2021 13:53:24 +0200	[thread overview]
Message-ID: <20211004115324.GE28453@pengutronix.de> (raw)
In-Reply-To: <20210825092701.30436-1-a.fatoum@pengutronix.de>

On Wed, Aug 25, 2021 at 11:27:01AM +0200, Ahmad Fatoum wrote:
> barebox supports PWM backlight. Remove the notice about lack of support.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  Documentation/user/framebuffer.rst | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)

Applied, thanks

Sascha

> 
> diff --git a/Documentation/user/framebuffer.rst b/Documentation/user/framebuffer.rst
> index 8b95ad6b8700..d17df822f299 100644
> --- a/Documentation/user/framebuffer.rst
> +++ b/Documentation/user/framebuffer.rst
> @@ -4,9 +4,7 @@ Framebuffer support
>  Framebuffer splash screen
>  -------------------------
>  
> -barebox supports BMP and PNG graphics using the :ref:`command_splash` command. barebox
> -currently has no support for backlights, so unless there is a board specific enable
> -hook for enabling a display it must be done manually with a script. Since barebox
> +barebox supports BMP and PNG graphics using the :ref:`command_splash` command. Since barebox
>  has nothing useful to show on the framebuffer it doesn't enable it during startup.
>  A framebuffer can be enabled with the ``enable`` parameter of the framebuffer device:
>  
> @@ -39,7 +37,7 @@ A typical script to enable the framebuffer could look like this:
>    # wait for signals to become stable
>    msleep 100
>  
> -  # finally enable backlight
> +  # finally enable backlight manually if no driver exists
>    gpio_direction_output 42 1
>  
>  Framebuffer console
> -- 
> 2.30.2
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


      reply	other threads:[~2021-10-04 11:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25  9:27 Ahmad Fatoum
2021-10-04 11:53 ` Sascha Hauer [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=20211004115324.GE28453@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@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