All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jose Abreu <Jose.Abreu@synopsys.com>
To: dri-devel@lists.freedesktop.org
Cc: Jose.Abreu@synopsys.com, daniel.vetter@ffwll.ch,
	nariman@opensource.wolfsonmicro.com, wsa@sang-engineering.com,
	laurent.pinchart@ideasonboard.com
Subject: [adv7511] Adding audio to transmitter driver
Date: Mon, 15 Feb 2016 19:13:11 +0000	[thread overview]
Message-ID: <20160215191311.GA24093@synopsys.com> (raw)

Hi all,

I am an employee at Synopsys and as part of our IP Prototyping Kits we are adding audio support to the ADV7511 HDMI transmitter. Our work is based on the Analog Devices kernel tree available at: https://github.com/analogdevicesinc/linux/blob/xcomm_zynq/drivers/gpu/drm/i2c/adv7511_audio.c.

Currently we are facing an difficulty regarding the organization of the driver. Analog Devices compiles both audio and video in a single global driver but we were wondering if its better to separate audio from video and make them as separate Kconfig entries.

As we expect to introduce this in the mainline we are asking you for suggestions or comments about this matter. Is it any driver in the mainline that faces the same situation so we can base our work? What do you think its the best solution? Enable audio and video at the same time or make them separate entries?

Best regards,
Jose Miguel Abreu


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-02-15 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 19:13 Jose Abreu [this message]
2016-02-15 23:21 ` [adv7511] Adding audio to transmitter driver Laurent Pinchart
  -- strict thread matches above, loose matches on Subject: below --
2016-02-16 10:45 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=20160215191311.GA24093@synopsys.com \
    --to=jose.abreu@synopsys.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=nariman@opensource.wolfsonmicro.com \
    --cc=wsa@sang-engineering.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.