linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ykk@rock-chips.com (Kuankuan.Yang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/6] Those patches is used for dw_hdmi audio.
Date: Mon, 15 Dec 2014 19:52:06 +0800	[thread overview]
Message-ID: <548ECB66.70004@rock-chips.com> (raw)
In-Reply-To: <548EC9E1.5040206@rock-chips.com>

  Hi Russell:

      thks for your replay, actually you also have send me those 
dw-hdmi-audio.c patches, and I also agree it's an beautiful way to make 
hdmi-audio works. Beside,
  I try to reuse it into our platform, and actually the system have 
created the DW_HDMI sound card successfully, but i cannot play any 
sound  with this sound card.
      After dump the registers, I found the part of "Audio DMA 
Registers" cannot write and always read with 0x00.  So I searching the 
document  "Designware Core
  HDMI Transmitter Controller Databook", and found that  "Audio DMA 
Registers" only present when the hardware configuration parameter 
AUDIO_IF is set to
  AHBAUDDMA. Than I communicate with our IC colleagues, they told me 
that our cpu rk3288 only support two way to  transmit audio data( I2S & 
SPDIF ), in that
way we do not support AHB_DMA, it's very sad, and this it why i give up 
this way, also it's my bad that i should replay to u first in the before 
mail.


Best Regards.
> ? 2014?12?15? 18:38, Russell King - ARM Linux ??:
>> On Mon, Dec 15, 2014 at 10:11:28AM +0800, Yakir Yang wrote:
>>> rk3288 use Designware HDMI IP, Designware HDMI supports four interfaces to
>>> config hdmi audio(I2S, S/PDIF, Generic Parallel Audio, AHB Audio DMA), but
>>> rk3288 only support two ways to config hdmi audio(I2S, S/PDIF), So we take
>>> I2S as hdmi audio operation interfaces, and then treat hdmi audio as an
>>> standard ALSA devices(only got platback function).
>> There is no need for dw-hdmi audio to be implemented as an ASoC
>> device - as I've already sent patches to Andy with my ALSA driver
>> which has been around for the last two years, and works well, and
>> doesn't require any additional DT description.
>>
>

  parent reply	other threads:[~2014-12-15 11:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  2:11 [RFC PATCH 0/6] Those patches is used for dw_hdmi audio Yakir Yang
2014-12-15  2:11 ` [PATCH 4/6] ASoC: rockchip-hdmi-audio: add sound driver for hdmi audio Yakir Yang
2014-12-15  2:55 ` [PATCH 5/6] dt-bindings: Add documentation for Rockchip hdmi-audio Yakir Yang
2014-12-15  9:02   ` Lars-Peter Clausen
2014-12-15  9:46     ` Kuankuan.Yang
2014-12-15 10:40   ` Russell King - ARM Linux
2014-12-15 12:02     ` Mark Brown
2014-12-15 13:10       ` Kuankuan.Yang
2014-12-15 16:18         ` Mark Brown
2014-12-16  2:14           ` Kuankuan.Yang
2014-12-16  2:38           ` Kuankuan.Yang
2014-12-16  6:17           ` Kuankuan.Yang
2014-12-16  9:34             ` Russell King - ARM Linux
2014-12-16  9:48               ` Kuankuan.Yang
2014-12-15  2:56 ` [PATCH 6/6] ARM: dts: rockchip: add hdmi audio nodes Yakir Yang
2014-12-15 10:38 ` [RFC PATCH 0/6] Those patches is used for dw_hdmi audio Russell King - ARM Linux
     [not found]   ` <548EC9E1.5040206@rock-chips.com>
2014-12-15 11:52     ` Kuankuan.Yang [this message]
2014-12-15 12:00       ` Russell King - ARM Linux
2014-12-15 12:46         ` Kuankuan.Yang
2014-12-15 15:48         ` Jean-Francois Moine

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=548ECB66.70004@rock-chips.com \
    --to=ykk@rock-chips.com \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).