Some regulators don't report any voltage values, so checking supported
voltage range results in disabling all SDHCI_CAN_VDD_* flags and
registration failure. This patch finally provides a correct fix for the
registration of SDHCI driver with all possible voltage regulators:
dummy, fixed and regulat
Hi Iwai,
Ouch, the subject reads "[PATCH 2/3]" but this is patch 3 of the series
and should be applied last. I am sorry for the noise.
Thanks,
Fernando
On 2013/02/12 16:54, Fernando Luis Vázquez Cao wrote:
Substitute ALC889 for ALC882 in macro and function names.
Cc: sta...@vger.kernel.org
C
* H. Peter Anvin wrote:
> On 02/11/2013 07:33 PM, Linus Torvalds wrote:
> > On Mon, Feb 11, 2013 at 5:37 PM, tip-bot for H. Peter Anvin
> > wrote:
> >>
> >> However, we can declare a bitfield using sizeof(), which is legal
> >> because sizeof() is a constant expression. This quiets the warning
On 02/05/2013 11:20 AM, Nicolas Ferre :
> Arnd, Olof,
>
> As I realized reading Linus' email that it was not possible to queue more
> fixes for 3.8, I took my time to send this tiny pull request. But now that
> the merge window is approaching, I prefer not to wait for more material.
> So, here is
On 12.02.2013 01:54, Jonathan Nieder wrote:
> Sarah Sharp wrote:
>
>> Can you turn on CONFIG_USB_DEBUG and CONFIG_USB_XHCI_HCD_DEBUGGING,
>> recompile the 3.7.5 kernel, and send me dmesg starting from the point
>> you unmount the device and then power it off?
>>
>> I'd like to keep that patch in s
* Andi Kleen wrote:
> From: Andi Kleen
>
> Recent Intel CPUs like Haswell and IvyBridge have a new alternative MSR
> range for perfctrs that allows writing the full counter width. Enable this
> range if the hardware reports it using a new capability bit.
>
> This lowers the overhead of perf s
* Andi Kleen wrote:
> From: Andi Kleen
>
> This avoids some problems with spurious PMIs on Haswell.
> Haswell seems to behave more like P4 in this regard. Do
> the same thing as the P4 perf handler by unmasking
> the NMI only at the end. Shouldn't make any difference
> for earlier non P4 cores
On Tue, 2013-02-12 at 17:18 +1100, Michael Ellerman wrote:
>
> I don't think you can, "active" is not well defined. Other code may have
> done nothing other than create the mapping and remembered the virq,
> which will break if you destroy the mapping. Or?
Active as in "requested". Yes there's a
On 12.02.2013 08:06, Mike Galbraith wrote:
>> In this case pick_next_task takes idle tasks and idle wastes cpu
>> time.
> That's not a waste of CPU time, that's utilization enforcement the thing
> it is designed to do.
Well this is a philosophical question and the opinions will IMHO
vary strongl
* Andi Kleen wrote:
> From: Andi Kleen
>
> Add support for the v2 PEBS format. It has a superset of the v1 PEBS
> fields, but has a longer record so we need to adjust the code paths.
The changelog talks about a 'v2' PEBS format - the code talks
about 'fmt2':
> +/*
> + * Same as pebs_record_
On Mon, Feb 11, 2013 at 03:54:05PM +, Pandruvada, Srinivas wrote:
> So finally we can use HID sensor hub over I2C.
> Did you try with any I2C sensor hub?
Yes, we have I2C HID sensor hub here and I tested with it. However, I'm not
that familiar how it should be used except that I can see the se
On 2013-02-11 00:58, Grant Likely wrote:
This patch creates of_count_phandle_with_args(), a new function for
counting the number of phandle+argument tuples in a given property. This
is better than the existing method of parsing each phandle individually
until parsing fails which is a horribly slo
Hi Heiko,
On Mon, Feb 11, 2013 at 10:11 AM, Heiko Carstens
wrote:
> Thanks Geert. A similar patch however is already in linux-next, together
> with a whole bunch of other patches which try to make s390's allmodconfig
> compile again after PCI, HAS_DMA and HAS_IOMEM got enabled by our new PCI
> co
At Tue, 12 Feb 2013 16:47:44 +0900,
Fernando Luis Vázquez Cao wrote:
>
> Some Vaio all-in-one desktop PCs (for example VGC-LN51JGB) are affected by
> the same issue that caused Vaio Z laptops to become silent: the speaker pin
> must be connected to the first DAC even though the codec itself advert
At Tue, 12 Feb 2013 16:49:46 +0900,
Fernando Luis Vázquez Cao wrote:
>
> The problem addressed by this fixup is not specific to Vaio Z, affecting
> some Vaio all-in-one desktop PCs too. Update the code comments accordingly.
>
> Cc: sta...@vger.kernel.org
> Cc: alsa-de...@alsa-project.org
> Signed
At Tue, 12 Feb 2013 16:54:16 +0900,
Fernando Luis Vázquez Cao wrote:
>
> Substitute ALC889 for ALC882 in macro and function names.
>
> Cc: sta...@vger.kernel.org
> Cc: alsa-de...@alsa-project.org
> Signed-off-by: Fernando Luis Vazquez Cao
This fixup can work generically to all ALC882 variants,
On 2013-02-11 01:22, Grant Likely wrote:
On Tue, 29 Jan 2013 15:53:42 +0100, Andreas Larsson wrote:
When using a gpio chip select with a OF_GPIO_ACTIVE_LOW flag, this needs to be
known to the controller driver.
Signed-off-by: Andreas Larsson
Out of curiosity, what do you need the flags for?
On Tue, Feb 12, 2013 at 10:20:22AM +0100, Geert Uytterhoeven wrote:
> Hi Heiko,
>
> On Mon, Feb 11, 2013 at 10:11 AM, Heiko Carstens
> wrote:
> > Thanks Geert. A similar patch however is already in linux-next, together
> > with a whole bunch of other patches which try to make s390's allmodconfig
On 2013/02/12 18:27, Takashi Iwai wrote:
At Tue, 12 Feb 2013 16:54:16 +0900,
Fernando Luis Vázquez Cao wrote:
Substitute ALC889 for ALC882 in macro and function names.
Cc: sta...@vger.kernel.org
Cc: alsa-de...@alsa-project.org
Signed-off-by: Fernando Luis Vazquez Cao
This fixup can work gener
On 2013-02-11 01:23, Grant Likely wrote:
On Tue, 29 Jan 2013 15:53:43 +0100, Andreas Larsson wrote:
Holes in the cs-gpios DT phandle list is supposed to mark that native
chipselects is to be used. The value returned from of_get_named_gpio_flags in
this case is -EEXIST. By initializing cs_gpios
Hi,
On Mon, 2013-02-11 at 13:48 -0800, David Rientjes wrote:
> CONFIG_IP_SCTP relies on being able to select things like CONFIG_CRC32C to
> build. Thus, nothing should be selecting CONFIG_IP_SCTP that does not
> meet its requirements.
>
> For example, if CONFIG_EXPERIMENTAL is disabled and CON
* Linus Torvalds wrote:
> On Mon, Feb 11, 2013 at 9:58 AM, Ingo Molnar wrote:
> >
> > So basically Pekka optimistically thought it's an eventual
> > 'tit for tat', a constant stream of benefits to the kernel,
> > in the hope of finding a home in the upstream kernel which
> > would further he
12.02.2013 00:58, J. Bruce Fields пишет:
void svc_close_net(struct svc_serv *serv, struct net *net)
{
- svc_close_list(serv, &serv->sv_tempsocks, net);
- svc_close_list(serv, &serv->sv_permsocks, net);
-
- svc_clear_pools(serv, net);
- /*
-* At this point the
On Mon 11-02-13 17:39:43, Johannes Weiner wrote:
> On Mon, Feb 11, 2013 at 10:27:56PM +0100, Michal Hocko wrote:
> > On Mon 11-02-13 14:58:24, Johannes Weiner wrote:
> > > On Mon, Feb 11, 2013 at 08:29:29PM +0100, Michal Hocko wrote:
> > > > On Mon 11-02-13 12:56:19, Johannes Weiner wrote:
> > > >
I'd like to come back to this topic. I have sent patches last year
already, changes to the last time I posted this is mainly that
I moved the CGEB base support from drivers/mfd/ to arch/x86/platform/
like suggested by Samuel Ortiz back then.
The following series adds support for the Congatec CGEB
This driver provides a I2C bus driver for the CGEB interface
found on some Congatec x86 modules. No devices are registered
on the bus, the user has to do this via the i2c device /sys
interface.
Signed-off-by: Sascha Hauer
---
drivers/i2c/busses/Kconfig |7 ++
drivers/i2c/busses/M
This driver provides support for the CGEB watchdog found on some
Congatec x86 modules.
Signed-off-by: Sascha Hauer
---
drivers/watchdog/Kconfig | 10 ++
drivers/watchdog/Makefile |1 +
drivers/watchdog/congatec_cgeb_watchdog.c | 161 +++
2013/2/12 Benjamin Herrenschmidt :
> On Mon, 2013-02-11 at 16:57 +0100, Michal Simek wrote:
>> But it reminds me that maybe the easiest solution is not to use endian
>> accessors just use two simple macros which should work on all systems.
>>
>> #define _readreg(offset) ({__raw_readl(offse
The Congatec CGEB is a BIOS interface found on some Congatec x86
modules. It provides access to on board peripherals like I2C busses
and watchdogs. This driver contains the basic support for accessing
the CGEB interface and registers the child devices.
Signed-off-by: Sascha Hauer
---
arch/x86/Kc
Hi Linus,
On Mon, Feb 11, 2013 at 02:58:44PM +0100, Linus Walleij wrote:
> On Thu, Dec 20, 2012 at 9:57 AM, Jean-Nicolas Graux
> wrote:
>
> > Provides support for 1801 variant of stmpe gpio port expanders.
> > This chip has 18 gpios configurable as GPI, GPO, keypad matrix,
> > special key or ded
Adding Dmitry to the thread, for the input parts.
On Thu, Dec 20, 2012 at 09:57:19AM +0100, Jean-Nicolas Graux wrote:
> Provides support for 1801 variant of stmpe gpio port expanders.
> This chip has 18 gpios configurable as GPI, GPO, keypad matrix,
> special key or dedicated key function.
>
> No
When interrupts are disabled, an RX condition can occur but
it is not reported when enabling interrupts again. We need to check
RSR and use napi_reschedule() if condition is met.
Signed-off-by: Nicolas Ferre
---
drivers/net/ethernet/cadence/macb.c | 5 +
1 file changed, 5 insertions(+)
diff
Hi Fabio,
On Mon, Feb 11, 2013 at 06:48:00PM -0200, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Fix the following sparse warnings:
>
> drivers/mfd/syscon.c:40:15: warning: symbol 'syscon_node_to_regmap' was not
> declared. Should it be static?
> drivers/mfd/syscon.c:56:15: warning: symbol
Hi Fabio,
On Mon, Feb 11, 2013 at 06:48:01PM -0200, Fabio Estevam wrote:
> From: Fabio Estevam
>
> da9052_i2c_fix() is only used locally, so let it be static.
>
> Fix the following sparse warning:
>
> drivers/mfd/da9052-i2c.c:63:5: warning: symbol 'da9052_i2c_fix' was not
> declared. Should i
On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
> The domain flag SD_PREFER_SIBLING was set both on MC and CPU domain at
> frist commit b5d978e0c7e79a, and was removed uncarefully when clear up
> obsolete power scheduler. Then commit 6956dc568 recover the flag on CPU
> domain only. It works, but
2013/2/11 Arnd Bergmann :
> On Monday 11 February 2013, Michal Simek wrote:
>> Unfortunately no. Another is spi/i2c (sysace as we discuss in this
>> thread), probably icap
>> network drivers are ok because they are not shared.
>> Timer when it is moved to clocksource(not important right now)
>> xil
On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
> It is impossible to miss a task allowed cpu in a eligible group.
I suppose your reasoning goes like: tsk->cpus_allowed is protected by
->pi_lock, we hold this, therefore it cannot change and
find_idlest_group() dtrt?
We can then state that this
On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
> There is 4 situations in the function:
> 1, no task allowed group;
> so min_load = ULONG_MAX, this_load = 0, idlest = NULL
> 2, only local group task allowed;
> so min_load = ULONG_MAX, this_load assigned, idlest = NULL
> 3, only non-
On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
> Guess the search cpu from bottom to up in domain tree come from
> commit 3dbd5342074a1e sched: multilevel sbe sbf, the purpose is
> balancing over tasks on all level domains.
>
> This balancing cost too much if there has many domain/groups in a
* Daniel Borkmann:
> On 02/11/2013 08:00 PM, Florian Weimer wrote:
>> * Daniel Borkmann:
>
> Thanks for your feedback, Florian!
>
>>> + * memcmp_nta - memcmp that is secure against timing attacks
>>
>> It's not providing an ordering, so it should not have "cmp" in the
>> name.
>
> I agree. What wo
On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
> We need initialize the se.avg.{decay_count, load_avg_contrib} to zero
> after a new task forked.
> Otherwise random values of above variables cause mess when do new task
> enqueue:
> enqueue_task_fair
> enqueue_entity
> en
On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
> + /*
> +* set the initial load avg of new task same as its load
> +* in order to avoid brust fork make few cpu too heavier
> +*/
> + if (flags & ENQUEUE_NEWTASK)
> + se->avg.load_avg_contrib = se-
Hi,
We (a cloud hosting provider) has recently observed a couple of
strange lockups when physical node runs significant amount of
Win2008R2 kvm appliances, one may see collection of those lockups at
the link below. After checking a lot of ideas without any valuable
result, I have suggested that ne
On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
> Remove CONFIG_FAIR_GROUP_SCHED that covers the runnable info, then
> we can use runnable load variables.
>
It would be nice if we could quantify the performance hit of doing so.
Haven't yet looked at later patches to see if we remove anything to
Andrew Morton writes:
> On Fri, 08 Feb 2013 12:13:09 -0800
> ebied...@xmission.com (Eric W. Biederman) wrote:
>
>> If mock has called unshare(CLONE_NEWPID). And then forked a process and
>> that process exited, and then forked anothe process that second and all
>> subsequent fork calls will fail
Hi Darren,
On Fri, Feb 08, 2013 at 03:20:36PM -0800, Darren Hart wrote:
> The current probe aborts if any of the 3 base address registers are
> disabled. On a TunnelCreek system I am working on, this resulted in the
> SMBIOS and GPIO devices being removed when it couldn't read the base
> address f
On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
> Current scheduler behavior is just consider the for larger performance
> of system. So it try to spread tasks on more cpu sockets and cpu cores
>
> To adding the consideration of power awareness, the patchset adds
> 2 kinds of scheduler policy:
Hi James,
On Fri, Feb 08, 2013 at 05:33:38PM -0800, James Ralston wrote:
> This patch adds the Watchdog Timer Device IDs for the Intel Wellsburg PCH
>
> Signed-off-by: James Ralston
> ---
> drivers/mfd/lpc_ich.c | 38 ++
> 1 files changed, 38 insertions(+),
On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
>
> The cpu's utilization is to measure how busy is the cpu.
> util = cpu_rq(cpu)->avg.runnable_avg_sum
> / cpu_rq(cpu)->avg.runnable_avg_period;
>
> Since the util is no more than 1, we use its percentage value in later
>
Hello,
I have a few comments on the devicetree binding and the way it's parsed.
> +static const struct of_device_id dbx500_mailbox_match[] = {
> + { .compatible = "stericsson,db8500-mailbox",
> + .data = (void *)db8500_mboxes,
> + },
> + { .compatible = "stericsson
Hi!
> > That's potentially deeadlock-prone, because a task waiting for mutex X may
> > very well be holding mutex Y, so if there's another task waiting for mutex
> > Y,
> > it needs to be frozen at the same time.
> >
> >> The only little detail is how do we implement that...
> >
> > This means th
Ihre Web-Mail-Kontingent hat die eingestellte Quote, die 2 GB ist überschritten.
Sie derzeit auf 2.3GB.To re-aktivieren und zu erhöhen
Ihre Web-Mail-Kontingent bitte überprüfen und aktualisieren Sie Ihre
Web-Mail-Konto in
Um wieder zu aktivieren und steigern Sie Ihren Web-Mail-Kontingent auf den L
On 02/07/13 01:23, Andy King wrote:
Hi,
> +/* Option name for socket's service label. Use as the option name in
> + * setsockopt(3) or getsockopt(3) to set or get the service label for a
> socket.
> + * The service label is a C-style NUL-terminated string. Only available for
> + * hypervisor
When status is DMA_SUCCESS the residue should be zero. Otherwise it's a bug.
Signed-off-by: Andy Shevchenko
Cc: Linus Walleij
Cc: linux-arm-ker...@lists.infradead.org
---
drivers/dma/coh901318.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/coh901318.c b/
It's possible to have an inconsistency in the list due to unprotected operation
on it. The patch adds a proper locking on the list operation.
Signed-off-by: Andy Shevchenko
Acked-by: Rob Herring
---
drivers/of/dma.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/of/dma.c b/dri
This is a patcset of independent fixes of the DMAC drivers. They are simple and
being understandable in their context.
Andy Shevchenko (6):
of: dma: protect list write operation by spin_lock
dmaengine.h: remove redundant else keyword
dma: coh901318_lli: avoid unbalanced locking
dma: coh90
Mitsuhiro Tanino writes:
> Re: [Patch 0/2] Exclude hwpoison page from vmcore dump
> (2012/11/01 19:40), Eric W. Biederman wrote:
>> Mitsuhiro Tanino writes:
>> I agree. If we are performing filtering filtering out of poisoned pages
>> seems very reasonable. So ack on the basic concept.
>>
>>
I have not checked the code but there is a possibility that custom pool->lock
is not needed at all due to dma_pool contains it's own lock.
Signed-off-by: Andy Shevchenko
Cc: Linus Walleij
Cc: linux-arm-ker...@lists.infradead.org
---
drivers/dma/coh901318_lli.c |2 +-
1 file changed, 1 inser
Accordingly to commentary in the platform_device_register_full the memory
allocated for dma_mask will not going to be freed. That's why is better to
assign dma_mask afterwards.
Signed-off-by: Andy Shevchenko
---
drivers/dma/edma.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
d
dmaengine_device_control returns -ENOSYS in case the dma driver doesn't have
such functionality.
Signed-off-by: Andy Shevchenko
---
include/linux/dmaengine.h |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
index bfcde
There is no need to assign 0 to residue, because dma_cookie_status() does this
for us.
Signed-off-by: Andy Shevchenko
---
drivers/dma/tegra20-apb-dma.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/dma/tegra20-apb-dma.c b/drivers/dma/tegra20-apb-dma.c
index 46e4630..fcee27e 10064
On Sun, Feb 10, 2013 at 05:58:14AM +, Len Brown wrote:
> From: Len Brown
>
> pm_idle() on arm64 was a synonym for default_idle(),
> so remove it and invoke default_idle() directly.
>
> Signed-off-by: Len Brown
> Cc: linux-arm-ker...@lists.infradead.org
For arm64:
Acked-by: Catalin Marinas
Hi Mark,
> -Original Message-
> From: Mark Brown [mailto:broo...@opensource.wolfsonmicro.com]
> Sent: Monday, February 11, 2013 10:35 PM
> To: J, KEERTHY
> Cc: linux-kernel@vger.kernel.org; lgirdw...@gmail.com
> Subject: Re: [PATCH V2] Regulator: Reorder the min max assignment in
> the seq
On Tuesday 12 February 2013, Michal Simek wrote:
> > In particular, ARM can run both big- and little-endian even though
> > big-endian is rarely used, so you need to know the endianess for
> > the device you are talking to rather than assume that it knows
> > what the CPU does at the time.
>
> For
On Tuesday 12 February 2013, Benjamin Herrenschmidt wrote:
> It depends how the ARM core operates vs. IO when switched between BE and
> LE, does it keep the same lines doing byte 0 or does it keep the MSB/LSB
> in the same place (and thus changes which lanes contain byte 0) ?
IIRC it changed betwe
>
> just 3 nouveau fixes, all user visible issues, I have one radeon
> regression fix I'm hoping to send tomorrow once I'm happy with it.
Okay I've added the radeon regression fix on top as well
The following changes since commit ff7c60c580d9722f820d85c9c58ca55ecc1ee7c4:
drm/ttm: fix fence loc
On Tue, 2013-02-12 at 17:41 +1100, Michael Ellerman wrote:
> On Mon, Feb 11, 2013 at 09:53:58PM -0500, Peter Hurley wrote:
> > On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
> > > > Can you reproduce after using the following patch series?
> > > > [PATCH v3 00/23] ldisc fixes
> > >
> >
On Tuesday 12 February 2013, Alexander Shiyan wrote:
> > On Monday 11 February 2013, Alexander Shiyan wrote:
> > > The driver can be used in various subsystems and therefore should not
> > > be unloaded when it is defined in the kernel configuration, so remove
> > > support for unloading it.
> > >
From: Manjunath Goudar
Separate the Atmel host controller driver from ehci-hcd host code
into its own driver module.
Signed-off-by: Manjunath Goudar
Cc: Alan Stern
Cc: Greg KH
Cc: Grant Likely
Cc: Rob Herring
Cc: Andrew Victor
Cc: Nicolas Ferre
Cc: Jean-Christophe Plagniol-Villard
Cc: li
On Mon, 2013-02-11 at 15:11 -0500, Vivek Goyal wrote:
> vfs_getxattr_alloc() returns -EOPNOTSUPP if filesystem does not have
> security label enabled. In that case there is no point in continuing
> further and try to fix hashes (if ima_appraise=fix was specified) as
> that will fail too. Return ear
Change it to CONFIG_HAVE_VIRT_TO_BUS and set it in all architecures
that already provide virt_to_bus().
Signed-off-by: Stephen Rothwell
---
arch/Kconfig| 7 +++
arch/alpha/Kconfig | 1 +
arch/arm/Kconfig| 1 +
arch/avr32/Kconfig | 1 +
arch/blackfin/Kconfig |
From: Sjur Brændeland
This driver depends on Rusty's new host virtio ring implementation,
so this patch-set is based on the vringh branch in Rusty's git.
Changes since V1:
- Use the new iov helper functions, and simplify iov handling.
However this triggers compile warnings, as it takes struct
From: Sjur Brændeland
Add functions for creating, deleting and kicking host-side virtio rings.
The host ring is not integrated with virtiqueues and cannot be managed
through virtio-config. Remoteproc must export functions for handling the
host-side virtio rings.
The functions rproc_virtio_get_v
From: Sjur Brændeland
Add helper macro for drivers that don't do anything
special in module init/exit.
Signed-off-by: Sjur Brændeland
---
include/linux/virtio.h |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/include/linux/virtio.h b/include/linux/virtio.h
inde
From: Vikram ARV
Add the the Virtio shared memory driver for STE Modems.
caif_virtio is implemented utilizing the virtio framework
for data transport and is managed with the remoteproc frameworks.
The Virtio queue is used for transmitting data to the modem, and
the new vringh implementation is r
On 12/02/13 11:47, Stephen Rothwell wrote:
> Change it to CONFIG_HAVE_VIRT_TO_BUS and set it in all architecures
nit: typo in "architecures"
> that already provide virt_to_bus().
>
> Signed-off-by: Stephen Rothwell
Reviewed-by: James Hogan
Cheers
James
signature.asc
Description: OpenPGP d
On Mon, Feb 11, 2013 at 3:46 AM, Kumar, Anil wrote:
> As there are no use of #address-cells and #size-cells properties
> in pinctrl-single driver DT node. Fix pinctrl-single binding documentation
> to remove these properties.
>
> Signed-off-by: Kumar, Anil
> ---
> Tested on da850 EVM.
I need To
2013/2/12 Arnd Bergmann :
> On Tuesday 12 February 2013, Michal Simek wrote:
>> > In particular, ARM can run both big- and little-endian even though
>> > big-endian is rarely used, so you need to know the endianess for
>> > the device you are talking to rather than assume that it knows
>> > what th
On Tue, 2013-02-12 at 09:12 +0100, Stanislav Meduna wrote:
> On 12.02.2013 08:06, Mike Galbraith wrote:
>
> >> In this case pick_next_task takes idle tasks and idle wastes cpu
> >> time.
>
> > That's not a waste of CPU time, that's utilization enforcement the thing
> > it is designed to do.
>
>
Add the needed sections to enable audio support and related pin mux on
Devkit8000 when booted with DT blob.
Signed-off-by: Anil Kumar
---
This patch is based on top of kernel 3.8-rc5 and
the following patches.
Peter Ujfalusi:-
ASoC: twl4030: Correct the support for Voice port
ASoC: twl4030: Conv
On Thu 07-02-13 00:02:20, Jan Kara wrote:
> On Tue 05-02-13 20:05:48, Steven Rostedt wrote:
> > [ I sent this in a reply to another thread, but wanted a bit more attention
> > to it ]
> >
> > To prevent deadlocks with doing a printk inside the scheduler,
> > printk_sched() was created. The issue
Most device drivers do not need to perform any postprocessing on the
scatterlists they receive from higher-level drivers (e.g. the block
or SCSI layer), because they translate the request metadata directly
from the various C structs into the data that is required by the device.
virtio devices howe
Move the creation of the request header and response footer to
__virtblk_add_req. vbr->sg only contains the data scatterlist,
the header/footer are added separately using the new piecewise
API for building virtqueue buffers.
With this change, virtio-blk (with use_bio) is not relying anymore on
th
This is similar to the previous patch, but a bit more radical
because the bio and req paths now share the buffer construction
code. Because the req path doesn't use vbr->sg, however, we
need to add a couple of arguments to __virtblk_add_req.
We also need to teach __virtblk_add_req how to build SC
Using the new virtio_scsi_add_sg function lets us simplify the queueing
path. In particular, all data protected by the tgt_lock is just gone
(multiqueue will find a new use for the lock).
The speedup is relatively small (2-4%) but it is worthwhile because of
the code simplification it enables. A
Adding a single direct buffer is a very common case. Introduce
an optimized function for that.
Signed-off-by: Paolo Bonzini
---
drivers/char/hw_random/virtio-rng.c |2 +-
drivers/char/virtio_console.c |4 +-
drivers/net/virtio_net.c|2 +-
drivers/rpmsg/virtio_rpmsg
Eliminate the code duplication between virtqueue_add_buf and
virtqueue_add_sg. That's safe to do now that no devices will
pass scatterlists with a termination marker in the middle.
Signed-off-by: Paolo Bonzini
---
drivers/virtio/virtio_ring.c | 159 +++---
1
Prepare for when virtqueue_add_buf will use sg_next instead of
ignoring ending markers.
Note that for_each_sg (and thus virtqueue_add_sg) allows you
to pass a "truncated" scatterlist that does not have a marker
on the last item. We rely on this in add_recvbuf_mergeable.
Signed-off-by: Paolo Bonz
virtio device drivers translate requests from higher layer in two steps:
a device-specific step in the device driver, and generic preparation
of virtio direct or indirect buffers in virtqueue_add_buf. Because
virtqueue_add_buf also accepts the outcome of the first step as a single
struct scatterli
This is useful in places that recycle the same scatterlist multiple
times, and do not want to incur the cost of sg_init_table every
time in hot paths.
Acked-by: Jens Axboe
Signed-off-by: Paolo Bonzini
---
block/blk-integrity.c |2 +-
block/blk-merge.c |2 +-
include/linu
Right now, both virtblk_add_req and virtblk_add_req_wait call
virtqueue_add_buf. To prepare for the next patches, abstract the call
to virtqueue_add_buf into a new function __virtblk_add_req, and include
the waiting logic directly in virtblk_add_req.
Signed-off-by: Paolo Bonzini
---
drivers/blo
On Mon, Feb 11, 2013 at 6:39 PM, Stephen Warren wrote:
> On 02/11/2013 07:09 AM, Linus Walleij wrote:
>> However if you take this all the way to the descriptor API
>> it will make the consumer (driver) API for GPIO descriptors deviate
>> from what is today used for clocks, regulators and pins.
>>
On Tue, 2013-02-12 at 11:11 +0100, Michal Simek wrote:
> For high performance IPs using accessors functions is still
> problematic
> because there will be performance regression it means that
> from my point of view there still should be any option to "setup"
> proper endians for the driver and it
On Mon, Feb 11, 2013 at 5:50 PM, Max Filippov wrote:
> FWIW I see that the issue is caused by building drivers/gpio/devres.c
> with CONFIG_GPIOLIB=n. Should I just turn GPIO_DEVRES off too?
Hm. Shawn just added:
+config GPIO_DEVRES
+ def_bool y
+ depends on HAS_IOMEM
Can you please
On Mon, Feb 11, 2013 at 9:53 PM, Stephen Warren wrote:
> On 02/10/2013 01:11 PM, Linus Walleij wrote:
>> From: Laurent Meunier
>>
>> This update adds a debugfs interface to modify a pin configuration
>> for a given state in the pinctrl map. This allows to modify the
>> configuration for a non-act
spin_lock(&lp->lock) is used in at86rf230_isr interrupt
handler and in at86rf230_xmit callback to protect
lp->irq_disabled. It seems that deadlock is possible,
because:
at86rf230_xmit
spin_lock(&lp->lock); // acquired
// interrupt
at86rf230_isr
spin_lock(&lp->lock); // deadlock
To prevent it
virtio_scsi_target_state is now empty, but we will find new uses
for it in the next few patches. However, dropping the sglist lets
us turn the array-of-pointers into a simple array, which simplifies
the allocation.
However, we do not leave the virtio_scsi_target_state structs in the
flexible arra
This will be needed soon in order to retrieve the per-target
struct.
Cc: linux-s...@vger.kernel.org
Signed-off-by: Paolo Bonzini
---
drivers/scsi/virtio_scsi.c | 17 +
1 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virti
This patch adds queue steering to virtio-scsi. When a target is sent
multiple requests, we always drive them to the same queue so that FIFO
processing order is kept. However, if a target was idle, we can choose
a queue arbitrarily. In this case the queue is chosen according to the
current VCPU,
Avoid duplicated code in all of the callers.
Cc: linux-s...@vger.kernel.org
Signed-off-by: Paolo Bonzini
---
drivers/scsi/virtio_scsi.c | 22 +-
1 files changed, 9 insertions(+), 13 deletions(-)
diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c
index 3dd
1 - 100 of 715 matches
Mail list logo
