devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jyri Sarha <jsarha@ti.com>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: dri-devel@lists.freedesktop.org, airlied@linux.ie,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	bcousson@baylibre.com, tony@atomide.com, detheridge@ti.com,
	tomi.valkeinen@ti.com
Subject: Re: [PATCH RFC 0/3] Make "ti,tilcdc,slave" DT binding more sensible
Date: Wed, 14 Jan 2015 11:56:46 +0200	[thread overview]
Message-ID: <54B63D5E.1010606@ti.com> (raw)
In-Reply-To: <20150114075729.7fe4b80a@armhf>

On 01/14/2015 08:57 AM, Jean-Francois Moine wrote:
> On Tue, 13 Jan 2015 19:12:25 +0200
> Jyri Sarha <jsarha@ti.com> wrote:
>
>> These patches are needed for Beaglebone-back HDMI audio. There is no
>> direct dependency between these patches and the other (dts and ASoC)
>> changes needed for the HDMI audio so these changes can be merged
>> independently. I also feel that these changes make sense even without
>> the HDMI audio.
>>
>> Best regards,
>> Jyri
>>
>> Jyri Sarha (3):
>>    drm: encoder_slave: Add drm_i2c_encoder_attach()
>>    drm/tilcdc: slave: Add support for "i2c-slave" DT-parameter
>>    ARM: dts: am335x-boneblack: Use new binding in ti,tilcdc,slave node
>>
>>   .../devicetree/bindings/drm/tilcdc/slave.txt       |    4 +-
>>   arch/arm/boot/dts/am335x-boneblack.dts             |    9 +++-
>>   drivers/gpu/drm/drm_encoder_slave.c                |   51 ++++++++++++++++++++
>>   drivers/gpu/drm/tilcdc/tilcdc_slave.c              |   50 +++++++++++--------
>>   include/drm/drm_encoder_slave.h                    |    3 ++
>>   5 files changed, 95 insertions(+), 22 deletions(-)
>
> Instead of adding code to have the slave encoder working, it would be
> simpler to change the way tilcdc uses the tda998x.
> I already proposed such a patch:
>
> http://lists.freedesktop.org/archives/dri-devel/2014-March/056065.html
>
> and the changes in the tda998x driver have been done by Russell:
>
> commit: a8f4d4d63739e4bca459ff40636f1d9e4b7ef5e6
> 	drm/i2c: tda998x: allow re-use of tda998x support code
> and
> commit: c707c3619ca81f499a5ce032021405e989a96ff0
> 	drm/i2c: tda998x: add component support
>

Interesting. Would you still have the original branch somewhere? Manual 
applying the patches from the web-page is time consuming.

Best regards,
Jyri

      reply	other threads:[~2015-01-14  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 17:12 [PATCH RFC 0/3] Make "ti,tilcdc,slave" DT binding more sensible Jyri Sarha
2015-01-13 17:12 ` [PATCH RFC 1/3] drm: encoder_slave: Add drm_i2c_encoder_attach() Jyri Sarha
2015-01-13 17:12 ` [PATCH RFC 2/3] drm/tilcdc: slave: Add support for "i2c-slave" DT-parameter Jyri Sarha
     [not found] ` <cover.1421167634.git.jsarha-l0cyMroinI0@public.gmane.org>
2015-01-13 17:12   ` [PATCH RFC 3/3] ARM: dts: am335x-boneblack: Use new binding in ti,tilcdc,slave node Jyri Sarha
2015-01-14  6:57 ` [PATCH RFC 0/3] Make "ti,tilcdc,slave" DT binding more sensible Jean-Francois Moine
2015-01-14  9:56   ` Jyri Sarha [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=54B63D5E.1010606@ti.com \
    --to=jsarha@ti.com \
    --cc=airlied@linux.ie \
    --cc=bcousson@baylibre.com \
    --cc=detheridge@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=moinejf@free.fr \
    --cc=tomi.valkeinen@ti.com \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).