From: pavan_savoy@ti.com
To: linux-kernel@vger.kernel.org, gregkh@suse.de
Cc: Pavan Savoy <pavan_savoy@ti.com>
Subject: [PATCH 0/7] TI ST patches for new requirements
Date: Fri, 4 Feb 2011 02:23:08 -0600 [thread overview]
Message-ID: <1296807795-5408-1-git-send-email-pavan_savoy@ti.com> (raw)
From: Pavan Savoy <pavan_savoy@ti.com>
Greg,
(re-submitting series, after documenting sysfs-platform-kim..)
The following 7 patches are some major updates that has been going on
in the Texas Instrument's shared transport driver.
These contain few new requirements and some cleanup patches.
The major 2 changes are the first 2 patches.
1. The change from protocol based registration to packet/channel based
registration has been conceptually ACKed by Gustavo (Bluetooth Maintainer).
With this TI-ST now no longer refers to bluetooth headers which was a concern
previously.
2. The 2nd major change is from rfkill based communication to normal sysfs
entry based communication.
This has been conceptually ACKed by Samuel Ortiz (MFD Maintainer).
Previously when the line discipline driver wanted the UART to be opened
and ldisc to be installed, it ab-used the rfkill device node to notify the
user-space daemon, Now it notifies using simpler sysfs entries & making use
of sysfs_notify.
This also allows the UART specifics to be shared with user-space.
Other patches include fixing left over error codes, correcting few dbug logs,
fixes for bugs found during stress testing, firmware change & cleanup.
Pavan Savoy (7):
drivers:misc: ti-st: register with channel IDs
drivers:misc: ti-st: move from rfkill to sysfs
drivers:misc: ti-st: fix error codes
drivers:misc: ti-st: set right debug levels for logs
drivers:misc: ti-st: firmware download optimization
drivers:misc: ti-st: fix hci-ll on wake_ind collision
drivers:misc: ti-st: remove multiple gpio handling
Documentation/ABI/testing/sysfs-platform-kim | 48 +++
drivers/misc/ti-st/st_core.c | 413 ++++++++--------------
drivers/misc/ti-st/st_kim.c | 491 +++++++++++++-------------
drivers/misc/ti-st/st_ll.c | 10 +-
include/linux/ti_wilink_st.h | 76 +++--
5 files changed, 494 insertions(+), 544 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-platform-kim
next reply other threads:[~2011-02-04 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 8:23 pavan_savoy [this message]
2011-02-04 8:23 ` [PATCH 1/7] drivers:misc: ti-st: register with channel IDs pavan_savoy
2011-02-04 8:23 ` [PATCH 2/7] drivers:misc: ti-st: move from rfkill to sysfs pavan_savoy
2011-02-04 8:23 ` [PATCH 3/7] drivers:misc: ti-st: fix error codes pavan_savoy
2011-02-04 8:23 ` [PATCH 4/7] drivers:misc: ti-st: set right debug levels for logs pavan_savoy
2011-02-04 8:23 ` [PATCH 5/7] drivers:misc: ti-st: firmware download optimization pavan_savoy
2011-02-04 8:23 ` [PATCH 6/7] drivers:misc: ti-st: fix hci-ll on wake_ind collision pavan_savoy
2011-02-04 8:23 ` [PATCH 7/7] drivers:misc: ti-st: remove multiple gpio handling pavan_savoy
-- strict thread matches above, loose matches on Subject: below --
2011-02-02 11:00 [PATCH 0/7] TI ST patches for new requirements pavan_savoy
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=1296807795-5408-1-git-send-email-pavan_savoy@ti.com \
--to=pavan_savoy@ti.com \
--cc=gregkh@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®