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]

Message-Id: <1178031675.5883.67.camel@localhost.localdomain>
Date:	Tue, 01 May 2007 16:01:15 +0100
From:	Richard Purdie <rpurdie@...ys.net>
To:	Paul Sokolovsky <pmiscml@...il.com>
Cc:	Dmitry Krivoschekov <dmitry.krivoschekov@...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 17:36 +0300, Paul Sokolovsky wrote:
>         Either way, I don't pledge to be a HW designer with
> contemporary lexicon. The aim was simple - as a single word would be
> too ambiguous, general, or vice-versa, omitting, then acronym is
> needed, hopefully existing, and not new, and SoC is the most fitting
> TLA, IMHO. But I'm open to specific suggestions for improvement. For
> example, if I was to write a Documentation/ entry for that, I'd mention
> companion chips, peripheral/integrated controllers, etc. But renaming
> drivers/soc/ to drivers/companion/ would be more confusing, as the
> concept described is not tied to companion chips per se (even though
> many of chips we (handhelds.org) deal with, can be classified as
> such).

A while back I proposed drivers/mfd/ (multi function devices) and there
are a couple of drivers in there in mainline which probably fit your
description of SoC. The code I had once intended for there is probably
more ASoC related now...

Richard





-
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/