From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: David Airlie <airlied@linux.ie>,
Darren Etheridge <detheridge@ti.com>,
Rob Clark <robdclark@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/8] drm/i2c: tda998x: add video and audio input configuration
Date: Wed, 14 Aug 2013 16:34:42 +0200 [thread overview]
Message-ID: <520B9582.7070503@gmail.com> (raw)
In-Reply-To: <20130814141236.GA29211@n2100.arm.linux.org.uk>
On 08/14/13 16:12, Russell King - ARM Linux wrote:
> On Tue, Aug 06, 2013 at 12:20:15AM +0200, Sebastian Hesselbarth wrote:
>> @@ -0,0 +1,23 @@
>> +#ifndef __TDA998X_H__
>> +#define __TDA998X_H__
>> +
>> +enum tda998x_audio_format {
>> + AFMT_I2S,
>> + AFMT_SPDIF,
>> +};
>> +
>> +struct tda998x_encoder_params {
>> + int audio_cfg;
>> + int audio_clk_cfg;
>> + enum tda998x_audio_format audio_format;
>> + int audio_sample_rate;
>> + char audio_frame[6];
>> + int swap_a, mirr_a;
>> + int swap_b, mirr_b;
>> + int swap_c, mirr_c;
>> + int swap_d, mirr_d;
>> + int swap_e, mirr_e;
>> + int swap_f, mirr_f;
>> +};
>
> You really should pick my version of this header file from the message
> I sent earlier:
>
> E1UllOe-00058q-Ep@rmk-PC.arm.linux.org.uk
> [PATCH RFC 7/8] drm/i2c: nxp-tda998x: add video and audio input configuration
>
> if you're going to suggest that it's something I produced.
>
Right, that one above must have been the one I made up from the
one RFC you forgot to add it. I must have messed it up and will
take yours, of course.
Sebastian
next prev parent reply other threads:[~2013-08-14 14:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 22:20 [PATCH 0/8] Several NXP TDA998x patches Sebastian Hesselbarth
2013-08-05 22:20 ` [PATCH 1/8] drm/i2c: tda998x: fix EDID reading on TDA19988 devices Sebastian Hesselbarth
2013-08-14 12:16 ` Russell King - ARM Linux
2013-08-14 12:32 ` Rob Clark
2013-08-05 22:20 ` [PATCH 2/8] drm/i2c: tda998x: ensure VIP output mux is properly set Sebastian Hesselbarth
2013-08-14 12:15 ` Russell King - ARM Linux
2013-08-05 22:20 ` [PATCH 3/8] drm/i2c: tda998x: fix npix/nline programming Sebastian Hesselbarth
2013-08-05 22:20 ` [PATCH 4/8] drm/i2c: tda998x: prepare for video input configuration Sebastian Hesselbarth
2013-08-05 22:20 ` [PATCH 5/8] drm/i2c: tda998x: add video and audio " Sebastian Hesselbarth
2013-08-14 12:20 ` Russell King - ARM Linux
2013-08-14 14:12 ` Russell King - ARM Linux
2013-08-14 14:34 ` Sebastian Hesselbarth [this message]
2013-08-05 22:20 ` [PATCH 6/8] drm/i2c: tda998x: fix sync generation and calculation Sebastian Hesselbarth
2013-08-14 12:41 ` Russell King - ARM Linux
2013-08-14 14:14 ` Sebastian Hesselbarth
2013-08-14 14:35 ` Russell King - ARM Linux
2013-08-05 22:20 ` [PATCH 7/8] drm/i2c: tda998x: prepare for broken sync workaround Sebastian Hesselbarth
2013-08-05 22:20 ` [PATCH 8/8] drm/tilcdc fixup mode to workaound sync for tda998x Sebastian Hesselbarth
2013-08-06 16:26 ` [PATCH 0/8] Several NXP TDA998x patches Etheridge, Darren
2013-08-08 22:08 ` Darren Etheridge
2013-08-08 22:08 ` Darren Etheridge
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=520B9582.7070503@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=detheridge@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robdclark@gmail.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 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.