From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Lee Jones <lee@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: the pcf50633 - dead?
Date: Sun, 9 Mar 2025 12:26:18 +0000 [thread overview]
Message-ID: <Z82I6vuJPufg6mjA@gallifrey> (raw)
In-Reply-To: <d68fbcda-d77c-4426-b579-57010de82c7b@app.fastmail.com>
* Arnd Bergmann (arnd@arndb.de) wrote:
> On Sun, Mar 9, 2025, at 04:03, Dr. David Alan Gilbert wrote:
> > Hi Arnd,
> > My scripts noticed pcf50633_adc_sync_read and a load of other
> > pcf50633 symbols weren't called; and hmm I'm pretty sure most of it's
> > dead.
> > Your:
> > 61b7f8920b176e3cb86c3b5e7c866261720a7917
> > ARM: s3c: remove all s3c24xx support
> > removed the last/only includes of any of the pcf50633 headers,
> > I think it was part of openmoko.
> > The only place I see it enabled (=m) in a config is
> > arch/mips/configs/ip27_defconfig which is the ancient SGI Onyx
> > which predates the pcf50633 by a good few years (and is definitely
> > not portable and battery powered!)
>
> Yes, I have that one on my list of drivers that are unused upstream
> and should be cleaned up.
>
> See also my reply at [1], feel free to send patches for any of those.
Ooh, Juicy list!
I'll probably do the pcf50633 soon, and I've made a note of that list.
Thanks,
Dave
> Arnd
>
> [1] https://lore.kernel.org/lkml/a15bb180-401d-49ad-a212-0c81d613fbc8@app.fastmail.com/
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
prev parent reply other threads:[~2025-03-09 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 2:03 the pcf50633 - dead? Dr. David Alan Gilbert
2025-03-09 8:04 ` Arnd Bergmann
2025-03-09 12:26 ` Dr. David Alan Gilbert [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=Z82I6vuJPufg6mjA@gallifrey \
--to=linux@treblig.org \
--cc=arnd@arndb.de \
--cc=lee@kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox