linux-kernel - Re: [RFC, PATCH 0/4] SoC base drivers

lists.openwall.net		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 linux-cve-announce 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:	Tue, 01 May 2007 11:33:27 +0100
From:	ian <spyro@....com>
To:	Ben Dooks <ben-linux-arm@...ff.org>
Cc:	Paul Sokolovsky <pmiscml@...il.com>, kernel-discuss@...dhelds.org,
	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [RFC, PATCH 0/4] SoC base drivers

On Tue, 2007-05-01 at 09:39 +0100, Ben Dooks wrote:
> 
> Wow, platform devices with a new name. I don't see how any of this is
> not handled by platfrom device.

No, not so. That was a criticism levelled at a previous incarnation of
this code which has since been addressed - this is now a convienience
layer on top of platform device, as opposed to what it used to be - a
complete device class of its own.

It eliminates a _lot_ of code duplication for hh.org, where we have
multiple machines with multiple CPU types all sharing multiple SoC chips
which have varying subsets of decices in them (eg. the TMIO SoCs share
MMC blocks with the ASIC3 ones, w1 is shared in a few devices, etc.)

> Anything registering new IRQs could create sub platform devices
> with the correct resources.

Which is exactly what this code does, but without requiring each and
every platform to rewrite the same glue code over and over.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/