mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: hverkuil@xs4all.nl (Hans Verkuil)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 3/6] documentation: media: Add documentation for new RGB and YUV bus formats
Date: Mon, 20 Mar 2017 16:04:18 +0100	[thread overview]
Message-ID: <4aa7c066-342b-c4a5-fd95-deda9f216e26@xs4all.nl> (raw)
In-Reply-To: <97b0c618-a3f4-11d7-d117-c83e8949633a@baylibre.com>

On 03/17/2017 05:11 PM, Neil Armstrong wrote:
> On 03/16/2017 06:01 PM, Archit Taneja wrote:
>>
>>
>> On 3/7/2017 10:12 PM, Neil Armstrong wrote:
>>> Add documentation for added Bus Formats to describe RGB and YUS formats used
>>
>> s/YUS/YUV
> 
> Thanks again....
> 
>>
>>> as input to the Synopsys DesignWare HDMI TX Controller.
>>>
>>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>>> ---
>>>  Documentation/media/uapi/v4l/subdev-formats.rst | 4992 ++++++++++++++++++-----
>>>  1 file changed, 3963 insertions(+), 1029 deletions(-)
>>
>> Do we know if there is a better way to add more columns without
>> adding so many lines?
> 
> It seems not, the reason is written in the commands.
> 
>> If not, one option could be to create a separate tables for
>> 48 bit RGB formats, 48 bit YUV formats etc.
> 
> It would be simple indeed, any V4L guys for an advice here ?

I would split up these large tables into separate tables, depending on the
number of bits each pixel uses: so an RGB table for 8 bits, 9-16 bits,
17-24, 25-32, 33-48.

This also avoids a major problem where the horizontal scrollbar is at the bottom
of the table, but the column numbering is at the top and out of sight if the
table is long.

It also prevents these large horizontal widths when they are not needed.

Regards,

	Hans

  reply	other threads:[~2017-03-20 15:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 16:42 [PATCH v3 0/6] drm: bridge: dw-hdmi: Add support for Custom PHYs Neil Armstrong
2017-03-07 16:42 ` [PATCH v3 1/6] drm: bridge: dw-hdmi: Extract PHY interrupt setup to a function Neil Armstrong
2017-03-07 17:12   ` Jose Abreu
2017-03-08 10:25     ` Neil Armstrong
2017-03-07 16:42 ` [PATCH v3 2/6] media: uapi: Add RGB and YUV bus formats for Synopsys HDMI TX Controller Neil Armstrong
2017-03-16 17:06   ` Archit Taneja
2017-03-17 16:10     ` Neil Armstrong
2017-03-20 15:35   ` Hans Verkuil
2017-03-07 16:42 ` [PATCH v3 3/6] documentation: media: Add documentation for new RGB and YUV bus formats Neil Armstrong
2017-03-16 17:01   ` Archit Taneja
2017-03-17 16:11     ` Neil Armstrong
2017-03-20 15:04       ` Hans Verkuil [this message]
2017-03-20 14:33   ` Hans Verkuil
2017-03-07 16:42 ` [PATCH v3 4/6] drm: bridge: dw-hdmi: Switch to V4L bus format and encodings Neil Armstrong
2017-03-07 17:35   ` Jose Abreu
2017-03-08  9:35     ` Neil Armstrong
2017-03-08 12:12     ` Neil Armstrong
2017-03-09 14:27       ` Jose Abreu
2017-03-13 11:43         ` Jose Abreu
2017-03-14  8:14           ` Neil Armstrong
2017-03-07 16:42 ` [PATCH v3 5/6] drm: bridge: dw-hdmi: Add Documentation on supported input formats Neil Armstrong
2017-03-16 16:43   ` Archit Taneja
2017-03-07 16:42 ` [PATCH v3 6/6] drm: bridge: dw-hdmi: Move HPD handling to PHY operations Neil Armstrong
2017-03-07 17:19   ` Jose Abreu

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=4aa7c066-342b-c4a5-fd95-deda9f216e26@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=linus-amlogic@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

all inboxes | Powered by JetHome®