From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, Jim Qu <Jim.Qu@amd.com>,
Mark Brown <broonie@kernel.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [alsa-devel] [PATCH v2 0/3] Make the audio component binding more generic
Date: Thu, 19 Jul 2018 18:26:28 -0500 [thread overview]
Message-ID: <136e40e7-8667-8816-108b-7102c8f963d8@linux.intel.com> (raw)
In-Reply-To: <s5hpnzj3vhb.wl-tiwai@suse.de>
On 7/19/18 1:56 PM, Takashi Iwai wrote:
> On Thu, 19 Jul 2018 15:05:45 +0200,
> Pierre-Louis Bossart wrote:
>>
>> On 7/19/18 12:50 AM, Takashi Iwai wrote:
>>> On Wed, 18 Jul 2018 22:54:35 +0200,
>>> Pierre-Louis Bossart wrote:
>>>>
>>>>
>>>>
>>>> On 07/17/2018 04:26 AM, Takashi Iwai wrote:
>>>>> Hi,
>>>>>
>>>>> this is a preliminiary patch set to convert the existing i915 /
>>>>> HD-audio component binding to be applicable to other drivers like
>>>>> radeon / amdgpu. This patchset itself doesn't change the
>>>>> functionality but only renames and split to a new drm_audio_component
>>>>> stuff from i915_audio_component.
>>>>>
>>>>> The actual usage of the new API will follow once after this one gets
>>>>> reviewed / accepted. The whole patches (including this patchset) are
>>>>> found in topic/hda-acomp branch of sound.git tree.
>>>>>
>>>>> BTW, since the whole stuff is about the audio binding, I suppose these
>>>>> will go through sound git tree. Let me know if anyone has concerns.
>>>> No objections but a slight concern that this will conflict with the
>>>> HDAudio+DSP patches that I was about to resubmit on top of your
>>>> topic/hda-core-intel branch. the two series touch the same files so
>>>> it'd be a miracle if there is no issue.
>>>> How do you want to deal with this?
>>>
>>> Does it conflict severely? If it's trivial, it can be resolved at
>>> merge time, too. The changes in my patchset are fairly trivial, so it
>>> shouldn't be too hard.
>>
>> I was able to make things work by taking your topic/hda-core-intel,
>> merge it on Mark's for-next, then add my additional changes and these
>> DRM changes. The last two can be done in any order. But I am getting
>> some conflicts if I try to apply these DRM changes first, not sure why
>> git is complaining though, the changes look trivial enough.
>> So yes it looks possible to deal with the two series in parallel, will
>> send my update later today.
>
> OK, since my changes are relatively trivial to deal with, I merge the
> changes to for-next branch now.
>
> If your patches can be respinned, maybe it's easier to be rebased on
> top of these merges.
I was planning to resend them tomorrow after internal reviews (mostly
changes in the detection/enablement of the HDaudio+DSP case). If you
want to take a look in the mean time the patches are here:
https://github.com/plbossart/sound/commits/upstream/hda2
I can rebase them as needed, no big deal.
Thanks
-Pierre
>
> Mark, could you merge topic/drm_audio_component branch into yours, if
> Pierre's patchset won't go in immediately? It's an immutable branch,
> including already topic/hda-core-intel in itself.
>
>
> thanks,
>
> Takashi
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-07-19 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 9:26 [PATCH v2 0/3] Make the audio component binding more generic Takashi Iwai
2018-07-17 9:26 ` [PATCH v2 1/3] drm/i915: Split audio component to a generic type Takashi Iwai
2018-07-17 20:06 ` Rodrigo Vivi
2018-07-17 9:26 ` [PATCH v2 2/3] ALSA: hda/i915: Associate audio component with devres Takashi Iwai
2018-07-17 9:26 ` [PATCH v2 3/3] ALSA: hda: Make audio component support more generic Takashi Iwai
2018-07-18 20:54 ` [alsa-devel] [PATCH v2 0/3] Make the audio component binding " Pierre-Louis Bossart
2018-07-19 5:50 ` Takashi Iwai
2018-07-19 13:05 ` Pierre-Louis Bossart
2018-07-19 18:56 ` Takashi Iwai
2018-07-19 23:26 ` Pierre-Louis Bossart [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=136e40e7-8667-8816-108b-7102c8f963d8@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=Jim.Qu@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=tiwai@suse.de \
/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).