GitHub PushEvent at 2014-05-17 04:19:39
Repository: DNA_kitkat
Actor: torrented
Payload: {"shas":[["46a0a7a2afa2ae9a3082b9fc1d1a2717eb1b46c7","90b51f8a5079017e81711ae9317c35b0575b34e1@gmail.com","cpufreq: add ability to lock the /sys controls\n\nSigned-off-by: torrented <wallace.ryan10@gmail.com>\n\nConflicts:\n\tdrivers/cpufreq/cpufreq.c","Christopher R. Palmer",true],["c8989aa0eb9539666eb262dcc6bee50521ec4dcb","e8574b55140123c7e38a57b02ddff8b1dd3b7513@gmail.com","Update Files\n\nSigned-off-by: torrented <wallace.ryan10@gmail.com>","torrented",true],["04fd0f61c279d16b418991138bf06f4c2e08a3c1","e8574b55140123c7e38a57b02ddff8b1dd3b7513@gmail.com","Revert \"Update Files\"\n\nThis reverts commit e611240d2e026391be5bd82f71fd818b86a86bf9.","torrented",true],["908f82e354f0a709d92d83d0d2214b94bfabbb13","e8574b55140123c7e38a57b02ddff8b1dd3b7513@gmail.com","Fix Files\n\nSigned-off-by: torrented <wallace.ryan10@gmail.com>","torrented",true],["e91b3df26f6a1a72f2e84a18f3e3addb9cfed47f","e8574b55140123c7e38a57b02ddff8b1dd3b7513@gmail.com","Added cmdline for locking the CPU Freq after cmdline sets scaling_min/max_freqs so init.post_boot.sh doesn't reset our values\n\nSigned-off-by: torrented <wallace.ryan10@gmail.com>","torrented",true],["e76d6877d82d38053cbdd61ec74d6c7627bf42ae","15d7a7f70c58bf708052629c6bf93d96a446d604@gmail.com","Merge pull request #1 from torrented/ihate\n\nSet Default MIN/MAX if not set by CMDLINE","iHateWEBos",true],["0ac5d48de3a62a78f3848c3ff926295f81cbe0da","3fb360b964bf23e8080fd2972e2df37c8762ce5a@gmail.com","Squashed: Slimbus super fun pack.\nsquashed the following commits from poondog:\n\nDRIVERS: SLIMBUS: slimbus enhancements mkII\n\n    This time we keep the root freq to 11.\n    If Root Freq is set at 11, 24,576MHz has the best compatibility for all present sampling\nrates (e.g, any sample rate can be converted, 48KHz to 96KHz, 44.1KHz to 96KHz, 48KHz to\n128KHz etc.) Increasing the root frequency is likely to cause invalid present sample rate\ncombinations which leads to audio glitches such as distortion. \"A Natural Frequency is\ndefined as a CLK frequency that allows a family of data rates to be supported. The different\nsample rate flows can be optimally supported by changing a particular Natural Frequency\nusing the Clock Gear.\" I looked at a Clock Gear/RF table and it looks like CLK Gear 10 and\nRF 24,576MHz (Stock RF) is an excellent combination due to its compatibility towards every\nother sample rates.\n\n    ZeroInfinity/Poondog\n\n    Signed-off-by: ZeroInfinity <infinitezero345@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 60abd0f\nAuthor: Kiran Gunda <kgunda@codeaurora.org>\nDate:   Mon Mar 17 16:11:40 2014 +0530\n\n    Slim_ngd: Modify waiting mechanism in kthread\n\n    wait_for_completion_timeout() is not a good option in\n    kthread as it leads to scheduling the kthread on the every timeout.\n    Hence modify it to wait_for_completion() from\n    wait_for_completion_timeout().\n\n    Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>\n    Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 8c7210e\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Fri Feb 7 19:40:12 2014 -0700\n\n    slimbus: Use physical address type where physical address is used\n\n    Use physical address type for buffers using physical address.\n    (e.g. interaction with data-mover engine)\n\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n    Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit e59f466\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Mon Jan 27 20:55:59 2014 -0700\n\n    slimbus: Enable clients to send user messages to devices.\n\n    Slimbus protocol allows user messages of destination referred, or\n    source referred type to be sent to a slimbus device.\n    Provide framework to support such messages. Note that, controller\n    may not support all user messages.\n\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n    Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit b215fa8\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Mon Feb 3 12:17:04 2014 -0700\n\n    slim_ngd: Handle error flags before handling SENT flag\n\n    It's possible that error flags were set alongwith SENT flag for\n    TX transaction status. In such a scenario, error flag status should\n    be handled (and SENT flag should be cleared). Move error-flag\n    handling ahead of SENT flag handling to avoid interrupt being called\n    twice, and completion being set twice.\n\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n    Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>\n    Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 7c96575\nAuthor: Kiran Gunda <kgunda@codeaurora.org>\nDate:   Tue Oct 8 16:32:13 2013 +0530\n\n    Slimbus: Correct the conditional check during channel removal\n\n    Use actual channel number to check if the channel to be\n    removed is present in the define_chan list before removing\n    it, instead of using the internal channel number used by\n    the frame work.\n\n    Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>\n    Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 6fe1b5e\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Fri Jun 21 12:18:20 2013 -0600\n\n    slim_msm: Get platform-specific information from platform-data\n\n    Number of pipes available to application processor for data channels,\n    and product-code field of enumeration address needed for setting\n    these pipes can be different for different platforms.\n    Store this platform-specific information in platform-data, and get\n    it from Device-Tree if applicable.\n\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n    Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 57d703f\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Wed May 15 20:18:01 2013 -0600\n\n    slim_msm: Signal client's completion for per transfer notification\n\n    Slimbus ports are connected to BAM pipes and ports inform the pipe\n    when descriptor's data transfer is done. Clients queue a completion\n    per descrptor when that descriptor is processed. This completion will\n    get overwritten if client queues multiple descriptors. Use\n    per-transfer user-data as client's completion to avoid this problem.\n    This also reduces controller-driver involvement in data transfer.\n\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n    Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit c5dcdd6\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Wed May 15 20:01:45 2013 -0600\n\n    slim_msm: Report flow-error and mask apps slimbus port interrupts\n\n    Apps side slimbus ports may overflow/underflow if BAM pipes connected\n    to those ports don't have descriptors scheduled.\n    Report such errors and mask the port interrupts until BAM pipes have\n    descriptors scheduled to avoid interrupts firing multiple times.\n\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n    Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 5e0ef9e\nAuthor: Kiran Gunda <kgunda@codeaurora.org>\nDate:   Mon Oct 21 17:00:15 2013 +0530\n\n    slim_ngd: Add NULL pointer check apart from error check\n\n    Check against NULL pointer after allocating\n    the memory for msm_slim_ctrl structure pointer\n    dynamically to avoid unexpected crashes.\n\n    Earlier this pointer is checked only for error\n    codes. In this patch NULL pointer check is also\n    added.\n\n    Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>\n    Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 807c7164ceb461e21a46161f8706d81006fd2aa5\nAuthor: Kiran Gunda <kgunda@codeaurora.org>\nDate:   Tue Feb 4 07:45:03 2014 +0530\n\n    slim-ngd: NULL pointer check for client buffer\n\n    There is the chance of passing NULL pointer by the client\n    during the Slimbus/Codec transactions. Hence add NULL\n    pointer check for client buffer aswell.\n\n    CRs-Fixed: 608324\n    Change-Id: I161e8f04401afebb64ed72d5f392a67feb6ec13a\n    Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>\n    Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 85b21f63bfabb77732dc972e4132b6a9569ec9de\nAuthor: Ajay Dudani <adudani@codeaurora.org>\nDate:   Wed Aug 14 23:32:30 2013 -0700\n\n    slim_ngd: Make sure transaction is not dereferenced after it's freed\n\n    Every read transaction over slimbus is a set of one transmit and one\n    receive. Receive part frees meta-data for the read transaction since\n    it is no longer needed, and the transaction-ID can be reused.\n    Make sure that the transmit function doesn't try to dereference the\n    transaction meta-data after possibly receiving a response.\n\n    CRs-fixed: 515802\n    Change-Id: Id736ad368d4944a6aabc89f4ff295d664bc5efa0\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n    Signed-off-by: Ajay Dudani <adudani@codeaurora.org>\n\ncommit 5cf37798e4eef79f09f11325a1d9fadd20651333\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Fri Apr 26 18:05:37 2013 -0600\n\n    slim_ngd: Support reserving message bandwidth for clients\n\n    Message bandwidth can be reserved by clients to do message-intensive\n    transactions over Slimbus. While slimbus framework supports that,\n    NGD driver was missing corresponding code to send this request to\n    master driver on ADSP. This patch adds that support.\n\n    Change-Id: If6a340746816658ac0aa1b4bd7c2270205eb6d4a\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 10c76ce03102e4ae76d090e4f3c7096d6b84a845\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Fri Feb 22 19:06:39 2013 -0700\n\n    slimbus: Handle channel control correctly if controller manages BW\n\n    If bandwidth allocation is managed by controller (and not framework),\n    channel control commands from all clients should be sent to the\n    controller.\n\n    Change-Id: Ibdd27c35a48818efdd55a0a84c52fbb9671cdb77\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 6d6927666e8d92156543053293a508f815c1565f\nAuthor: Kiran Gunda <kgunda@codeaurora.org>\nDate:   Thu Jan 10 17:03:33 2013 +0530\n\n    slim_msm: Reading the smaller length messages properly\n\n    If the smaller length messages(<= 4 Bytes) like REPORT_ABSENT\n    are received over slimbus, the master driver is reading the\n    excessive length than required. Due to that the next messages\n    over slimbus are getting corrupted. This patch fixes this issue\n    and also handles the REPORT_ABSENT message sent by the third party\n    slimbus client devices.\n\n    CRs-Fixed: 431529\n    Change-Id: I7b3c07a94603482a6a9a7645ade70228144703bc\n    Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>\n\ncommit aa9c94d15b8d40c54e8a45f48e05495fe91b4cc2\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Jan 22 17:51:41 2013 -0700\n\n    slimbus: Add slimbus device driver unregistration function\n\n    slim_driver_unregister is added to reverse effects of\n    slim_driver_register. That way a slimbus device driver can be\n    registered when driver module is loaded, and unregistered when\n    the driver module is unloaded.\n\n    CRs-Fixed: 441540\n    Change-Id: Iae64f84c99d5027c9b55c3fde5fe71c6a550354e\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\n    Conflicts:\n    \tinclude/linux/slimbus/slimbus.h\n\ncommit aedb21330278ef8a5a2050b211a6ea2ec9703033\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Sat Dec 1 15:43:01 2012 -0700\n\n    slimbus: Refine scope of controller and scheduler mutex locks\n\n    Controller mutex scope is restricted to controller specific data\n    structures, such as addressing table, transaction table.\n    Scheduler lock is used to protect scheduling data structures (such\n    as channels, and bandwidth).\n    This way, controller mutex is not needed when expensive\n    reconfiguration sequence(used for channel scheduling, bandwidth\n    management) is in progress. Transactions over messaging channel (such\n    as element read/writes, logical address assignment) can happen in\n    parallel and don't have to block on reconfiguration sequence which\n    only affects data channels.\n\n    CRs-Fixed: 426945\n    Change-Id: I2ca20aa76901ee19dba62874c86c2108fac9fa02\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit dd94f94fd8d6d28c8b43435ad923b608c811678c\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Oct 30 13:44:08 2012 -0600\n\n    slim_ngd: Rectify define, removal messages per protocol\n\n    Populate required bits only as client handle while sending\n    channel define, removal messages to the master driver.\n    Previously, complete logical address was set as client handle\n    which would corrupt other fields in that byte if logical\n    address had non-zero MSBs. This patch fixes that problem.\n\n    Change-Id: I96e8a7917c1fe68e1c86f6837c0b9f8ee187ca3d\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 96e8b46485257231829079bed73ebe42487cbab9\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Oct 30 21:12:09 2012 -0600\n\n    slimbus: Populate slimbus device's logical address during assignment\n\n    Slimbus device is assigned logical address when it reports present.\n    Make sure to populate the device's logical address (laddr) during\n    this assignment.\n\n    CRs-Fixed: 412148\n    Change-Id: Icb8d74f6ea71aff8f6cb30523002f7839e2cb028\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit c66927d43475e8913c77dbc02c8eabd1cc146c0b\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Wed Oct 17 22:41:57 2012 -0600\n\n    slimbus: Specify number of channels for the group in group handle\n\n    Use group handle instead of next element in channel's data structure\n    to identify how many channels were specified by a client in the group.\n    That way clients can specify different number of channels for shared\n    channels, and work with their own client-handle. Note that sequence of\n    channel still matters (so 2 clients sharing a channel should not\n    specify channels in different order, otherwise scheduling of the\n    channels will not be in the correct order)\n\n    CRs-Fixed: 415109\n    Change-Id: Idd636a500ee6449b16648a234b9e76fad21f2fcc\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit f259ddaaf2957e127182fa25fce6b1f308d5beb3\nAuthor: Stephen Boyd <sboyd@codeaurora.org>\nDate:   Wed Oct 31 17:41:43 2012 -0700\n\n    slim_msm: Fix unsafe locking in msm_sat_enqueue()\n\n    msm_sat_enqueue() calls spin_lock() and msm_sat_dequeue() calls\n    spin_lock_irqsave(). This leads to lockdep warnings about the\n    same lock being taken in interrupts on and interrupts off context\n    which can lead to a potential deadlock.\n\n    =================================\n    [ INFO: inconsistent lock state ]\n    3.4.0+ #382 Tainted: G        W\n    ---------------------------------\n    inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.\n    kworker/u:2/94 [HC1[1]:SC0[0]:HE0:SE1] takes:\n     (&(&sat->lock)->rlock){?.+...}, at: [<c0348b80>] msm_sat_enqueue+0x20/0xb0\n    {HARDIRQ-ON-W} state was registered at:\n      [<c00bd290>] __lock_acquire+0x664/0x8d8\n      [<c00bd690>] lock_acquire+0x18c/0x1e8\n      [<c06989a4>] _raw_spin_lock+0x38/0x48\n      [<c0348b80>] msm_sat_enqueue+0x20/0xb0\n      [<c0349338>] msm_slim_rxwq+0x278/0x42c\n      [<c0349580>] msm_slim_rx_msgq_thread+0x94/0x1f8\n      [<c008e480>] kthread+0x90/0xa0\n      [<c000f438>] kernel_thread_exit+0x0/0x8\n    irq event stamp: 24219\n    hardirqs last  enabled at (24218): [<c0699188>] _raw_spin_unlock_irqrestore+0x3c/0x68\n    hardirqs last disabled at (24219): [<c06993f4>] __irq_svc+0x34/0x78\n    softirqs last  enabled at (24129): [<c00738a8>] irq_exit+0x54/0xa8\n    softirqs last disabled at (24108): [<c00738a8>] irq_exit+0x54/0xa8\n\n    other info that might help us debug this:\n     Possible unsafe locking scenario:\n\n           CPU0\n           ----\n      lock(&(&sat->lock)->rlock);\n      <Interrupt>\n        lock(&(&sat->lock)->rlock);\n\n     *** DEADLOCK ***\n\n    3 locks held by kworker/u:2/94:\n     #0:  ((sat->satcl.name)){.+.+.+}, at: [<c0087124>] process_one_work+0x1e8/0x648\n     #1:  ((&sat->wd)){+.+.+.}, at: [<c0087124>] process_one_work+0x1e8/0x648\n     #2:  (&dev->tx_lock){+.+...}, at: [<c0349cac>] msm_xfer_msg+0xb4/0x51c\n\n    stack backtrace:\n    [<c00151b0>] (unwind_backtrace+0x0/0x120) from [<c00b9d48>]\n(print_usage_bug+0x258/0x2c0)\n    [<c00b9d48>] (print_usage_bug+0x258/0x2c0) from [<c00ba12c>] (mark_lock+0x37c/0x68c)\n    [<c00ba12c>] (mark_lock+0x37c/0x68c) from [<c00bd20c>] (__lock_acquire+0x5e0/0x8d8)\n    [<c00bd20c>] (__lock_acquire+0x5e0/0x8d8) from [<c00bd690>] (lock_acquire+0x18c/0x1e8)\n    [<c00bd690>] (lock_acquire+0x18c/0x1e8) from [<c06989a4>] (_raw_spin_lock+0x38/0x48)\n    [<c06989a4>] (_raw_spin_lock+0x38/0x48) from [<c0348b80>] (msm_sat_enqueue+0x20/0xb0)\n    [<c0348b80>] (msm_sat_enqueue+0x20/0xb0) from [<c0348dc8>]\n(msm_slim_interrupt+0x1b8/0x4b0)\n    [<c0348dc8>] (msm_slim_interrupt+0x1b8/0x4b0) from [<c00d2ccc>]\n(handle_irq_event_percpu+0x118/0x3a4)\n    [<c00d2ccc>] (handle_irq_event_percpu+0x118/0x3a4) from [<c00d2f94>]\n(handle_irq_event+0x3c/0x5c)\n    [<c00d2f94>] (handle_irq_event+0x3c/0x5c) from [<c00d5c4c>]\n(handle_fasteoi_irq+0xd0/0x11c)\n    [<c00d5c4c>] (handle_fasteoi_irq+0xd0/0x11c) from [<c00d2ae4>]\n(generic_handle_irq+0x24/0x2c)\n    [<c00d2ae4>] (generic_handle_irq+0x24/0x2c) from [<c000f370>] (handle_IRQ+0x7c/0xc0)\n    [<c000f370>] (handle_IRQ+0x7c/0xc0) from [<c0008774>] (gic_handle_irq+0x6c/0xc4)\n    [<c0008774>] (gic_handle_irq+0x6c/0xc4) from [<c0699404>] (__irq_svc+0x44/0x78)\n    Exception stack(0xee061cd8 to 0xee061d20)\n    1cc0:                                                       00000001 eebda7c8\n    1ce0: 00000000 eebda400 20000013 c12b5430 ec96c168 c12b542c c12b5430 00000001\n    1d00: 20000013 ee061e14 3eb13eb1 ee061d20 c00ba520 c069918c 20000013 ffffffff\n    [<c0699404>] (__irq_svc+0x44/0x78) from [<c069918c>]\n(_raw_spin_unlock_irqrestore+0x40/0x68)\n    [<c069918c>] (_raw_spin_unlock_irqrestore+0x40/0x68) from [<c0279f2c>]\n(__debug_object_init+0x30c/0x344)\n    [<c0279f2c>] (__debug_object_init+0x30c/0x344) from [<c007b068>]\n(init_timer_on_stack_key+0x18/0x30)\n    [<c007b068>] (init_timer_on_stack_key+0x18/0x30) from [<c0695248>]\n(schedule_timeout+0x8c/0x4c0)\n    [<c0695248>] (schedule_timeout+0x8c/0x4c0) from [<c069768c>]\n(wait_for_common+0xec/0x164)\n    [<c069768c>] (wait_for_common+0xec/0x164) from [<c0349fc4>] (msm_xfer_msg+0x3cc/0x51c)\n    [<c0349fc4>] (msm_xfer_msg+0x3cc/0x51c) from [<c034a358>]\n(slim_sat_rxprocess+0x244/0x664)\n    [<c034a358>] (slim_sat_rxprocess+0x244/0x664) from [<c0087290>]\n(process_one_work+0x354/0x648)\n    [<c0087290>] (process_one_work+0x354/0x648) from [<c0089754>]\n(worker_thread+0x1a8/0x2a8)\n    [<c0089754>] (worker_thread+0x1a8/0x2a8) from [<c008e480>] (kthread+0x90/0xa0)\n    [<c008e480>] (kthread+0x90/0xa0) from [<c000f438>] (kernel_thread_exit+0x0/0x8)\n\n    Make this lock irqsafe as well so that this potential bug doesn't\n    occur.\n\n    Change-Id: Icbef6d1d749ee6ee81b079e19e57f22c38f00c68\n    Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>\n\ncommit 62d507f313d6921b1e0aea1e80208814f67317a7\nAuthor: poondog <markj338@gmail.com>\nDate:   Tue Apr 22 13:06:16 2014 +1000\n\n    slimbus: remove this too\n\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 585e5b930ba1dcaeb6c6fe92638e7b3e6ba8ad22\nAuthor: poondog <markj338@gmail.com>\nDate:   Tue Apr 22 12:59:04 2014 +1000\n\n    slilmbus: remove some functions that are incompatible with the current setup\n    we do not have the same qdsp6v2 files as the hammerhead so this will not work\n\n    Signed-off-by: poondog <markj338@gmail.com>\n\ncommit 56ba16baf80a7a2acf99bac8f1f5b08890922aa7\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Wed Sep 12 23:21:57 2012 -0600\n\n    slim_ngd: Slimbus satellite controller driver\n\n    NGD (non-ported generic device, also known as satellite device) is\n    used to implement light-weight slimbus controller driver.\n    This driver is responsible for:\n    1. Communicating with codec (or any slimbus slave registered from\n    application processor side) directly using slimbus HW messaging\n    interface.\n    2. Communicating with the manager device (controller by master driver)\n    on LPASS to do bandwidth and data channel management. NGD takes these\n    requests from slimbus slave on application processor side and passes\n    them to the manager device using slimbus messaging itself.\n    SPS BAM is used for receiving messages to offload CPU, and to enable\n    receiving multiple messages before driver can process them.\n    Runtime-pm is used for power management. Controller is in active\n    power state when messaging and/or data-channels are active from\n    application processor side.\n\n    Change-Id: Iff53c0ca9b768a3dac3bccb5004fd2f96070af50\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 78925cab4b96dfd42f8f95d59dba59b51f15501b\nAuthor: Kiran Gunda <kgunda@codeaurora.org>\nDate:   Tue Oct 9 13:30:13 2012 +0530\n\n    slimbus: Avoid same channel definition, removal in same sequence\n\n    Do not add the channel removal request to the remove list\n    when the client sends it right after the channel definition\n    without sending reconfigure_now request. Also remove the\n    channel define request from define list. This avoids\n    channel definition count being inconsistent, which may\n    lead to slimbus driver going into wrong state.\n\n    CRs-fixed: 409161\n    Change-Id: Iec4dd51d98416b7d769176bb1ef6cd2f5bacfa12\n    Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>\n\ncommit f5f0fa405d0cbabe2de7df147448bc0da4a03993\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Wed Oct 17 12:42:03 2012 -0600\n\n    slim_msm: Allow remote management of pipes for MSM slimbus BAM\n\n    Slimbus BAM may not be locally owned and/or controlled. In that case,\n    a remote processor (e.g. LPASS) configures BAM and sets security\n    configurations for the BAM pipes.\n    Allow driver to choose whether BAM is locally or remotely managed.\n\n    Change-Id: I10741cb394428f525c1633e707e88e699aa63cf5\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 8cd00aa99ce508ea320d7c4b31ad837b943dbb64\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Sun Sep 9 17:32:46 2012 -0600\n\n    slimbus: Allow controller to specify logical addresses\n\n    It is possible that the controller has fixed addressing table for\n    enumeration devices. In that case, logical address will be set by\n    controller and not by framework. get_laddr allows a controller to\n    assign logical address. Make sure framework allows such addressing\n    by not assuming that index into address table will represent logical\n    address.\n\n    Change-Id: I0e3873980c2ee2ece01237f450ecefff4e99aedc\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit ef88b1aa410faffc434abd49292106644588df77\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Jul 24 23:44:26 2012 -0600\n\n    slimbus: Allow controller to override default scheduling algorithm\n\n    Framework provides a slimbus scheduling algorithm and controller may\n    choose to override it. e.g. controller will override this if it\n    supports fixed set of channels at a fixed clock gear.\n    In that case, it is controller's responsibility to act on client\n    requests and update channel scheduling, subframe coding information.\n\n    Change-Id: I31fe72ef85f931900467b737652da7516d173dc5\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit e0a22a6b22019297c50cf3e95d31eb54d369e214\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Aug 21 18:07:39 2012 -0600\n\n    slim_msm: Move out common functionality from MSM controller driver\n\n    Starting with new platforms, MSM slimbus controller can operate in\n    master mode or satellite mode. (Not in both modes for the same build)\n    Move out common functional code from the controller driver that can\n    be reused by satellite mode and master mode.\n\n    Change-Id: Idbc3fa93067f67f645981071ff6ad457c284576f\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 72d04b21a12c2bcaf86ae98e85244764aa3eadcf\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Wed Sep 5 12:19:24 2012 -0600\n\n    slim_msm: Satellite channel should not be deallocated more than once\n\n    It is possible that satellite channel deallocation is requested more\n    than once. (e.g. if the satellite times out waiting for response from\n    previous removal, then it will request removal again during\n    channel deallocation from its side).\n    Make sure that does not result in deallocating the channel more than\n    once.\n\n    CRs-fixed: 395926\n    Change-Id: I002635849bcaa7309de1fbddf1127c456bca6f20\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 16e06dfa6ece7238b9a95569e662fcad1b991fd9\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Sep 4 11:27:26 2012 -0600\n\n    slim_msm: Retry initial sequence messages\n\n    Initial sequence messages (logical address assignment, and master\n    capability message) are very important messages to enable the\n    devices. It is possible that the device may NACK these messages\n    initially if it is in process of acquiring sync.\n    If these type of messages fail, retry a few times before actually\n    deeming the device unresponsive. Log the registers in case of NACKs\n    to better analyze the reason.\n\n    CRs-fixed: 396230\n    Change-Id: If0824f7ba962dbce068756e810a7bad8342373ec\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 1b74f2066c48d4956a3b2ddaad47a6b2f22998f8\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Sep 4 19:56:18 2012 -0600\n\n    slimbus: Clear slimbus read transaction if synchronous read fails\n\n    Failed read transaction is removed from the table of active\n    transactions if the transaction fails\n\n    CRs-fixed: 396237\n    Change-Id: Idda4d8b5fa2cdfde8a049cc4af4d92e9e57f678a\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 435a6a4b3a8e9c24234af14fc22c04f607ee3151\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Thu Aug 16 16:43:58 2012 -0600\n\n    slimbus: Decrement channel reference during reconfigure now\n\n    Slimbus clients can specify multiple add/remove channel requests\n    through control_ch API, followed by reconfiguration request (also\n    known as \"commit request\"). Clients may rely on the reconfiguration\n    request to actuate the channel activation/removal and not the\n    control-channel API.\n    So the channel reference should be decremented during reconfiguration\n    request, and not control_ch API.\n\n    CRs-Fixed: 389518\n    Change-Id: Id6ff57c6a4cad878e35004937fb08daf3b9afe7b\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit b205adc23e9737522fb52d7f67d95f90c0780681\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Wed Aug 15 00:01:57 2012 -0600\n\n    slim_msm: Keep track of satellite reconfiguring a channel\n\n    With mutiple clients able to use the same channel, it is not correct\n    assumption that a channel was active due to satellite client's\n    reconfiguration only. So during sub-system restart of a satellite,\n    rely on satellite-reconfiguration vote for a channel instead of\n    channel status to remove channels that were setup by the satellite\n    before sub-system restart.\n\n    CRs-Fixed: 389514\n    Change-Id: I825381f15cb55396fece5b390d395c7f0a7580ff\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 33376c0388358f440f2f92aaa1003c641a4ac086\nAuthor: Joonwoo Park <joonwoop@codeaurora.org>\nDate:   Tue Aug 28 15:26:11 2012 -0700\n\n    slimbus: Defer probing slimbus until ADSP is ready\n\n    If slimbus master resides in ADSP, slimbus driver has to wait until it's\n    up and running.  Do probe deferral until ADSP is ready.\n\n    Change-Id: I31ba4e270331c3b5250758f604d0d0cde9537427\n    Signed-off-by: Joonwoo Park <joonwoop@codeaurora.org>\n\ncommit f9d4310b2eecd6cfc394675cf9e3297e08710f40\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Aug 28 12:20:49 2012 -0600\n\n    slimbus: Add slave devices to controller after controller HW is up\n\n    Register controller is only responsible for making sure slimbus\n    controller structure is initialized with framework. This should not\n    assume that slimbus controller's hardware programming is done (e.g. if\n    slave's probe is trying to get logical address, then that will fail if\n    controller is registered, but slimbus hardware programming is not\n    complete, since probe is called synchrounously when device is added.\n    So this API separates register controller from slave device\n    registration. It should be called by controller when its hardware\n    programming is complete.\n\n    Change-Id: I52fa5567fc072951c89f99c70507aa3b1e4e22af\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 88716f3e25aa5c692a6402e9cf9e5b8c21112b83\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Sat Aug 11 15:02:12 2012 -0600\n\n    slim: msm: Control interface clock if it's specified\n\n    Some platforms (e.g. 8974) have interface clock that is not ON by\n    default. Turn it ON during probe, and control it like core clock\n    if it needs to be controlled.\n\n    Change-Id: Ifffb4b7ea9afb5f3f1208b4b2b6638594ffca541\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit e11bed21cdb0cf8c7b1e93dc6dca5a8c57102c49\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Mon Jul 23 19:38:57 2012 -0600\n\n    slimbus: Callback to indicate device report present message\n\n    Clients can register a callback (just like probe) and that callback\n    will be called when the client's device reports present per slimbus\n    specification. The callback is hosted in a workqueue to avoid doing\n    it in same context from which probe is called (and/or in the context\n    receiving report present message). Callback is called when the device\n    reports present for the first time after the bus is initialized.\n\n    Change-Id: I8396b87121950f99a09764d497bf2d4b1535565d\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit bc30a59963e7e5890f6129a993c961d6c12e2cd1\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Thu Jul 26 16:56:44 2012 -0600\n\n    slimbus: Fix channel concurrent usage during reconfiguration sequence\n\n    Reconfiguration sequence can lead to changes in channel segment\n    distribution and state. Since multiple clients can use 1 channel,\n    make sure channels cannot be manipulated when reconfiguration\n    sequence is in progress, and make sure that client doesn't send\n    reconfiguration sequence when no changes are pending to be sent\n    in the sequence from it.\n\n    CRs-Fixed: 383406\n    Change-Id: Ib5f0bc32f67f51f118fa417a2e580c8dc87ef0d0\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 1dddb86909299d905a56a7dbd631112dd7a0af1d\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Jul 31 19:06:21 2012 -0600\n\n    slim:msm: Change to register access for RX path if required\n\n    MSM controller for slimbus usually uses a BAM pipe to receive control\n    data. However, some targets may not have a BAM pipe assinged for\n    receiving this data. In that case, RX data should be received using\n    direct register access instead.\n    Introduce a Device-Tree property to change this access.\n\n    Change-Id: I9bb1502f25e0e855937bc6fb4131f55348d04794\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit f4574818d4ce906544993fec33e97b48af1e4b61\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Tue Jul 24 23:04:32 2012 -0600\n\n    slimbus: Export clock pause function\n\n    Previously this function was left-out to be exported by mistake.\n    Exporting the function helps any caller driver to be a module.\n\n    Change-Id: I2b9caca62821caea5ae92123689c6f8ddf2b207a\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit 2523d1a8776fe815e209757a919d147dc519dfa4\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Wed Jul 11 15:52:46 2012 -0600\n\n    slimbus: Disconnect source port if source end is removed by client\n\n    If source end of a channel removes its vote, it should be allowed to\n    be reclaimed by other client (or by other source port by same client)\n    who wants to be the source for this channel.\n\n    CRs-Fixed: 376731\n    Change-Id: Ia30c6a4b07de7df98cde8bc928205b4f4598036d\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit a91f20ad4f0fa3c036799e6a9b1a9d73e6d1e413\nAuthor: Sagar Dharia <sdharia@codeaurora.org>\nDate:   Mon Jun 25 12:44:02 2012 -0600\n\n    slimbus: Modify check for empty slots\n\n    There was a corner case where the open slot count was going -ve\n    indicating that there are no slots left for messaging. The current\n    check to ensure non-zero messaging slots does not take that into\n    account. This commit fixes that check.\n\n    CRs-fixed: 370229\n    Change-Id: I832ce0a26f1919d3d03b4ef0311603a5a778685e\n    Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>\n\ncommit f7583a13f2195b1c38ae6254e0d147ae08d5cd80\nAuthor: David Brown <davidb@codeaurora.org>\nDate:   Thu Jan 17 16:46:16 2013 -0800\n\n    slimbus: Add Qualcomm Slimbus driver\n\n    Signed-off-by: David Brown <davidb@codeaurora.org>\n\ncommit e1907b8f4378fbfdc1c34635307f8226d8d8777c\nAuthor: poondog <markj338@gmail.com>\nDate:   Tue Apr 22 12:07:27 2014 +1000\n\n    DRIVERS: SLIMBUS: removal of current slimbus drivers\n    slimbus is overrated anyway, who needs it?\n\n    Signed-off-by: poondog <markj338@gmail.com>","poondog",true],["b818a5993e1ab28158f876196b27b4454f5d0ae8","15d7a7f70c58bf708052629c6bf93d96a446d604@gmail.com","add missing \"};\" left out by poon","ihatewebos",true],["b87ec8c8ad8ff39111d3419f26a9ca5c35a076cd","0d62248ee021b6e01c0ee596a62a5b145b996974@parallels.com","block: account iowait time when waiting for completion of IO request\n\nUsing wait_for_completion() for waiting for a IO request to be executed\nresults in wrong iowait time accounting. For example, a system having\nthe only task doing write() and fdatasync() on a block device can be\nreported being idle instead of iowaiting as it should because\nblkdev_issue_flush() calls wait_for_completion() which in turn calls\nschedule() that does not increment the iowait proc counter and thus does\nnot turn on iowait time accounting.\n\nThe patch makes block layer use wait_for_completion_io() instead of\nwait_for_completion() where appropriate to account iowait time\ncorrectly.\n\nSigned-off-by: Vladimir Davydov <vdavydov@parallels.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: flar2 <asegaert@gmail.com>","Vladimir Davydov",true],["ee95a0fe0428675982d18beabbddd4f3622768b1","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","block: Adding ROW scheduling algorithm\n\nThis patch adds the implementation of a new scheduling algorithm - ROW.\nThe policy of this algorithm is to prioritize READ requests over WRITE\nas much as possible without starving the WRITE requests.\n\nChange-Id: I4ed52ea21d43b0e7c0769b2599779a3d3869c519\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["ddc8cc017d1830e1ea98d22bf6256197a4aab992","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","block: ROW: Correct minimum values of ROW tunable parameters\n\nThe ROW scheduling algorithm exposes several tunable parameters.\nThis patch updates the minimum allowed values for those parameters.\n\nChange-Id: I5ec19d54b694e2e83ad5376bd99cc91f084967f5\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["fa0df3ea2e84755e6fccf22153a79c2b9138f0cc","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","block: ROW: Fix forced dispatch\n\nThis patch fixes forced dispatch in the ROW scheduling algorithm.\nWhen the dispatch function is called with the forced flag on, we\ncan't delay the dispatch of the requests that are in scheduler queues.\nThus, when dispatch is called with forced turned on, we need to cancel\nidling, or not to idle at all.\n\nChange-Id: I3aa0da33ad7b59c0731c696f1392b48525b52ddc\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["ef16191e386d9c0b59ed21d914618083dffe49e7","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","block: Add API for urgent request handling\n\nThis patch add support in block & elevator layers for handling\nurgent requests. The decision if a request is urgent or not is taken\nby the scheduler. Urgent request notification is passed to the underlying\nblock device driver (eMMC for example). Block device driver may decide to\ninterrupt the currently running low priority request to serve the new\nurgent request. By doing so READ latency is greatly reduced in read&write\ncollision scenarios.\n\nNote that if the current scheduler doesn't implement the urgent request\nmechanism, this code path is never activated.\n\nChange-Id: I8aa74b9b45c0d3a2221bd4e82ea76eb4103e7cfa\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\n\nConflicts:\n\tblock/blk-core.c\n\tblock/blk-settings.c\n\tblock/blk.h\n\tblock/elevator.c\nmodified for HTC M7\n\nSigned-off-by: Paul Reioux <reioux@gmail.com>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["1b66e96c3fc4fa1cb6add06b29b6cbc049f02123","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","row: Adding support for reinsert already dispatched req\n\nAdd support for reinserting already dispatched request back to the\nschedulers internal data structures.\nThe request will be reinserted back to the queue (head) it was\ndispatched from as if it was never dispatched.\n\nChange-Id: I70954df300774409c25b5821465fb3aa33d8feb5\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["9f6994db177fb9a6620dedeba1494a8a89fb8d45","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","block:row: fix idling mechanism in ROW\n\nThis patch addresses the following issues found in the ROW idling\nmechanism:\n1. Fix the delay passed to queue_delayed_work (pass actual delay\n   and not the time when to start the work)\n2. Change the idle time and the idling-trigger frequency to be\n   HZ dependent (instead of using msec_to_jiffies())\n3. Destroy idle_workqueue() in queue_exit\n\nChange-Id: If86513ad6b4be44fb7a860f29bd2127197d8d5bf\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["b2b6357646b8b9c2767804af7ad99fff9476beb1","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","row: Add support for urgent request handling\n\nThis patch adds support for handling urgent requests.\nROW queue can be marked as \"urgent\" so if it was un-served in last\ndispatch cycle and a request was added to it - it will trigger\nissuing an urgent-request-notification to the block device driver.\nThe block device driver may choose at stop the transmission of current\nongoing request to handle the urgent one. Foe example: long WRITE may\nbe stopped to handle an urgent READ. This decreases READ latency.\n\nChange-Id: I84954c13f5e3b1b5caeadc9fe1f9aa21208cb35e\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["51f9f7e77ca8c6f37ed5a01f2d6f8ad5e3e826c1","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","block: row: Add some debug information on ROW queues\n\n1. Add a counter for number of requests on queue.\n2. Add function to print queues status (number requests\n   currently on queue and number of already dispatched requests\n   in current dispatch cycle).\n\nChange-Id: I1e98b9ca33853e6e6a8ddc53240f6cd6981e6024\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["2d6bb95499889c57000dfeb8fa37ab1980417417","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","block: row: Insert dispatch_quantum into struct row_queue\n\nThere is really no point in keeping the dispatch quantum\nof a queue outside of it. By inserting it to the row_queue\nstructure we spare extra level in accessing it.\n\nChange-Id: Ic77571818b643e71f9aafbb2ca93d0a92158b199\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["1da0fc5b5a1f2b1d38395b3ae474ac3e4c21c1da","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","block: row: fix sysfs functions - idle_time conversion\n\nidle_time was updated to be stored in msec instead of jiffies.\nSo there is no need to convert the value when reading from user or\ndisplaying the value to him.\n\nChange-Id: I58e074b204e90a90536d32199ac668112966e9cf\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true],["edb8bc22ebf26726dacb3e8e70fed51da972085f","c7fa93ff364b50c0a977a853487528f982a1ac48@codeaurora.org","block: row: Aggregate row_queue parameters to one structure\n\nEach ROW queues has several parameters which default values are defined\nin separate arrays. This patch aggregates all default values into one\narray.\nThe values in question are:\n - is idling enabled for the queue\n - queue quantum\n - can the queue notify on urgent request\n\nChange-Id: I3821b0a042542295069b340406a16b1000873ec6\nSigned-off-by: Tatyana Brokhman <tlinder@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","Tatyana Brokhman",true]],"size":43,"ref":"refs/heads/ihate","head":"81d331caf3130686d4895ea821a07b741fedae35"}