All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] arm: omap2: n8x0: stop instantiating codec platform data
Date: Thu, 3 Nov 2022 14:46:08 +0200	[thread overview]
Message-ID: <Y2O4EMn4Ja/DeHZH@atomide.com> (raw)
In-Reply-To: <Y2Ow81ALm1Osd8xM@sirena.org.uk>

* Mark Brown <broonie@kernel.org> [221103 12:06]:
> On Wed, Nov 02, 2022 at 04:20:02PM -0700, Dmitry Torokhov wrote:
> > As of 0426370b58b2 ("ARM: dts: omap2420-n810: Correct the audio codec
> > (tlv320aic33) node") the DTS properly specifies reset GPIO, and the
> > device name in auxdata lookup table does not even match the one in
> > device tree anymore, so stop instantiating it.
> 
> Tony, I guess it makes sense for this to go via ASoC if you're OK with
> it?

Yes please pick it via ASoC, I've acked the first patch.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] arm: omap2: n8x0: stop instantiating codec platform data
Date: Thu, 3 Nov 2022 14:46:08 +0200	[thread overview]
Message-ID: <Y2O4EMn4Ja/DeHZH@atomide.com> (raw)
In-Reply-To: <Y2Ow81ALm1Osd8xM@sirena.org.uk>

* Mark Brown <broonie@kernel.org> [221103 12:06]:
> On Wed, Nov 02, 2022 at 04:20:02PM -0700, Dmitry Torokhov wrote:
> > As of 0426370b58b2 ("ARM: dts: omap2420-n810: Correct the audio codec
> > (tlv320aic33) node") the DTS properly specifies reset GPIO, and the
> > device name in auxdata lookup table does not even match the one in
> > device tree anymore, so stop instantiating it.
> 
> Tony, I guess it makes sense for this to go via ASoC if you're OK with
> it?

Yes please pick it via ASoC, I've acked the first patch.

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-11-03 12:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 23:20 [PATCH 1/3] arm: omap2: n8x0: stop instantiating codec platform data Dmitry Torokhov
2022-11-02 23:20 ` Dmitry Torokhov
2022-11-02 23:20 ` [PATCH 2/3] ASoC: tlv320aic3x: remove support for " Dmitry Torokhov
2022-11-02 23:20   ` Dmitry Torokhov
2022-11-02 23:20 ` [PATCH 3/3] ASoC: tlv320aic3x: switch to using gpiod API Dmitry Torokhov
2022-11-02 23:20   ` Dmitry Torokhov
2022-11-03 12:15 ` [PATCH 1/3] arm: omap2: n8x0: stop instantiating codec platform data Mark Brown
2022-11-03 12:15   ` Mark Brown
2022-11-03 12:46   ` Tony Lindgren [this message]
2022-11-03 12:46     ` Tony Lindgren
2022-11-03 12:45 ` Tony Lindgren
2022-11-03 12:45   ` Tony Lindgren
2022-11-03 16:35 ` Mark Brown
2022-11-03 16:35   ` 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=Y2O4EMn4Ja/DeHZH@atomide.com \
    --to=tony@atomide.com \
    --cc=broonie@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.