From: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
To: ian <spyro@f2s.com>
Cc: Paul Sokolovsky <pmiscml@gmail.com>,
kernel-discuss@handhelds.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [Kernel-discuss] Re: [RFC, PATCH 0/4] SoC base drivers
Date: Tue, 01 May 2007 23:08:23 +0400 [thread overview]
Message-ID: <46379027.7050202@gmail.com> (raw)
In-Reply-To: <1178042924.15769.5.camel@wirenth>
ian wrote:
> On Tue, 2007-05-01 at 20:29 +0400, Dmitry Krivoschekov wrote:
>> If you used ASIC acronym it would be more appropriate and not so
>> ambiguous.
>
> Actually, thats not bad. I'd be ok with that is SoC isnt used.
>
I'm ok with that too, i.e. very rough definition is:
SoC (system-on-chip) is a platform level chip which incorporates processor
devices (CPU, cache, coprocessors, memory controller etc.), system devices
(timers, interrupt controllers etc.) and peripheral devices
(UARTs, LCD controllers, USB controllers etc),
while ASIC (Application-specific integrated circuit) is also a platform
level
chip which incorporates peripheral and system devices but does not include
processor devices. ASICs are designed to expand processor functionality,
it could supplement a normal processor (non-SoC) and also could supplement
a SoC processor.
ASIC-related code (I mean core) forms additional platform layer, so I
suggest
adding ASIC helpers to generic platform code i.e. drivers/platform.c, but
ASIC drivers to drivers/asic/ directory.
Regards,
Dmitry
next prev parent reply other threads:[~2007-05-01 19:08 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
2007-05-01 18:08 ` [Kernel-discuss] " ian
2007-05-01 19:08 ` Dmitry Krivoschekov [this message]
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=46379027.7050202@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 \
--cc=spyro@f2s.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