From: Sebastian Reichel <sre@kernel.org>
To: Dev Null <devnull@uvos.xyz>
Cc: linux-omap@vger.kernel.org
Subject: Re: [bug report] Droid 4 cpcap rtc
Date: Mon, 29 Jun 2020 13:42:02 +0200 [thread overview]
Message-ID: <20200629114202.7e5su5ny75mhqubw@earth.universe> (raw)
In-Reply-To: <20200629002917.0a2045380a0fe022f852e067@uvos.xyz>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
Hi,
On Mon, Jun 29, 2020 at 12:29:17AM +0200, Dev Null wrote:
> 1. writing to the rtc via rtc-cpcap with hwclock appears to not work at all.
> - see https://github.com/maemo-leste/bugtracker/issues/399
> - hwclock: ioctl(RTC_SET_TIME) to /dev/rtc0 to set the time failed: Numerical result out of range
Looks like a regression introduced by "rtc: cpcap: set range",
which landed in v5.7.
> 2. do you by any chance know how the RGB -> RGWRBW pentile color
> conversion happens on the droid 4? is this handled in hardware or
> in software or in firmware somewere?
The omapdrm RGB framebuffer is send to the DSI panel, which has its
own local framebuffer to support panel self refresh. The panel
controller does the format change transparently and does not offer
any configuration options as far as I know.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-06-29 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 22:29 [bug report] Droid 4 cpcap rtc Dev Null
2020-06-29 11:41 ` [PATCH] rtc: cpcap: fix range Sebastian Reichel
2020-06-29 14:34 ` Tony Lindgren
2020-06-29 17:25 ` Merlijn Wajer
2020-07-02 20:23 ` Alexandre Belloni
2020-06-29 11:42 ` Sebastian Reichel [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=20200629114202.7e5su5ny75mhqubw@earth.universe \
--to=sre@kernel.org \
--cc=devnull@uvos.xyz \
--cc=linux-omap@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 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.