From: Mark Brown <broonie@kernel.org>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: sound: add Microsemi ZL38060 binding
Date: Mon, 20 Apr 2020 13:53:48 +0100 [thread overview]
Message-ID: <20200420125348.GC10045@sirena.org.uk> (raw)
In-Reply-To: <CAGngYiV9MxeLrERkgU2+rucCiJ5StCXN7GXxKLMfaJ-bqSpAAw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On Mon, Apr 20, 2020 at 08:50:45AM -0400, Sven Van Asbroeck wrote:
> On Mon, Apr 20, 2020 at 8:25 AM Mark Brown <broonie@kernel.org> wrote:
> >
> > I'd expect someone with knowledge of the hardware such as yourself.
>
> I claim no expertise - I was just getting tired of dragging the
> out-of-tree vendor
> driver for this chip from kernel to kernel. AFAIK, most people using this chip
> have forked the vendor driver and adapted it to their specific needs.
> If my name has to be there, I'd be keen to hand it over once someone more
> familiar with this chip comes along.
I think by virtue of taking this step you have become the de facto
upstream expert on this chip! Like you say hopefully someone more
familiar (ideally from Microsemi) will turn up.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-20 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 22:13 [PATCH v2 1/2] dt-bindings: sound: add Microsemi ZL38060 binding Sven Van Asbroeck
2020-04-17 22:13 ` [PATCH v2 2/2] ASoC: Add initial ZL38060 driver Sven Van Asbroeck
2020-04-20 12:15 ` [PATCH v2 1/2] dt-bindings: sound: add Microsemi ZL38060 binding Mark Brown
2020-04-20 12:22 ` Sven Van Asbroeck
2020-04-20 12:25 ` Mark Brown
2020-04-20 12:50 ` Sven Van Asbroeck
2020-04-20 12:53 ` Mark Brown [this message]
2020-04-21 18:22 ` Mark Brown
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=20200420125348.GC10045@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=thesven73@gmail.com \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).