From: Lee Jones <lee@kernel.org>
To: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>
Cc: tony@atomide.com, robh@kernel.org, wens@csie.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: twl6030-irq: Revert to use of_match_device()
Date: Thu, 30 Nov 2023 14:05:48 +0000 [thread overview]
Message-ID: <20231130140548.GL1470173@google.com> (raw)
In-Reply-To: <74b0b808-7b97-4e53-a1a4-6e2e1274ecff@gmail.com>
On Thu, 23 Nov 2023, Péter Ujfalusi wrote:
>
>
> On 23/11/2023 12:41, Lee Jones wrote:
> >>> @@ -368,10 +368,10 @@ int twl6030_init_irq(struct device *dev, int irq_num)
> >>> int nr_irqs;
> >>> int status;
> >>> u8 mask[3];
> >>> - const int *irq_tbl;
> >>> + const struct of_device_id *of_id;
> >>>
> >>> - irq_tbl = device_get_match_data(dev);
> >>> - if (!irq_tbl) {
> >>> + of_id = of_match_device(twl6030_of_match, dev);
> >>
> >> I think you just dropped support for ACPI.
> >
> > Ah, scrap that. I was looking at the wrong part of 1e0c866887f4.
> >
> > So what about the other drivers changed in the aforementioned commit?
>
> Looking back at it again, I think only this patch is needed.
> This is not a real driver, it is using the twl core's device.
> The twl6030 is for sure broken, let me reply to the twl4030-power in a sec.
>
> > Ideally we'd have a call that covers all of the various probing APIs.
> >
> >> Rob, care to follow-up?
Rob, last chance to state your case before I apply it.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-11-30 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 11:48 [PATCH] mfd: twl6030-irq: Revert to use of_match_device() Peter Ujfalusi
2023-11-23 10:37 ` Lee Jones
2023-11-23 10:41 ` Lee Jones
2023-11-23 15:40 ` Péter Ujfalusi
2023-11-30 14:05 ` Lee Jones [this message]
2023-12-01 11:30 ` (subset) " Lee Jones
2024-02-19 9:52 ` Andreas Schwab
2024-02-19 14:33 ` Lee Jones
2024-02-26 11:36 ` Tony Lindgren
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=20231130140548.GL1470173@google.com \
--to=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=robh@kernel.org \
--cc=tony@atomide.com \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).