From: Rodolfo Giometti <giometti@linux.it>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>, Greg KH <greg@kroah.com>
Subject: Support for Silicon C2 Interface.
Date: Fri, 3 Oct 2008 16:36:28 +0200 [thread overview]
Message-ID: <1223044589-31741-1-git-send-email-giometti@linux.it> (raw)
In-Reply-To: <>
C2 port implements a two wire serial communication protocol (bit
banging) designed to enable in-system programming, debugging, and
boundary-scan testing on low pin-count Silicon Labs devices.
Main references are at Silicon Laboratories site:
* AN127: FLASH Programming via the C2 Interface
http://www.silabs.com/public/documents/tpub_doc/anote/Microcontrollers/Small_Form_Factor/en/an127.pdf
* C2 Specification
http://www.silabs.com/public/documents/tpub_doc/spec/Microcontrollers/en/C2spec.pdf
Currently this code supports only flash programming through sysfs
interface but extensions shoud be easy to add.
I know that this (proposal) patch may be incomplete but I'd like to
know what you are thinking about it before continuing further. For example
I'd like to know if should I put the C2 port core here or into proper
subdirectory of linux/drivers/misc/ where clients can be placed also.
Thanks for your suggestions,
Rodolfo
--
drivers/misc/Kconfig | 13
drivers/misc/Makefile | 1
drivers/misc/c2port_core.c | 996 +++++++++++++++++++++++++++++++++++++++++++++
include/linux/c2port.h | 65 ++
4 files changed, 1075 insertions(+)
next reply other threads:[~2008-10-03 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 14:36 Rodolfo Giometti [this message]
2008-10-03 14:36 ` [PATCH 1/1] Add c2 port support Rodolfo Giometti
2008-10-03 21:59 ` Greg KH
2008-10-07 9:38 ` Rodolfo Giometti
2008-10-07 17:30 ` Greg KH
2008-10-07 19:14 ` Rodolfo Giometti
2008-10-07 20:00 ` Greg KH
2008-10-07 20:27 ` Rodolfo Giometti
2008-10-03 14:49 ` Support for Silicon C2 Interface Greg KH
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=1223044589-31741-1-git-send-email-giometti@linux.it \
--to=giometti@linux.it \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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.