From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Ricardo Neri <ricardo.neri@ti.com>
Cc: peter.ujfalusi@ti.com, s-guiriec@ti.com, b-cousson@ti.com,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v3 0/7] Create platform device for audio support
Date: Tue, 6 Nov 2012 13:36:19 +0200 [thread overview]
Message-ID: <5098F633.5040200@ti.com> (raw)
In-Reply-To: <1352182757-1216-1-git-send-email-ricardo.neri@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
On 2012-11-06 08:19, Ricardo Neri wrote:
> Hi Tomi, l-o list,
>
> The main purpose of this patch set is to create a platform device for audio
> support from the OMAPDSS HDMI driver. This tries to follow an approach similar
> to MFD drivers in which a core driver creates domain-specific devices. Under
> this approach, the OMAPDSS HDMI drivers acts as the core driver, retrieves its
> resources (from DT or hwmod) and passes the relevant audio resources for
> other drivers to use.
>
> This is also beneficial for future DT boot support, as the OMAP HDMI IP will be
> represented by a single node in the tree.
>
> Before creating the platform device for audio, I also did minor cleanup to the
> OMAPDSS HDMI driver probe function.
>
> Changes from v2:
> *Check the validity of the audio platform device by checking a non-NULL condition
> rather than an error pointer condition.
> *Pass the ID of the HDMI platform device to handle more than one instance of
> HDMI audio platform devices. This is for future implementations that support
> more than one HDMI output.
>
> Changes from v1:
> *Simplify ioremap further by using devm_request_and_ioremap.
> *Pass to the audio driver only the DMA port and not the whole register space.
> *Use a local array for the audio resources and init them with DEFINE_RES_MEM.
> *Obtain the DMA port address offset and size from the HDMI IP-specific library.
>
> v2 is accessible here:
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg79529.html
>
> v1 is accessible here:
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg77861.html
Looks good to me, I'll apply to omapdss tree.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]
prev parent reply other threads:[~2012-11-06 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 6:19 [PATCH v3 0/7] Create platform device for audio support Ricardo Neri
2012-11-06 6:19 ` [PATCH v3 1/7] OMAPDSS: HDMI: Rename resource variable at probe Ricardo Neri
2012-11-06 6:19 ` [PATCH v3 2/7] OMAPDSS: HDMI: Convert to devm_request_and_ioremap Ricardo Neri
2012-11-06 6:19 ` [PATCH v3 3/7] OMAPDSS: HDMI: Make panel return dssdev register errors Ricardo Neri
2012-11-06 6:19 ` [PATCH v3 4/7] OMAPDSS: HDMI: Handle panel init error at probe Ricardo Neri
2012-11-06 6:19 ` [PATCH v3 5/7] OMAPDSS: HDMI: Uninit display on device add error Ricardo Neri
2012-11-06 6:19 ` [PATCH v3 6/7] OMAPDSS: HDMI: Add op to get audio DMA port address offset Ricardo Neri
2012-11-06 6:19 ` [PATCH v3 7/7] OMAPDSS: HDMI: Create platform device for audio support Ricardo Neri
2012-11-06 11:36 ` Tomi Valkeinen [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=5098F633.5040200@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=ricardo.neri@ti.com \
--cc=s-guiriec@ti.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.