From: Richard Purdie <rpurdie@rpsys.net>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>,
kernel-discuss@handhelds.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [RFC, PATCH 0/4] SoC base drivers
Date: Tue, 01 May 2007 16:01:15 +0100 [thread overview]
Message-ID: <1178031675.5883.67.camel@localhost.localdomain> (raw)
In-Reply-To: <1068016897.20070501173657@gmail.com>
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
next prev parent reply other threads:[~2007-05-01 15:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 5:08 [RFC, PATCH 0/4] SoC base drivers Paul Sokolovsky
2007-05-01 8:39 ` Ben Dooks
2007-05-01 10:11 ` Paul Sokolovsky
2007-05-01 10:33 ` ian
2007-05-01 13:53 ` Dmitry Krivoschekov
2007-05-01 14:36 ` Paul Sokolovsky
2007-05-01 15:01 ` Richard Purdie [this message]
2007-05-01 17:18 ` Paul Sokolovsky
2007-05-01 18:58 ` Richard Purdie
2007-05-01 19:27 ` Russell King
2007-05-01 16:29 ` Dmitry Krivoschekov
2007-05-01 18:08 ` [Kernel-discuss] " ian
2007-05-01 19:08 ` Dmitry Krivoschekov
2007-05-01 20:09 ` Paul Sokolovsky
2007-05-01 21:17 ` Dmitry Krivoschekov
2007-05-02 13:39 ` Paul Sokolovsky
2007-05-01 15:55 ` ian
2007-05-01 16:38 ` Dmitry Krivoschekov
2007-05-01 17:12 ` Paul Sokolovsky
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=1178031675.5883.67.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=dmitry.krivoschekov@gmail.com \
--cc=kernel-discuss@handhelds.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pmiscml@gmail.com \
/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