3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Barry Grussling
commit b579fa52f6be0b4157ca9cc5e94d44a2c89a7e95 upstream.
This patch adds support for the Schweitzer Engineering Laboratories
C662 USB cable based off the CP210x driver.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sami Rahman
commit 7681156982026ebf7eafd7301eb0374d7648d068 upstream.
Added support for MMB Networks and Planet Innovation Ingeni ZigBee USB
devices using customized Silicon Labs' CP210x.c USB
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 5ec2481b7b47a4005bb446d176e5d0257400c77d upstream.
smp_call_function_* must not be called from softirq context.
But clock_was_set() which calls on_each_cpu() is called
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Jeffery
commit 1c327d962fc420aea046c16215a552710bde8231 upstream.
In nlmsvc_retry_blocked, the check that the list is non-empty and acquiring
the pointer of the first entry is
Congrats!! your Email has Won the Yahoo HK Lotto Cash Prize valued at
Three Million Five Hundred Thousand Dollars. Please Contact Fran Mayer
on Tel: +447031909741 or Email: promos_...@yahoo.com.hk to claim your
prize Money.
--
To unsubscribe from this list: send the line "unsubscribe
On Fri, Jul 26, 2013 at 09:52:56AM +, Feng-Hsin Chiang wrote:
> FOTG210 is an OTG controller which can be configured as an
> USB2.0 host. FOTG210 host is an ehci-like controller with
> some differences. First, register layout of FOTG210 is
> incompatible with EHCI. Furthermore, FOTG210 is lack
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eldad Zack
commit be2f93a4c4981b3646b6f98f477154411b8516cb upstream.
Return SNDRV_PCM_POS_XRUN (snd_pcm_uframes_t) instead of
SNDRV_PCM_STATE_XRUN (snd_pcm_state_t) from the pointer
function
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Enrico Mioso
commit 63b5df963f52ccbab6fabedf05b7ac6b465789a4 upstream.
This patch adds support for the ONYX 3G device (version 1) from ALFA
NETWORK.
Signed-off-by: Enrico Mioso
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "zhangwei(Jovi)"
commit 11034ae9c20f4057a6127fc965906417978e69b2 upstream.
All syscall tracing irqs-off tags are wrong, the syscall enter entry doesn't
disable irqs.
[root@jovi tracing]#echo
On Fri, Jul 26, 2013 at 1:18 PM, Cyrill Gorcunov wrote:
> Andy reported that if file page get reclaimed we loose soft-dirty bit
> if it was there, so save _PAGE_BIT_SOFT_DIRTY bit when page address
> get encoded into pte entry. Thus when #pf happens on such non-present
> pte we can restore it
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Yongjun
[ Upstream commit e1558a93b61962710733dc8c11a2bc765607f1cd ]
Add missing .owner of struct pppox_proto. This prevents the
module from being removed from underneath its users.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit a5cc68f3d63306d0d288f31edfc2ae6ef8ecd887 ]
key_notify_sa_flush() and key_notify_policy_flush() miss to initialize
the sadb_msg_reserved member of the
On Thursday 25 of July 2013 21:03:43 Mark Brown wrote:
> On Thu, Jul 25, 2013 at 12:42:00PM -0700, Vincent Palatin wrote:
> > +- regulator-suspend-disk-microvolt: voltage applied when entering S2D
> > +- regulator-suspend-disk-disabled: turn off when entering S2D
> > +-
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sergei Shtylyov
[ Upstream commit ca8c35852138ee0585eaffe6b9f10a5261ea7771 ]
EESR.RFE (receive FIFO overflow) interrupt is enabled by the driver on all SoCs
and sh_eth_error() handles it but
This is the start of the stable review cycle for the 3.4.55 release.
There are 59 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Jul 28 20:48:22 UTC 2013.
Anything
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Fabio Estevam
commit 5c78dfe87ea04b501ee000a7f03b9432ac9d008c upstream.
SGTL5000_PLL_FRAC_DIV_MASK is used to mask bits 0-10 (11 bits in total) of
register CHIP_PLL_CTRL, so fix the mask to
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 5ec2481b7b47a4005bb446d176e5d0257400c77d upstream.
smp_call_function_* must not be called from softirq context.
But clock_was_set() which calls on_each_cpu() is called
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit 1eb4f758286884e7566627164bca4c4a16952a83 ]
We could end up expiring a route which is part of an ecmp route set. Doing
so would invalidate the
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Enrico Mioso
commit 3d1a69e726406ab662ab88fa30a3a05ed404334d upstream.
Prevent the option driver from binding itself to the QMI/WWAN interface, making
it unusable by the proper driver.
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Eldad Zack
commit be2f93a4c4981b3646b6f98f477154411b8516cb upstream.
Return SNDRV_PCM_POS_XRUN (snd_pcm_uframes_t) instead of
SNDRV_PCM_STATE_XRUN (snd_pcm_state_t) from the pointer
function
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: "Alexandr \\\"Sky\\\" Ivanov"
commit ca24763588844b14f019ffc45c7df6d9e8f932c5 upstream.
Adding support for D-Link DWM-152/C1 and DWM-156/C1 devices.
DWM-152/C1:
T: Bus=01 Lev=01 Prnt=01
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Enrico Mioso
commit 63b5df963f52ccbab6fabedf05b7ac6b465789a4 upstream.
This patch adds support for the ONYX 3G device (version 1) from ALFA
NETWORK.
Signed-off-by: Enrico Mioso
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit f3e351eef3a7fd1e36a3e18d4f2f069b00deb23c upstream.
The quirk for Dell laptops with STAC9228 overrides the pin default
config of NID 0x0f to the value with
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Enrico Mioso
commit 878c69aae986ae97084458c0183a8c0a059865b1 upstream.
Some (very few) early devices like mine, where not exposting a proper CDC
descriptor. This was fixed with an immediate
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Luiz Angelo Daros de Luca
commit 90625070c4253377025878c4e82feed8b35c7116 upstream.
This adds NetGear Managed Switch M4100 series, M5300 series, M7100 series
USB ID (0846:0110) to the cp210x
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 1ea9a69d1a36a5b62bf281ba8bb304fcac656dad upstream.
The EAPD GPIO is dynamically turned on/off for some machines with
Sigmatel codecs, but this didn't work as expected, and
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Daniil Bolsun
commit c38e83b6cc2adf80e3f091fd92cfbeacc9748347 upstream.
This patch was tested on 3.10.1 kernel.
Same models of Petatel NP10T modems have different device IDs.
Unfortunately
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Frysinger
commit 6287e7319870ec949fb809e4eb4154c2b05b221f upstream.
Commit 8ef6e6201b26cb9fde79c1baa08145af6aca2815 (ARM: footbridge: use
fixed PCI i/o mapping) broke booting on my
From: Eric Dumazet
Date: Tue, 23 Jul 2013 17:15:54 -0700
> From: Eric Dumazet
>
> usbnet doesn't support yet SG, so drivers should not advertise SG or TSO
> capabilities, as they allow TCP stack to build large TSO packets that
> need to be linearized and might use order-5 pages.
>
> This
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 3e3aac497513c669e1c62c71e1d552ea85c1d974 ]
egress_priority_map[] hash table updates are protected by rtnl,
and we never remove elements until device is
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ralf Baechle
commit 27f62b9f294b7e2019c94c385abda43a0af6bb8b upstream.
CC drivers/rapidio/switches/idt_gen2.o
drivers/rapidio/switches/idt_gen2.c: In function ‘idtg2_show_errlog’:
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Sylwester Nawrocki
commit d817468c4b2892b9468e2a0c92116e38a3a61370 upstream.
This patch restores serial port operation which has been broken since
commit 60e93575476f ("serial: samsung:
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Williams
commit 4cf76df06ecc852633ed927d91e01c83c33bc331 upstream.
Speaks AT on interfaces 5 (command & PPP) and 3 (secondary), other
interface protocols are unknown.
Signed-off-by: Dan
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Wang
[ Upstream commit 885291761dba2bfe04df4c0f7bb75e4c920ab82e ]
We try to linearize part of the skb when the number of iov is greater than
MAX_SKB_FRAGS. This is not enough since each
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit a5faeaf9109578e65e1a32e2a3e76c8b47e7dcb6 upstream.
Code in blkdev.c moves a device inode to default_backing_dev_info when
the last reference to the device is put and moves the
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 94190301ffa059c2d127b3a67ec5d161d5c62681 upstream.
Signed-off-by: Bjørn Mork
Signed-off-by: Greg Kroah-Hartman
---
drivers/usb/serial/option.c |2 ++
1 file changed,
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ralf Baechle
commit 39205750efa6d335fac4f9bcd32b49c7e71c12b7 upstream.
If CONFIG_CAVIUM_OCTEON_LOCK_L2_TLB, CONFIG_CAVIUM_OCTEON_LOCK_L2_EXCEPTION,
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Wang
[ Upstream commit 3b7b514f44bff05d26a6499c4d4fac2a83938e6e ]
This is a regression introduced by
commit fd58156e456d9f68fe0448 (IPIP: Use ip-tunneling code.)
Similar to GRE tunnel,
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Sami Rahman
commit 7681156982026ebf7eafd7301eb0374d7648d068 upstream.
Added support for MMB Networks and Planet Innovation Ingeni ZigBee USB
devices using customized Silicon Labs' CP210x.c
On Fri, Jul 26, 2013 at 1:30 PM, Felipe Balbi wrote:
> On Fri, Jul 26, 2013 at 09:23:35AM -0700, Olof Johansson wrote:
>> On Fri, Jul 26, 2013 at 2:54 AM, Felipe Balbi wrote:
>> > On Thu, Jul 25, 2013 at 01:59:51PM -0700, Olof Johansson wrote:
>> >> On Thu, Jul 25, 2013 at 10:19 AM, Felipe Balbi
On Friday 26 of July 2013 09:40:15 Stephen Warren wrote:
> (CC'ing the new DT binding maintainers and mailing list on this reply,
> hence quoting the whole of the DT binding)
>
> On 07/25/2013 06:29 AM, Laxman Dewangan wrote:
> > Palmas series device like TPS65913, TPS80036 supports the backup
>
On Fri, Jul 26, 2013 at 10:28 PM, H. Peter Anvin wrote:
> On 07/26/2013 01:24 PM, Ingo Molnar wrote:
>>
>> Am I being too pedantic in expecting that we still mark it
>> e820-reserved?
>>
>> This area really isnt an ordinary PCI resource such as a
>> BAR or an MMIO region. It's truly system RAM
There exists a PRIMARY_SECONDARY_PAD3 in the same register base as
PRIMARY_SECONDARY_PAD2, which controls the function of certain pins. Add
a property for this setting.
Signed-off-by: Andrew Chew
---
Documentation/devicetree/bindings/mfd/palmas.txt | 3 ++-
drivers/mfd/palmas.c
It seems that the value read back from the PALMAS_GPIO_DATA_IN register
isn't valid if the GPIO direction is out. When that's the case, we can
read back the PALMAS_GPIO_DATA_OUT register to get the proper output value.
Change-Id: Iaf877e538cfdb37a6759c45ec3c6e4ee31078709
Signed-off-by: Andrew
On 07/26/2013 10:15 PM, Bin Liu wrote:
> Sebastian,
Hi Bin,
> I started thinking when I tried this git.ti.com 3.8 kernel, I might
> have done 'devmem2 0x47401c60 b 0x81' to manually set the SESSION bit
> after plugged a device. It was months ago, I don't quite remember what
> I tested.
Ah. You
Systems with Intel graphics controllers set aside memory exclusively for
gfx driver use. This memory is not always marked in the E820 as
reserved or as RAM, and so is subject to overlap from E820 manipulation
later in the boot process. On some systems, MMIO space is allocated on
top, despite the
For use by userspace (at some point in the future) and other kernel code.
v2: move PCI IDs to uabi (Chris)
move PCI IDs to drm/ (Dave)
v3: fixup Quanta detection - needs to come first (Daniel)
v4: fix up PCI match structure init for easier use by userspace (Chris)
Signed-off-by: Jesse Barnes
These address the comments I've received so far, but omit the new E820
type for this mem.
Chris's patches could go on top if desired; they add a new type and
resource reservation function for looking up regions by name. That
allows us to remove some duplicate code in the driver for finding
Hi,
On Fri, Jul 26, 2013 at 06:44:23PM +, Paul Zimmerman wrote:
> > From: Felipe Balbi [mailto:ba...@ti.com]
> > Sent: Friday, July 26, 2013 2:54 AM
> > > > > Also, this is not *modifying* what was passed, just skipping the xHCI
> > > > > address space so we don't request_mem_region() an area
On Fri, Jul 26, 2013 at 09:23:35AM -0700, Olof Johansson wrote:
> On Fri, Jul 26, 2013 at 2:54 AM, Felipe Balbi wrote:
> > On Thu, Jul 25, 2013 at 01:59:51PM -0700, Olof Johansson wrote:
> >> On Thu, Jul 25, 2013 at 10:19 AM, Felipe Balbi wrote:
> >> > On Thu, Jul 25, 2013 at 09:18:39AM -0700,
On 07/26/2013 01:24 PM, Ingo Molnar wrote:
>
> Am I being too pedantic in expecting that we still mark it
> e820-reserved?
>
> This area really isnt an ordinary PCI resource such as a
> BAR or an MMIO region. It's truly system RAM (which cannot
> be moved/reallocated), used by graphics
Hi,
So at the moment the kernel has pretty comprehensive support for the
*at() variants of file API calls, and at one point I was rewriting my
app to be a modern Unix citizen and use the *at variants, but I ran into
one admittedly obscure corner case, which is the lack of API calls to
manipulate
On Fri, Jul 26, 2013 at 03:31:34PM +0300, Ivan T. Ivanov wrote:
>
> Hi Felipe,
>
> On Thu, 2013-07-25 at 16:43 +0300, Ivan T. Ivanov wrote:
> > On Wed, 2013-07-24 at 15:39 +0300, Felipe Balbi wrote:
> > > On Tue, Jul 09, 2013 at 06:47:09PM +0300, Ivan T. Ivanov wrote:
> > > > From: "Ivan T.
On Fri, Jul 26, 2013 at 01:19:30PM -0700, H. Peter Anvin wrote:
> Hi everyone,
>
> I have tagged this one for -stable, but it is a definite "maybe", so I
> wanted to:
>
> a) qualify that tagging, and
> b) perhaps use it as a boundary case for policy clarification.
>
> This patch is an old bug,
* Jesse Barnes wrote:
> On Thu, 25 Jul 2013 20:31:27 -0700
> "H. Peter Anvin" wrote:
>
> > On 07/25/2013 07:14 PM, Jesse Barnes wrote:
> > > To clarify: it'll either be marked reserved or not listed at all in e820,
> > > which is why I did this early, before any other e820 stuff like the
Hi everyone,
I have tagged this one for -stable, but it is a definite "maybe", so I
wanted to:
a) qualify that tagging, and
b) perhaps use it as a boundary case for policy clarification.
This patch is an old bug, an incorrect assembly constraint, but as
happens with this type of bug it is being
Andy reported that if file page get reclaimed we loose soft-dirty bit
if it was there, so save _PAGE_BIT_SOFT_DIRTY bit when page address
get encoded into pte entry. Thus when #pf happens on such non-present
pte we can restore it back.
Reported-by: Andy Lutomirski
Signed-off-by: Cyrill Gorcunov
This patch copies the phy support bits from dsps into the generic phy
driver. Most code can be re-used except for the on/off.
The additional am335x can be removed once we have a phy driver that does
more than this.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/phy/phy-generic.c | 116
Hi,
The last series has been rebased ontop Felipe's testing branch. It contains
only the support for multiple devices. I decided to keep the temporary change
in the nop (now generic) phy driver which should ease the transition.
I still have the problem that the second USB port does not work
The "nop" driver isn't a do-nothing-stub but supports a couple functions
like clock on/off or is able to use a voltage regulator. This patch
simply renames the driver to "generic" since it is easy possible to
extend it by a simple function istead of writing a complete driver.
Signed-off-by:
dsps uses a nop driver which is added in dsps itself and does the PHY
on/off calls within dsps. Since those calls are now moved the nop driver
itself, we can now request the phy proper phy and remove those calls.
Currently only the first musb interface is used so we only add one phy
node for now.
This moves the two instances from the big node into two child nodes. The
glue layer ontop does almost nothing.
There is one devices containing the (2) phy, (2) usb and later the dma
engine. The usb device is the "glue device" which contains the musb
device as a child. This is what we do ever
Sebastian,
On Fri, Jul 26, 2013 at 2:55 PM, Sebastian Andrzej Siewior
wrote:
> The bit is removed in otg_timer() because the phy gets into
> OTG_STATE_A_WAIT_BCON.
>
> Now, this is current HEAD + my stuff to get second port working. I
> downloaded v3.2 and browsed as I was looking for the
* Don Zickus wrote:
> On Fri, Jul 26, 2013 at 02:49:34PM +0200, Michal Hocko wrote:
> > proc_dowatchdog doesn't synchronize multiple callers which
> > might lead to confusion when two parallel callers might confuse
> > watchdog_enable_all_cpus resp. watchdog_disable_all_cpus (e.g. watchdog
> >
Commit-ID: 323f54ed0f3ce20e9946c961fc928ccdb80d9345
Gitweb: http://git.kernel.org/tip/323f54ed0f3ce20e9946c961fc928ccdb80d9345
Author: Tom Rini
AuthorDate: Thu, 25 Jul 2013 14:26:10 -0400
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2013 21:54:01 +0200
numa: Mark __node_set() as
Quoting Cho KyongHo (2013-07-26 04:27:54)
> This adds gate clocks of all System MMUs and their master IPs
> that are not apeared in clk-exynos5250.c
>
> Signed-off-by: Cho KyongHo
Change looks good to me. Are you OK if I take it into the clk tree or do
you want to keep this series together?
It seems that the value read back from the PALMAS_GPIO_DATA_IN register
isn't valid if the GPIO direction is out. When that's the case, we can
read back the PALMAS_GPIO_DATA_OUT register to get the proper output value.
Change-Id: Iaf877e538cfdb37a6759c45ec3c6e4ee31078709
Signed-off-by: Andrew
On 25-07-2013 13:33, Pawel Moll wrote:
> On Thu, 2013-07-25 at 18:20 +0100, Eduardo Valentin wrote:
thermal_zone {
type = "CPU";
>>>
>>> So what does this exactly mean? What is so special about CPU? What other
>>> types you've got there? (Am I just lazy not looking at the
On 07/26/2013 08:29 PM, Bin Liu wrote:
Hi Bin,
>> [ 97.570852] musb-hdrc musb-hdrc.1.auto: Poll devctl 19 (a_wait_bcon)
> I don't think you are testing with the 3.2 kernel you referred from
> the ti.com link you mentioned above.
> 3.2 kernel should have no '.auto' at the end of the device
On Fri, Jul 26, 2013 at 8:55 AM, Catalin Marinas
wrote:
>
> - Stack size increased to 16K (similar to other 64-bit architectures)
I pulled, but this is misleading.
*Some* other 64-bit architectures do 16k stack sizes. But neither
x86-64 nor powerpc do, afaik. Instead, they do irq stacks, which
[+cc linux-acpi]
On Fri, Jul 26, 2013 at 12:51 AM, Rui Wang wrote:
> Hi Bjorn,
>
> This was originally the method I used to test hotplug on Intel SDV machines
> which are not capable of doing hotplug. I would like to present it here in
> case it interests the community, then it can be made
A new trace event is added to pm events to print time it takes to suspend and
resume a device. It generates trace message that includes device, driver,
parent information in addition to the type of pm ops invoked as well as the
pm event and error status from the pm ops. Example trace below:
Heinz and Frantisek,
I believe your issue should be fixed by this patch:
http://marc.info/?l=linux-usb=137476546506888=2
Please let me know if it doesn't.
Sarah Sharp
On Sat, May 11, 2013 at 04:09:25PM +0200, Heinz Diehl wrote:
> On 11.05.2013, Frantisek Hrbata wrote:
>
> > I haven't tried
On 07/23/2013 10:09 PM, Richard Zhao wrote:
> The patch series aim to move apbdma to generic DT binding.
>
> Changes:
> - It add dmas/dma-names properties while leave
> nvidia,dma-request-selector to be compatible.
> - update apbdma driver and dma client drivers
> - ASoC tegra adds a new struct
I am aware that it it is always recommended that attributes must be
associate via attribute groups when calling device_register() .
This way when the device is created, user space can always see
attributes once they get device create notification via uevent.
I have need to create/delete
On Wed, Jul 24, 2013 at 3:05 PM, Greg Kroah-Hartman
wrote:
> The dev_attrs field of struct class is going away soon, dev_groups
> should be used instead. This converts the led class code to use the
> correct field.
>
> Cc: Bryan Wu
> Cc: Richard Purdie
> Signed-off-by: Greg Kroah-Hartman
>
On Fri, Jul 26, 2013 at 11:50 AM, Mark Brown wrote:
> On Fri, Jul 26, 2013 at 11:25:32AM -0700, Felipe F. Tonello wrote:
>> From: "Felipe F. Tonello"
>>
>> ALSA standard jacks already are implemented using ALSA KControl.
>> So there is no need implement that itself or to use snd_jack for input
Mark,
On Fri, Jul 26, 2013 at 11:54 AM, Mark Brown wrote:
> On Fri, Jul 26, 2013 at 11:25:30AM -0700, Felipe F. Tonello wrote:
>
>> +
>> + /* Update ALSA KControl interface */
>> + snd_kctl_jack_report((struct snd_card *)jack->kctl->private_data,
>> jack->kctl, !!status);
>
> This isn't
(Also CC'ing in the DT bindings maintainers, hence quoting all of the
binding.)
On 07/26/2013 04:15 AM, Laxman Dewangan wrote:
> TI Palam series Power Management IC have multiple pins which can be
S/Palam/Palmas/ right? This name seems to get typo'd an awful lot, both
in this patch and others...
Hi Mark,
On Fri, Jul 26, 2013 at 11:46 AM, Mark Brown wrote:
> On Fri, Jul 26, 2013 at 11:25:30AM -0700, Felipe F. Tonello wrote:
>
>> - snprintf(kctl->id.name, sizeof(kctl->id.name), "%s Jack", name);
>> +
>> + strlcpy(kctl->id.name, name, sizeof(kctl->id.name));
>
> This looks like
Hi Mark,
On Fri, Jul 26, 2013 at 11:56 AM, Mark Brown wrote:
> On Fri, Jul 26, 2013 at 11:25:33AM -0700, Felipe F. Tonello wrote:
>> From: "Felipe F. Tonello"
>>
>> ALSA standard jacks already are implemented using ALSA KControl.
>> So there is no need implement that itself or to use snd_jack
On Fri, Jul 26, 2013 at 11:25:33AM -0700, Felipe F. Tonello wrote:
> From: "Felipe F. Tonello"
>
> ALSA standard jacks already are implemented using ALSA KControl.
> So there is no need implement that itself or to use snd_jack
> for input events only.
Similar changlog comment as on the ASoC
On Fri, Jul 26, 2013 at 11:25:30AM -0700, Felipe F. Tonello wrote:
> +
> + /* Update ALSA KControl interface */
> + snd_kctl_jack_report((struct snd_card *)jack->kctl->private_data,
> jack->kctl, !!status);
This isn't ideal for multi-function jacks like headsets - it will report
a
On Fri, Jul 26, 2013 at 12:01 PM, Sudeep KarkadaNagesha
wrote:
> Rob,
>
> On 22/07/13 12:32, Sudeep KarkadaNagesha wrote:
>> From: Sudeep KarkadaNagesha
>>
>> Multiple drivers need to get the cpu device node from the cpu logical
>> index and then access the of_node.
>>
>> This patch adds helper
On Fri, Jul 26, 2013 at 04:16:42PM +0200, Michal Hocko wrote:
> On Thu 25-07-13 18:25:37, Johannes Weiner wrote:
> > System calls and kernel faults (uaccess, gup) can handle an out of
> > memory situation gracefully and just return -ENOMEM.
> >
> > Enable the memcg OOM killer only for user
On Fri, Jul 26, 2013 at 11:25:32AM -0700, Felipe F. Tonello wrote:
> From: "Felipe F. Tonello"
>
> ALSA standard jacks already are implemented using ALSA KControl.
> So there is no need implement that itself or to use snd_jack for input
> events only.
This changelog doesn't correspond to the
On Fri, Jul 26, 2013 at 11:25:30AM -0700, Felipe F. Tonello wrote:
> - snprintf(kctl->id.name, sizeof(kctl->id.name), "%s Jack", name);
> +
> + strlcpy(kctl->id.name, name, sizeof(kctl->id.name));
This looks like it'd break existing users unless they are updated to
remove the "Jack" from
On Fri, Jul 26, 2013 at 03:52:07PM +0200, Michal Hocko wrote:
> On Thu 25-07-13 18:25:36, Johannes Weiner wrote:
> > The x86 fault handler bails in the middle of error handling when the
> > task has a fatal signal pending. For a subsequent patch this is a
> > problem in OOM situations because it
On Fri, Jul 26, 2013 at 03:19:47PM +0200, Michal Hocko wrote:
> On Thu 25-07-13 18:25:35, Johannes Weiner wrote:
> > Unlike global OOM handling, memory cgroup code will invoke the OOM
> > killer in any OOM situation because it has no way of telling faults
> > occuring in kernel context - which
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Friday, July 26, 2013 2:54 AM
> > > > Also, this is not *modifying* what was passed, just skipping the xHCI
> > > > address space so we don't request_mem_region() an area we won't really
> > > > handle and prevent xhci-hcd.ko from probing.
> > >
>
On Fri, 2013-07-26 at 10:38 -0700, Greg Kroah-Hartman wrote:
> > Signed-off-by: Oleg Nesterov
>
> Acked-by: Greg Kroah-Hartman
Thanks Greg, I appreciate this.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 07/26/2013 11:22 AM, Mark Rutland wrote:
> On Fri, Jul 26, 2013 at 04:11:57PM +0100, Mark Langsdorf wrote:
>> Some board designs do not drive the SATA transmit lines within the
>> specification. The ECME can provide override settings, on a per board
>> basis, to bring the transmit lines within
On 07/26/2013 11:26 AM, Mark Rutland wrote:
> On Fri, Jul 26, 2013 at 04:11:58PM +0100, Mark Langsdorf wrote:
>> Some SGPIO PICs don't follow the standard very well and expect a
>> certain number of clock cycles or port frames in each SGPIO pattern.
>> Add two optional parameters in the DTB that
Sebastian,
On Fri, Jul 26, 2013 at 1:22 PM, Sebastian Andrzej Siewior
wrote:
> On 07/26/2013 08:17 PM, Bin Liu wrote:
>
> Hi Bin.
>
>>> In TI 3.2 kernel, the otg_timer() toggles the SESSION bit in
>>> OTG_STATE_B_IDLE state. So whenever the ID pin is grounded by
>>> connecting a device, the
On 07/26/2013 02:27 PM, Arjan van de Ven wrote:
On 7/26/2013 11:13 AM, Rik van Riel wrote:
Could you try running the tests with just the repeat mode
stuff from commit 69a37bea excluded, but leaving the common
infrastructure and commit e11538?
personally I think we should go the other way
On 7/26/2013 11:13 AM, Rik van Riel wrote:
Could you try running the tests with just the repeat mode
stuff from commit 69a37bea excluded, but leaving the common
infrastructure and commit e11538?
personally I think we should go the other way around.
revert the set entirely first, and now,
From: "Felipe F. Tonello"
This patch series enable KControl support for core Jack and update current
codecs. This will will enable moderns user-space daemons, such as
PulseAudio(>=2.0), to have jack detection support via newer ALSA KControl
interface.
Patch 1: Actually implementation using
From: "Felipe F. Tonello"
ALSA standard jacks already are implemented using ALSA KControl. So there is
no need implement that itself or to use snd_jack for input events only.
Signed-off-by: Felipe F. Tonello
---
sound/pci/hda/Kconfig | 8
sound/pci/hda/hda_codec.h | 2 --
From: "Felipe F. Tonello"
This patch adds jack support for alsa kcontrol.
This support is necessary since the new kcontrol is used by user-space
daemons, such as PulseAudio(>=2.0), to do jack detection.)
Signed-off-by: Felipe F. Tonello
---
include/sound/jack.h | 6 --
From: "Felipe F. Tonello"
ALSA standard jacks already are implemented using ALSA KControl.
So there is no need implement that itself or to use snd_jack for input
events only.
Signed-off-by: Felipe F. Tonello
---
include/sound/soc.h| 2 +-
sound/soc/fsl/wm1133-ev1.c |
301 - 400 of 1610 matches
Mail list logo
