Permalink
Branch: gingerbread
Commits on Jun 5, 2012
  1. disable some cpufreq_direct_set_policy function to make kernel not "F…

    phiexz committed Jun 5, 2012
    …ORCE BACK" to ondemand when turn off S5K5CAGX sensor and taking picture & set log. Thanks to squadzone for let me know this fuction should removed
  2. defconfig: removing xz & make lzma for compressed kernel

    phiexz committed Jun 5, 2012
    AFAIK, i dissapoint with xz, some of my experiment make kernel cant booting with xz
    compression. but it can boot with gzip & lzma.
  3. Revert "decompressors: add XZ decompressor module"

    phiexz committed Jun 5, 2012
    This reverts commit f9cbe1b.
  4. Revert "decompressors: add boot-time XZ support"

    phiexz committed Jun 5, 2012
    This reverts commit 61c0da0.
  5. Revert "Squashfs: add XZ compression support"

    phiexz committed Jun 5, 2012
    This reverts commit cee48d7.
  6. Revert "Squashfs: Add XZ compression configuration option"

    phiexz committed Jun 5, 2012
    This reverts commit 2d144eb.
  7. Revert "ARM: support XZ compressed kernels"

    phiexz committed Jun 5, 2012
    This reverts commit b1123e0.
Commits on May 14, 2012
  1. msm: camera: multiframe HJR fix for snapshot redesign

    Sunid Wilson authored and phiexz committed Feb 23, 2011
    Updated the post processing code to handle multiframe HJR
    which is aligned with new snapshot design
    
    Change-Id: I939b5339f731beefa7f42dcd2c6509d689087b9c
    Signed-off-by: Sunid Wilson <sunid@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  2. msm: smd_pkt: silence debug messages in kernel log

    Jeff Hugo authored and phiexz committed Feb 23, 2011
    Change-Id: Id07a872181a140405fd7f9c90fb015a9ee216c12
    CRs-Fixed: 275973
    Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  3. diag: Bump up buffer size

    Shalabh Jain authored and phiexz committed Feb 23, 2011
    DIAG char driver uses buffers to forward traffic from SMD/SDIO
    channels. Bumping up the buffer size to accommodate largers packets.
    
    Change-Id: I5331e5666bc5e38b236616c6c5108705fa25d144
    Signed-off-by: Shalabh Jain <shalabhj@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  4. msm_fb: display: Fix MDDI CRC Error handling condition

    Ravishangar Kalyanam authored and phiexz committed Feb 14, 2011
    Fix MDDI CRC Error handling condition to avoid looping of MDDI reads
    infinitely
    
    Change-Id: I4e65b635fc4041213e544f64919a9a6f074b366e
    CRs-Fixed: 275229
    Signed-off-by: Ravishangar Kalyanam <rkalya@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  5. Bluetooth: Move stream receive functions to a shared location.

    Mat Martineau authored and phiexz committed Mar 1, 2011
    This allows streaming mode receive code to be shared between
    RFCOMM and L2CAP ERTM.  Includes handling of non-linear
    socket buffers.
    
    Change-Id: If3c20f79c0a0ca1f7cff1ffd75de94cfdcb8e252
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  6. Bluetooth: Handle non-linear skbs produced by L2CAP.

    Mat Martineau authored and phiexz committed Mar 1, 2011
    Upcoming ERTM changes introduce the possiblity of non-linear
    socket buffers being passed to L2CAP users within the kernel.
    Check for and force these socket buffers to be linearized.
    There should not be performance issues, since these Bluetooth
    profiles do not use ERTM in practice. Without this change,
    non-linear buffers could cause stability problems.
    
    Change-Id: Ibb473de4d248c7ad85f9e7b8ff59a84a686449e7
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  7. Bluetooth: fix oops in l2cap_connect_req

    nholstein authored and phiexz committed Oct 15, 2010
    In error cases when the ACL is insecure or we fail to allocate a new
    struct sock, we jump to the "response" label.  If so, "sk" will be
    null and the kernel crashes.
    
    Signed-off-by: Nathan Holstein <nathan.holstein@gmail.com>
    Acked-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    (cherry picked from commit d793fe8caa3911e6a1e826b45d4ee00d250cdec8)
    
    Change-Id: I2e6066b6c80b15cae704cfa65a9c9b65b569341b
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  8. Bluetooth: Update conf_state before send config_req out

    haijun authored and phiexz committed Sep 30, 2010
    Update conf_state with L2CAP_CONF_REQ_SENT before send config_req out in
    l2cap_config_req().
    
    Signed-off-by: Haijun Liu <haijun.liu@atheros.com>
    Acked-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    (cherry picked from commit ab3e571564a5d8fa4923e2e858e574c931a014c7)
    
    Change-Id: Ice77b7f1ddaf572635efb1a2de6873843947ab1d
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  9. Bluetooth: Disallow to change L2CAP_OPTIONS values when connected

    Gustavo F. Padovan authored and phiexz committed Oct 4, 2010
    L2CAP doesn't permit change like MTU, FCS, TxWindow values while the
    connection is alive, we can only set that before the
    connection/configuration process. That can lead to bugs in the L2CAP
    operation.
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    (cherry picked from commit eaa71b318c5ed0cd1ac3182a533471dc5edf372d)
    
    Change-Id: I8ccf4ed842a01d9dfb7c7e8484e5862e0d131564
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  10. Bluetooth: Fix deadlock in the ERTM logic

    Gustavo F. Padovan authored and phiexz committed Sep 21, 2010
    The Enhanced Retransmission Mode(ERTM) is a realiable mode of operation
    of the Bluetooth L2CAP layer. Think on it like a simplified version of
    TCP.
    The problem we were facing here was a deadlock. ERTM uses a backlog
    queue to queue incomimg packets while the user is helding the lock. At
    some moment the sk_sndbuf can be exceeded and we can't alloc new skbs
    then the code sleep with the lock to wait for memory, that stalls the
    ERTM connection once we can't read the acknowledgements packets in the
    backlog queue to free memory and make the allocation of outcoming skb
    successful.
    
    This patch actually affect all users of bt_skb_send_alloc(), i.e., all
    L2CAP modes and SCO.
    
    We are safe against socket states changes or channels deletion while the
    we are sleeping wait memory. Checking for the sk->sk_err and
    sk->sk_shutdown make the code safe, since any action that can leave the
    socket or the channel in a not usable state set one of the struct
    members at least. Then we can check both of them when getting the lock
    again and return with the proper error if something unexpected happens.
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    Signed-off-by: Ulisses Furquim <ulisses@profusion.mobi>
    (cherry picked from commit e454c844644683571617896ab2a4ce0109c1943e)
    
    Change-Id: I9eb586afed7cd5d9349e069e592f04da78a330dc
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  11. Bluetooth: Fix inconsistent lock state with RFCOMM

    Gustavo F. Padovan authored and phiexz committed Aug 14, 2010
    When receiving a rfcomm connection with the old dund deamon a
    inconsistent lock state happens. That's because interrupts were already
    disabled by l2cap_conn_start() when rfcomm_sk_state_change() try to lock
    the spin_lock.
    
    As result we may have a inconsistent lock state for l2cap_conn_start()
    after rfcomm_sk_state_change() calls bh_lock_sock() and disable interrupts
    as well.
    
    [ 2833.151999]
    [ 2833.151999] =================================
    [ 2833.151999] [ INFO: inconsistent lock state ]
    [ 2833.151999] 2.6.36-rc3 #2
    [ 2833.151999] ---------------------------------
    [ 2833.151999] inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage.
    [ 2833.151999] krfcommd/2306 [HC0[0]:SC0[0]:HE1:SE1] takes:
    [ 2833.151999]  (slock-AF_BLUETOOTH){+.?...}, at: [<ffffffffa00bcb56>] rfcomm_sk_state_change+0x46/0x170 [rfcomm]
    [ 2833.151999] {IN-SOFTIRQ-W} state was registered at:
    [ 2833.151999]   [<ffffffff81094346>] __lock_acquire+0x5b6/0x1560
    [ 2833.151999]   [<ffffffff8109534a>] lock_acquire+0x5a/0x70
    [ 2833.151999]   [<ffffffff81392b6c>] _raw_spin_lock+0x2c/0x40
    [ 2833.151999]   [<ffffffffa00a5092>] l2cap_conn_start+0x92/0x640 [l2cap]
    [ 2833.151999]   [<ffffffffa00a6a3f>] l2cap_sig_channel+0x6bf/0x1320 [l2cap]
    [ 2833.151999]   [<ffffffffa00a9173>] l2cap_recv_frame+0x133/0x770 [l2cap]
    [ 2833.151999]   [<ffffffffa00a997b>] l2cap_recv_acldata+0x1cb/0x390 [l2cap]
    [ 2833.151999]   [<ffffffffa000db4b>] hci_rx_task+0x2ab/0x450 [bluetooth]
    [ 2833.151999]   [<ffffffff8106b22b>] tasklet_action+0xcb/0xe0
    [ 2833.151999]   [<ffffffff8106b91e>] __do_softirq+0xae/0x150
    [ 2833.151999]   [<ffffffff8102bc0c>] call_softirq+0x1c/0x30
    [ 2833.151999]   [<ffffffff8102ddb5>] do_softirq+0x75/0xb0
    [ 2833.151999]   [<ffffffff8106b56d>] irq_exit+0x8d/0xa0
    [ 2833.151999]   [<ffffffff8104484b>] smp_apic_timer_interrupt+0x6b/0xa0
    [ 2833.151999]   [<ffffffff8102b6d3>] apic_timer_interrupt+0x13/0x20
    [ 2833.151999]   [<ffffffff81029dfa>] cpu_idle+0x5a/0xb0
    [ 2833.151999]   [<ffffffff81381ded>] rest_init+0xad/0xc0
    [ 2833.151999]   [<ffffffff817ebc4d>] start_kernel+0x2dd/0x2e8
    [ 2833.151999]   [<ffffffff817eb2e6>] x86_64_start_reservations+0xf6/0xfa
    [ 2833.151999]   [<ffffffff817eb3ce>] x86_64_start_kernel+0xe4/0xeb
    [ 2833.151999] irq event stamp: 731
    [ 2833.151999] hardirqs last  enabled at (731): [<ffffffff8106b762>] local_bh_enable_ip+0x82/0xe0
    [ 2833.151999] hardirqs last disabled at (729): [<ffffffff8106b93e>] __do_softirq+0xce/0x150
    [ 2833.151999] softirqs last  enabled at (730): [<ffffffff8106b96e>] __do_softirq+0xfe/0x150
    [ 2833.151999] softirqs last disabled at (711): [<ffffffff8102bc0c>] call_softirq+0x1c/0x30
    [ 2833.151999]
    [ 2833.151999] other info that might help us debug this:
    [ 2833.151999] 2 locks held by krfcommd/2306:
    [ 2833.151999]  #0:  (rfcomm_mutex){+.+.+.}, at: [<ffffffffa00bb744>] rfcomm_run+0x174/0xb20 [rfcomm]
    [ 2833.151999]  #1:  (&(&d->lock)->rlock){+.+...}, at: [<ffffffffa00b9223>] rfcomm_dlc_accept+0x53/0x100 [rfcomm]
    [ 2833.151999]
    [ 2833.151999] stack backtrace:
    [ 2833.151999] Pid: 2306, comm: krfcommd Tainted: G        W   2.6.36-rc3 #2
    [ 2833.151999] Call Trace:
    [ 2833.151999]  [<ffffffff810928e1>] print_usage_bug+0x171/0x180
    [ 2833.151999]  [<ffffffff810936c3>] mark_lock+0x333/0x400
    [ 2833.151999]  [<ffffffff810943ca>] __lock_acquire+0x63a/0x1560
    [ 2833.151999]  [<ffffffff810948b5>] ? __lock_acquire+0xb25/0x1560
    [ 2833.151999]  [<ffffffff8109534a>] lock_acquire+0x5a/0x70
    [ 2833.151999]  [<ffffffffa00bcb56>] ? rfcomm_sk_state_change+0x46/0x170 [rfcomm]
    [ 2833.151999]  [<ffffffff81392b6c>] _raw_spin_lock+0x2c/0x40
    [ 2833.151999]  [<ffffffffa00bcb56>] ? rfcomm_sk_state_change+0x46/0x170 [rfcomm]
    [ 2833.151999]  [<ffffffffa00bcb56>] rfcomm_sk_state_change+0x46/0x170 [rfcomm]
    [ 2833.151999]  [<ffffffffa00b9239>] rfcomm_dlc_accept+0x69/0x100 [rfcomm]
    [ 2833.151999]  [<ffffffffa00b9a49>] rfcomm_check_accept+0x59/0xd0 [rfcomm]
    [ 2833.151999]  [<ffffffffa00bacab>] rfcomm_recv_frame+0x9fb/0x1320 [rfcomm]
    [ 2833.151999]  [<ffffffff813932bb>] ? _raw_spin_unlock_irqrestore+0x3b/0x60
    [ 2833.151999]  [<ffffffff81093acd>] ? trace_hardirqs_on_caller+0x13d/0x180
    [ 2833.151999]  [<ffffffff81093b1d>] ? trace_hardirqs_on+0xd/0x10
    [ 2833.151999]  [<ffffffffa00bb7f1>] rfcomm_run+0x221/0xb20 [rfcomm]
    [ 2833.151999]  [<ffffffff813905e7>] ? schedule+0x287/0x780
    [ 2833.151999]  [<ffffffffa00bb5d0>] ? rfcomm_run+0x0/0xb20 [rfcomm]
    [ 2833.151999]  [<ffffffff81081026>] kthread+0x96/0xa0
    [ 2833.151999]  [<ffffffff8102bb14>] kernel_thread_helper+0x4/0x10
    [ 2833.151999]  [<ffffffff813936bc>] ? restore_args+0x0/0x30
    [ 2833.151999]  [<ffffffff81080f90>] ? kthread+0x0/0xa0
    [ 2833.151999]  [<ffffffff8102bb10>] ? kernel_thread_helper+0x0/0x10
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    (cherry picked from commit fad003b6c8e3d944d4453fd569b0702ef1af82b3)
    
    Change-Id: I7e0d235cf86209e6f36b413705bc1bb3495a6cee
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  12. Bluetooth: Simplify L2CAP Streaming mode sending

    Gustavo F. Padovan authored and phiexz committed Aug 30, 2010
    As we don't have any error control on the Streaming mode, i.e., we don't
    need to keep a copy of the skb for later resending we don't need to
    call skb_clone() on it.
    Then we can go one further here, and dequeue the skb before sending it,
    that also means we don't need to look to sk->sk_send_head anymore.
    
    The patch saves memory and time when sending Streaming mode data, so
    it is good to mainline.
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    (cherry picked from commit ccbb84af28594e19fd4bf27ff2828c80d03b6081)
    
    Change-Id: If4644a561b812b6d37a0a1925bf192a96f8620be
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  13. Bluetooth: fix MTU L2CAP configuration parameter

    Andrei Emeltchenko authored and phiexz committed Sep 1, 2010
    When receiving L2CAP negative configuration response with respect
    to MTU parameter we modify wrong field. MTU here means proposed
    value of MTU that the remote device intends to transmit. So for local
    L2CAP socket it is pi->imtu.
    
    Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@nokia.com>
    Acked-by: Ville Tervo <ville.tervo@nokia.com>
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    (cherry picked from commit 8183b775bc5b79b6b1e250019c9dd930554dfa94)
    
    Change-Id: I6977d681f1800fa24c8ec8c3e652379a4fd9bff1
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  14. Bluetooth: Only enable L2CAP FCS for ERTM or streaming

    Mat Martineau authored and phiexz committed Aug 24, 2010
    This fixes a bug which caused the FCS setting to show L2CAP_FCS_CRC16
    with L2CAP modes other than ERTM or streaming.  At present, this only
    affects the FCS value shown with getsockopt() for basic mode.
    
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    (cherry picked from commit 8c462b6047da80491b8cb6be878e8bf9313ac3e1)
    
    Change-Id: I9ed53b9d9a8ce287e0b3e2725469be99ea756600
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  15. Bluetooth: Use 3-DH5 payload size for default ERTM max PDU size

    Mat Martineau authored and phiexz committed Aug 5, 2010
    The previous value of 672 for L2CAP_DEFAULT_MAX_PDU_SIZE is based on
    the default L2CAP MTU.  That default MTU is calculated from the size
    of two DH5 packets, minus ACL and L2CAP b-frame header overhead.
    
    ERTM is used with newer basebands that typically support larger 3-DH5
    packets, and i-frames and s-frames have more header overhead.  With
    clean RF conditions, basebands will typically attempt to use 1021-byte
    3-DH5 packets for maximum throughput.  Adjusting for 2 bytes of ACL
    headers plus 10 bytes of worst-case L2CAP headers yields 1009 bytes
    of payload.
    
    This PDU size imposes less overhead for header bytes and gives the
    baseband the option to choose 3-DH5 packets, but is small enough for
    ERTM traffic to interleave well with other L2CAP or SCO data.
    672-byte payloads do not allow the most efficient over-the-air
    packet choice, and cannot achieve maximum throughput over BR/EDR.
    
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit db12d647ccc971ed120199dc7ea5be2b5887d328)
    
    Change-Id: I701860b54968718fe7ace32ef740799afb5b9606
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  16. Bluetooth: Fix incorrect setting of remote_tx_win for L2CAP ERTM

    Mat Martineau authored and phiexz committed Aug 5, 2010
    remote_tx_win is intended to be set on receipt of an L2CAP
    configuration request.  The value is used to determine the size of the
    transmit window on the remote side of an ERTM connection, so L2CAP
    can stop sending frames when that remote window is full.
    
    An incorrect remote_tx_win value will cause the stack to not fully
    utilize the tx window (performance impact), or to overfill the remote
    tx window (causing dropped frames or a disconnect).
    
    This patch removes an extra setting of remote_tx_win when a
    configuration response is received.  The transmit window has a
    different meaning in a response - it is an informational value
    less than or equal to the local tx_win.
    
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit cff70fae111efba80c27023772ce5265797fb514)
    
    Change-Id: I98c43555638b7f286123091e685b5dc7a4fe0c6d
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  17. Bluetooth: Change default L2CAP ERTM retransmit timeout

    Mat Martineau authored and phiexz committed Aug 5, 2010
    The L2CAP specification requires that the ERTM retransmit timeout be at
    least 2 seconds for BR/EDR connections.
    
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit fa235562fbde8703aabeeedfa0772f08608d1542)
    
    Change-Id: I775d3773113d6cbbcdc428795a6ab26be83d2bc9
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  18. Bluetooth: Fix endianness issue with L2CAP MPS configuration

    Mat Martineau authored and phiexz committed Aug 5, 2010
    Incoming configuration values must be converted to native CPU order
    before use.  This fixes a bug where a little-endian MPS value is
    compared to a native CPU value.  On big-endian processors, this
    can cause ERTM and streaming mode segmentation to produce PDUs
    that are larger than the remote stack is expecting, or that would
    produce fragmented skbs that the current FCS code cannot handle.
    
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit 86b1b26326279299c93ddb11ab4782d3896bf84c)
    
    Change-Id: I848b91c1fec47e89ab9bf07efab462605cca3c4c
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  19. Bluetooth: Check result code of L2CAP information response

    Ville Tervo authored and phiexz committed Aug 4, 2010
    Check result code of L2CAP information response. Otherwise
    it would read invalid feature mask and access invalid memory.
    
    Signed-off-by: Ville Tervo <ville.tervo@nokia.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit adb08edea0119f7a5484a9f6a385fbcecdf85a63)
    
    Change-Id: I20f0480804db7a3b5bfa0390fdd747e545a68b8e
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  20. Bluetooth: Don't send RFC for Basic Mode if only it is supported

    Gustavo F. Padovan authored and phiexz committed Aug 4, 2010
    If the remote side doesn't support Enhanced Retransmission Mode neither
    Streaming Mode, we shall not send the RFC option.
    
    Some devices that only supports Basic Mode do not understanding the RFC
    option. This patch fixes the regression found with these devices.
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit 6340650400525a9ca8d86b1b4501cc50670dce0d)
    
    Change-Id: I587eeedb06c40ff5457bb17939f2a0f5441c57c3
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  21. Bluetooth: Remove __exit from rfcomm_cleanup_ttys()

    Gustavo F. Padovan authored and phiexz committed Jul 31, 2010
    rfcomm_cleanup_ttys() is also called from rfcomm_init(), so it can't
    have __exit.
    
    Reported-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit 28e9509b1270e5cfa8bb3c5ff51f39214aa09262)
    
    Change-Id: If3834451fbb13fb1145dbd0bcb760e86b988a59b
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  22. Bluetooth: Use list_head for HCI blacklist head

    davem330 authored and phiexz committed Jul 31, 2010
    The bdaddr in the list root is completely unused and just
    taking up space.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Tested-by: Johan Hedberg <johan.hedberg@nokia.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit ea4bd8ba804dedefa65303b3bd105d6d2808e621)
    
    Change-Id: I5cdc4b7924c5704d2402495c4be7a025ad4eda7d
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  23. Bluetooth: Fix kfree() => kfree_skb() in hci_ath.c

    error27 authored and phiexz committed Jul 23, 2010
    sk_buffs have to be freed with kfree_skb() instead of kfree().
    
    Signed-off-by: Dan Carpenter <error27@gmail.com>
    Acked-by: Gustavo F. Padovan <padovan@profusion.mobi>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit 4ebaa4edf8799cab19d5a0642dc95f04fd284e06)
    
    Change-Id: I6544d7bc3b5683dab6455f399bcfeb2108f47010
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  24. Bluetooth: Add __init and __exit marks to RFCOMM

    Gustavo F. Padovan authored and phiexz committed Jul 24, 2010
    Those annotation save memory and space on the binary. __init code is
    discarded just after execute and __exit code is discarded if the module
    is built into the kernel image or unload of modules is not allowed.
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit 2f8362afcd2da8b313ec3cc04a50af19d3592972)
    
    Change-Id: I625614bfecd605c9afb809219474fc121fc9c213
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  25. Bluetooth: Add __init and __exit marks to UART drivers

    Gustavo F. Padovan authored and phiexz committed Jul 24, 2010
    Those marks are useful to save space in the binary and in the memory.
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit f2b94bb9e0b8bd048331a6e9d616e918f4bcbd97)
    
    Change-Id: Idb32a32682fb61bf731a97f94286f609943d1cdf
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  26. Bluetooth: Use hci_recv_stream_fragment() in UART driver

    Gustavo F. Padovan authored and phiexz committed Jul 24, 2010
    Use the new hci_recv_stream_fragment() to reassembly incoming UART
    streams.
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    Tested-by: Ville Tervo <ville.tervo@nokia.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit e9da101f6d0c9a8fda9f78a80365ba2a9f75603f)
    
    Change-Id: I3dce6b60ed93205f6db93a5a70f2d59b4b545063
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  27. Bluetooth: Test 'count' value before enter the loop

    Gustavo F. Padovan authored and phiexz committed Jul 24, 2010
    Testing first we avoid enter the loop when count = 0.
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit da5f6c37eee040775997191d1a1bc91c0c1e51eb)
    
    Change-Id: Ie8a2746e9a993cddb7747e35105006bdd5ea6bb8
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>
  28. Bluetooth: Fix permission of hci_ath.c

    Gustavo F. Padovan authored and phiexz committed Jul 24, 2010
    .c file shall not have the 'x' permission.
    
    Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    (cherry picked from commit 0bbdf6cba0fb730ae2f2cfd5ead3d1e2e5498ddc)
    
    Change-Id: Ic127032b1f625146e3fbef3a9fde796349d00562
    Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
    Signed-off-by: Andika Edo <dhiika@phiexz.com>