From: Mark Brown <broonie@kernel.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Bayyavarapu, Maruthi" <maruthi.bayyavarapu@amd.com>,
Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Alex Deucher <alexander.deucher@amd.com>,
Dave Airlie <airlied@gmail.com>
Subject: Re: [PATCH 3/3] ASoC: AMD: add AMD ASoC ACP-I2S driver [v4]
Date: Thu, 20 Aug 2015 16:45:37 -0700 [thread overview]
Message-ID: <20150820234537.GA12027@sirena.org.uk> (raw)
In-Reply-To: <CADnq5_OGvvbq7=mc5JtcdA2zouUvk1VhV5pHg-Rbp2szQhA2KA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1524 bytes --]
On Thu, Aug 20, 2015 at 07:11:22PM -0400, Alex Deucher wrote:
> On Thu, Aug 20, 2015 at 6:31 PM, Mark Brown <broonie@kernel.org> wrote:
> > DRM is a special case here since there has always been work to share
> > bits of the code with other operating systems, the licensing for DRM is
> > very unusual within the kernel. A quick sampling of drivers suggests
> > that this license is not universally used there either.
> > There is also the issue I raised with the fact that your non-GPL license
> > statement does not appear to correspond to the MODULE_LICENSE() that
> > you've included which claims the code is GPLed.
> Once again this is exactly what the other drm drivers and support
> modules do. AMD generally prefers to contribute code licensed under
> an MIT/X11 style licence which is why we've done this. IANAL, but I
> think that is compatible with "GPL and additional rights".
This is not a DRM driver, it is an ASoC driver, and like I say DRM is a
bit special. I do note that AMD has contributed at least its CCP and
cpufreq drivers (indeed all their non-DRM code I could find with
explicit license statements) under a normal kernel license. As far as I
can tell this licensing is entirely confined to the DRM drivers.
I am not readily able to convince myself that this is compatible with
the intent of exporting the ASoC APIs _GPL(), this looks like it can be
used as the basis for a shim layer for non-GPL code (the licensing
strategy seems very similar). I'd need to think through this carefully.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-08-20 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 20:09 [PATCH 0/3] Add ASoC support for AMD APUs [v2] Alex Deucher
2015-08-20 20:09 ` [PATCH 2/3] drm/amd: add ACP driver support [v6] Alex Deucher
2015-08-20 20:09 ` [PATCH 3/3] ASoC: AMD: add AMD ASoC ACP-I2S driver [v4] Alex Deucher
2015-08-20 21:13 ` Mark Brown
2015-08-20 21:30 ` Alex Deucher
2015-08-20 22:31 ` Mark Brown
2015-08-20 23:11 ` Alex Deucher
2015-08-20 23:45 ` Mark Brown [this message]
2015-08-20 23:50 ` Alex Deucher
2015-08-21 0:10 ` Mark Brown
2015-08-21 2:05 ` Alex Deucher
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=20150820234537.GA12027@sirena.org.uk \
--to=broonie@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=maruthi.bayyavarapu@amd.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