From: Archit Taneja <architt@codeaurora.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
Mark Brown <broonie@kernel.org>, David Airlie <airlied@linux.ie>,
Fabio Estevam <fabio.estevam@freescale.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Koji Matsuoka <koji.matsuoka.xm@renesas.com>,
Thierry Reding <treding@nvidia.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>, Simon <horms@verge.net.au>,
linux-renesas-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Jose Abreu <joabreu@synopsys.com>
Subject: Re: [PATCH v4] drm: bridge: add DesignWare HDMI I2S audio support
Date: Thu, 24 Nov 2016 13:34:03 +0530 [thread overview]
Message-ID: <626df165-da09-298e-ed60-03d4119caec2@codeaurora.org> (raw)
In-Reply-To: <87vavdcvgh.wl%kuninori.morimoto.gx@renesas.com>
Hi,
On 11/24/2016 10:43 AM, Kuninori Morimoto wrote:
>
> Hi Archit, David, and DRM ML
>
> I had heared that Archit is the maintainer of dw-hdmi driver, but am I wrong ??
> I'm posting this patch series since half year ago, but no response
> from him, and nothing happen (I got review from Russell though).
> Is Archit really maintainer ??
> OTOH, get_maintainer.pl indicates David is the maintainer ?
> What should I do for this patch ??
I'm not the maintainer of the dw-hdmi driver, but I pull in the
changes that go into drm/bridge/
Will pull this.
Thanks,
Archit
>
>> Hi Russell
>>
>>>> @@ -11,4 +11,11 @@ struct dw_hdmi_audio_data {
>>>> u8 *eld;
>>>> };
>>>>
>>>> +struct dw_hdmi_i2s_audio_data {
>>>> + struct dw_hdmi *hdmi;
>>>> +
>>>> + void (*write)(struct dw_hdmi *hdmi, u8 val, int offset);
>>>> + u8 (*read)(struct dw_hdmi *hdmi, int offset);
>>>> +};
>>>
>>> Another slight concern here is why we need this separate data for i2s -
>>> maybe adding the write/read ops to struct dw_hdmi_audio_data would be
>>> a better thing to do, which would then allow the AHB audio to drop
>>> the .base argument in the future.
>>>
>>> I'm not that bothered about this though. So...
>>
>> Thank you for your feedback.
>> Maybe we can merge these in incremental patch if needed ?
>>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-11-24 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 1:00 Kuninori Morimoto
2016-11-08 11:10 ` Russell King - ARM Linux
2016-11-09 0:47 ` Kuninori Morimoto
2016-11-24 5:13 ` Kuninori Morimoto
2016-11-24 8:04 ` Archit Taneja [this message]
2016-11-24 8:08 ` Kuninori Morimoto
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=626df165-da09-298e-ed60-03d4119caec2@codeaurora.org \
--to=architt@codeaurora.org \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@freescale.com \
--cc=horms@verge.net.au \
--cc=joabreu@synopsys.com \
--cc=koji.matsuoka.xm@renesas.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=treding@nvidia.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
Powered by JetHome