From: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk,
kernel-discuss@handhelds.org
Subject: Re: [RFC, PATCH 0/4] SoC base drivers
Date: Tue, 01 May 2007 20:29:13 +0400 [thread overview]
Message-ID: <46376AD9.3020701@gmail.com> (raw)
In-Reply-To: <1068016897.20070501173657@gmail.com>
Paul Sokolovsky wrote:
> Hello Dmitry,
>
> Tuesday, May 1, 2007, 4:53:09 PM, you wrote:
>
>> I think your referring to the term "SoC (system-on-chip)" is confusing
>> (at least for me). You rather consider companion chips than SoCs.
>
>> Yes, any chip integrating a number of controllers could be considered
>> as a system-on-chip but if the chip doesn't make sense without
>> some master chip (processor) I'd consider the chip as a companion
>> (to the processor) chip.
>
> Ditto for me - I find "companion" thing confusing. What's
> important for the RFC/topic discussed is that it is integrated
> controller with many diversified functions, not what it is helper to
> something.
It's exactly helper. It helps to expand functionality of a main
processor.
> I understand that for many people SoC means CPU with ties,
> but IMHO, it's less stretch to take such chip, remove CPU, and still
> call it a SoC,
I do not know any chip that would be "just add a CPU and you'll get
a complete system", do you?
> than call an integrated audio/touchscreen controller a
> companion chip (well, of course it is; and RAM chip too ;-) ).
>
> 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.
If you used ASIC acronym it would be more appropriate and not so
ambiguous.
What kind of chips you deal with does not fit ASIC acronym?
> 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.
"peripheral/integrated controllers" are also within companion chips.
Every type of CMOS devices may be a part of processor chip or
may be a standalone chip as well as a group of CMOS devices
may be a part of the proc chip or may organize a standalone chip.
When your chip is missing a processor device then it is not
a system but a part of a system, you can not build a complete
system on a such chip, so you can not call it a "system-on-chip".
> But renaming
> drivers/soc/ to drivers/companion/ would be more confusing,
Not for me.
> 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).
>
>
Regards,
Dmitry
next prev parent reply other threads:[~2007-05-01 16:29 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
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 [this message]
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=46376AD9.3020701@gmail.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.