lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 19 Jan 2008 17:00:31 +0000
From:	Mark Brown <>
To:	Dmitry Baryshkov <>
Subject: Re: [PATCH] Core driver for WM97xx touchscreens

On Fri, Jan 18, 2008 at 06:11:45PM +0000, Dmitry Baryshkov wrote:
> Dmitry Torokhov wrote:

> > I will need some more time to review and understand the need for the new
> > bus in the driver.

> Most likely this can be converted to platform_bus. Maybe this can also get

Could you expand on how you see that being implemented, please?  It
doesn't feel entirely comfortable to me - providing a bus for the chip
seems more direct and the platform bus not what I'd think of using for
something hanging off another bus - but I think I'm just not visualising
what you're thinking of properly.

> help from soon-to-be posted MFD (multi function devices) helpers.

The multi-function device support does feel like it could be a good fit.
I'd seen it discussed sometime last year but don't recall seeing
anything for quite a while.  Like Ben said, any pointers to current work
would be appreciated.

It's probably worth mentioning that in addition to what is in the
current patch series these chips all also provide an audio codec which
requires a reasonably substantial driver for full support.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists