mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Curtis Malainey <cujomalainey@google.com>
Cc: Fletcher Woodruff <fletcherw@chromium.org>,
	Cezary Rojewski <cezary.rojewski@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jaroslav Kysela <perex@perex.cz>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Oder Chiou <oder_chiou@realtek.com>,
	Takashi Iwai <tiwai@suse.com>,
	Curtis Malainey <cujomalainey@chromium.org>,
	Ross Zwisler <zwisler@chromium.org>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v7 3/4] ASoC: rt5677: clear interrupts by polarity flip
Date: Tue, 18 Jun 2019 19:47:10 +0100	[thread overview]
Message-ID: <20190618184710.GP5316@sirena.org.uk> (raw)
In-Reply-To: <CAOReqxhETC9xAojXyDWLMOJ3W22Zn4GNGry44=XC=t_k7SCHqA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

On Tue, Jun 18, 2019 at 11:12:58AM -0700, Curtis Malainey wrote:
> On Tue, Jun 18, 2019 at 11:01 AM Fletcher Woodruff
> > On Sun, Jun 16, 2019 at 10:56 AM Cezary Rojewski
> > > On 2019-06-14 21:48, Fletcher Woodruff wrote:

> > > > +     ret = regmap_read(rt5677->regmap, RT5677_IRQ_CTRL1, &reg_irq);
> > > > +     if (ret) {
> > > > +             pr_err("rt5677: failed reading IRQ status: %d\n", ret);

> > > The entire rt5677 makes use of dev_XXX with the exception of.. this very
> > > function. Consider reusing "component" field which is already part of
> > > struct rt5677_priv and removing pr_XXX.

> > I was using dev_XXX, but I believe Curtis found that 'component' was
> > sometimes uninitialized when this function was called, so I switched
> > back to pr_XXX. I may be misremembering though, so I'll let Curtis
> > comment as well.

> The issue here is that the IRQ is setup in the i2c probe and the
> component is setup in the codec probe. In theory if the hardware is in

The component is not needed for a struct device, you must have a struct
device if you have a regmap or have probed at all.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-06-18 18:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 19:48 [PATCH v7 0/4] Fix jack detection for Chromebook Pixel Fletcher Woodruff
2019-06-14 19:48 ` [PATCH v7 1/4] ASoC: rt5677: fall back to DT prop names on error Fletcher Woodruff
2019-06-17 15:24   ` Applied "ASoC: rt5677: fall back to DT prop names on error" to the asoc tree Mark Brown
2019-06-14 19:48 ` [PATCH v7 2/4] ASoC: rt5677: move jack-detect init to i2c probe Fletcher Woodruff
2019-06-17 15:24   ` Applied "ASoC: rt5677: move jack-detect init to i2c probe" to the asoc tree Mark Brown
2019-06-14 19:48 ` [PATCH v7 3/4] ASoC: rt5677: clear interrupts by polarity flip Fletcher Woodruff
2019-06-16 16:56   ` Cezary Rojewski
2019-06-18 18:00     ` Fletcher Woodruff
2019-06-18 18:12       ` Curtis Malainey
2019-06-18 18:47         ` Mark Brown [this message]
2019-06-18 19:10           ` Curtis Malainey
2019-06-14 19:48 ` [PATCH v7 4/4] ASoC: rt5677: handle concurrent interrupts Fletcher Woodruff

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=20190618184710.GP5316@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=cezary.rojewski@intel.com \
    --cc=cujomalainey@chromium.org \
    --cc=cujomalainey@google.com \
    --cc=fletcherw@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oder_chiou@realtek.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=zwisler@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®