From: Mark Brown <broonie@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: Weidong Wang <wangweidong.a@awinic.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] ASoC: codecs: aw88261: Remove non-existing reset gpio
Date: Fri, 29 Sep 2023 14:54:27 +0200 [thread overview]
Message-ID: <ZRbJAwoanwLnnaJ1@finisterre.sirena.org.uk> (raw)
In-Reply-To: <CVVET1A2CO26.3O47662JKAL6@otso>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On Fri, Sep 29, 2023 at 02:44:47PM +0200, Luca Weiss wrote:
> Unfortunately the dt binding is a bit trickier to update since it's made
> for both AW88261 and AW88395.
> After spending a bit of time using non-Google search machines (Google
> seems incapable of finding anything there) I found a datasheet for
> AW88395 and that does appear to have a RSTN "Active low hardware reset"
> pin so we should not remove that one.
> Probably it's easier to separate the two dt bindings then, instead of
> trying to keep them together?
You can do conditionals based on compatibles so it might not be
required.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-09-29 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 10:28 [PATCH RFC] ASoC: codecs: aw88261: Remove non-existing reset gpio Luca Weiss
2023-09-29 12:30 ` Mark Brown
2023-09-29 12:44 ` Luca Weiss
2023-09-29 12:54 ` Mark Brown [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=ZRbJAwoanwLnnaJ1@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=perex@perex.cz \
--cc=phone-devel@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=wangweidong.a@awinic.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).