Il 21/08/2014 13:54, Radim Krčmář ha scritto:
> Guity as charged.
> Using 0/1 or true/false in this context directly would be pretty bad ...
> Is enum fine? (SHIRINK_PLE_WINDOW, GROW_PLE_WINDOW?)
I prefer good old Ctrl-C Ctrl-V (adjusted for your favorite editor). :)
Paolo
--
To unsubscribe from
On 08/20/2014 10:41 PM, Soren Brinkmann wrote:
> Match the naming pattern of all other SMP ops and rename
> zynq_platform_cpu_die --> zynq_cpu_die.
>
> Signed-off-by: Soren Brinkmann
> ---
> arch/arm/mach-zynq/platsmp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On Thu, Aug 14, 2014 at 5:59 PM, Bjorn Andersson
wrote:
> The example in the binding document indicates that interrupt 32 is used
> for the TLMM summary IRQ. Correct this to reduce the confusion.
>
> Signed-off-by: Bjorn Andersson
Patch applied.
Yours,
Linus Walleij
--
To unsubscribe from
Il 21/08/2014 13:38, Radim Krčmář ha scritto:
> 2014-08-21 10:29+0200, Paolo Bonzini:
>> Il 20/08/2014 22:53, Radim Krčmář ha scritto:
>>> Introduce preempt notifiers for architecture specific code.
>>> Advantage over creating a new notifier in every arch is slightly simpler
>>> code and
Add macros to be able to mark string literals used in __init / __exit
functions.
Signed-off-by: Mathias Krause
---
v2: - use a better code example
---
include/linux/init.h | 20
1 file changed, 20 insertions(+)
diff --git a/include/linux/init.h b/include/linux/init.h
Make use of the pi_() helpers to mark the strings printed during
initialization for automatic release. Do so for the strings used in
command line parsing as well, by using the __init_str() macro.
Also convert the remaining printk() calls to their pr_ /
pi_ counterparts.
This moves ~1.7 kB from
The __init_str() / __exit_str() annotations create pseudo symbols.
Ignore them, they have no value for us.
Signed-off-by: Mathias Krause
---
scripts/kallsyms.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/scripts/kallsyms.c b/scripts/kallsyms.c
index
Modpost will detect wrong usage of the pe_*() / pi_*() macros or the
__init_str() / __exit_str() annotations in general. But it'll print
cryptic diagnoses in this case that don't really help fixing the issue
in the code. Detect __init / __exit string section mismatches by there
unique symbol name
On 08/20/2014 10:41 PM, Soren Brinkmann wrote:
> The DDR controller can detect idle periods and leverage low power
> features like self-refresh and clock stop.
> When new requests occur, the DDRC resumes normal operation.
>
> Signed-off-by: Soren Brinkmann
> ---
> arch/arm/mach-zynq/Makefile |
On Fri, Aug 8, 2014 at 6:48 PM, Javier Martinez Canillas
wrote:
> From: Tomasz Figa
>
> Currently after configuring a GPIO pin as an interrupt related pinmux
> registers are changed, but there is no protection from calling
> gpio_direction_*() in a badly written driver, which would cause the
Make use of the pi_() helpers to mark the strings printed during
initialization for automatic release. Do so for the strings used in
command line parsing as well, by using the __init_str() macro.
The debug messages have been converted to printk_init(KERN_DEBUG ...)
instead of pi_debug(...),
Make use of the pi_() helpers to mark the strings printed during
initialization for automatic release. Do so for the strings used in boot
parameters parsing as well, by using the __init_str() macro.
The debug messages have been converted to printk_init(KERN_DEBUG ...)
instead of pi_debug(...),
early_printk() and panic() expect a format string as first argument.
Change early_panic() to pass on the message as string instead of a
format string.
Signed-off-by: Mathias Krause
---
arch/x86/kernel/e820.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Thanks greg TODO was very confusing.
@Lars: These drivers are looks stable enough to move out of staging tree and
Can we move to outside staging tree as per your 1st Comment.
Regards
Sanjeev Sharma
-Original Message-
From: gregkh [mailto:gre...@linuxfoundation.org]
Sent: Wednesday,
Fix build failure caused as follows:
The function chipsfb_pci_init() references
the function __init chips_hw_init().
This is often because chipsfb_pci_init lacks a __init
annotation or the annotation of chips_hw_init is wrong.
make: *** [drivers] Error 2
by removing the __init annotation from
The memory used for functions marked with __init will be released after
initialization, albeit static data referenced by such code will not, if
not explicitly marked this way, too. This is especially true for format
strings used in messages printed by such code. Those are not marked and
therefore
All implementations of x86_init.memory_setup() actually return a const
char *. Adjust the prototypes to reflect reality.
Also add the missing __init annotation to xen_auto_xlated_memory_setup().
Signed-off-by: Mathias Krause
---
arch/x86/include/asm/e820.h |4 ++--
This is v3 of the patch series initially posted here:
https://lkml.org/lkml/2014/6/22/149
This series tries to address the problem of dangling strings of __init
functions after initialization, as well as __exit strings for code not
even included in the final kernel image. The code might get
Adding Greg into CC list.
Sanjeev Sharma
-Original Message-
From: Sanjeev Sharma [mailto:sanjeev_sha...@mentor.com]
Sent: Wednesday, August 20, 2014 3:03 PM
To: ji...@kernel.org; kgene@samsung.com
Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
On 08/20/2014 10:41 PM, Soren Brinkmann wrote:
> Signed-off-by: Soren Brinkmann
> ---
> arch/arm/mach-zynq/common.c | 6 ++
> arch/arm/mach-zynq/common.h | 11 +++
> arch/arm/mach-zynq/platsmp.c | 9 +
> 3 files changed, 26 insertions(+)
>
> diff --git
On Thu, Aug 21, 2014 at 01:17:18PM +0300, Mikko Perttunen wrote:
> this series adds support for the thermal monitoring features of the
> soctherm unit on the Tegra124 SoC.
For all patches in this series:
Reviewed-by: Juha-Matti Tilli
Tested-by: Juha-Matti Tilli
--
To unsubscribe from this
On Thu, 21 Aug 2014, Julia Lawall wrote:
> Convert a zero return value on error to a negative one, as returned
> elsewhere in the function.
>
> Additionally, converted 1 << 7 to BIT(7) at the suggestion of Lee Jones.
>
> A simplified version of the semantic match that finds this problem is as
>
On Wed, 13 Aug 2014, Inha Song wrote:
> Some boards need to set the INn_MODE[1:0] register to change
> the input signal patch. This wlf,inmode property is optional.
> If present values must be specified by the number of
> ARIZONA_MAX_INPUT.
>
> Example:
>- wlf,inmode = <2 0 2 0>; /* IN1,
On Tuesday 19 August 2014, German Rivera wrote:
> >> + * @dev_node: Node in the container's child list
> >
> > Same here: just use the device model's list management instead if you can,
> > or explain why this is needed.
> >
> We still need to keep a per-bus list of child devices (devices
Zhouyi Zhou wrote:
>
> CONFIG_JUMP_LABEL doesn't ensure HAVE_JUMP_LABEL, if it
> is not the case use maintainers's own mutex to guard
> the modification of global values.
I don't understand this patch.
What is the problem you are fixing?
The intent is to only use static_key infrastructure
if
This patch introduces virtual endpoint address mapping. It separates
function logic form physical endpoint addresses making it more hardware
independent.
Following modifications changes user space API, so to enable them user
have to switch on the FUNCTIONFS_VIRTUAL_ADDR flag in descriptors.
This patchset contains changes in FunctionFS making it easier and
safer to use. It fixes bug in endpoint files handling code, adds new
ioctl allowing to obtain endpoint descriptor, and introduces virtual
address mapping which allows to separate endpoint address space in
function from physical
Up to now, when endpoint addresses in descriptors were non-consecutive,
there were created redundant files, which could cause problems in kernel,
when user tryed to read/write to them. It was result of fact that maximum
endpoint address was taken as total number of endpoints in funciton.
This
This patch introduces ioctl named FUNCTIONFS_ENDPOINT_DESC, which
returns endpoint descriptor to userspace. It works only if function
is active.
Signed-off-by: Robert Baldyga
---
drivers/usb/gadget/function/f_fs.c | 21 +
include/uapi/linux/usb/functionfs.h | 6 ++
2
Hi, Rafael,
On Thu, 2014-08-21 at 06:04 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> We generally don't allow ACPI drivers to bind to ACPI device objects
> that companion "physical" device objects are created for to avoid
> situations in which two different drivers may attempt
On 08/19/2014 12:49 AM, Keith Busch wrote:
On Fri, 15 Aug 2014, Matias Bjørling wrote:
* NVMe queues are merged with the tags structure of blk-mq.
I see the driver's queue suspend logic is removed, but I didn't mean to
imply it was safe to do so without replacing it with something else. I
Hi Mark,
On Thu, Aug 21, 2014 at 6:18 AM, Mark Einon wrote:
>
> Hi Fabio, thanks for the review.
>
> It's a space alignment of parameters to go with the previous change, to
> keep wrapping consistent in the file:
>
> - while (i2c_wack) {
> + while (1) {
> if
Convert a zero return value on error to a negative one, as returned
elsewhere in the function.
Additionally, converted 1 << 7 to BIT(7) at the suggestion of Lee Jones.
A simplified version of the semantic match that finds this problem is as
follows: (http://coccinelle.lip6.fr/)
//
(
if@p1
On Thu, Aug 21, 2014 at 12:56:31PM +0100, Lee Jones wrote:
> On Tue, 12 Aug 2014, Charles Keepax wrote:
> > static struct irq_chip arizona_irq_chip = {
> > .name = "arizona",
> > - .irq_disable= arizona_irq_disable,
> > - .irq_enable =
On Wed, 13 Aug 2014, Charles Keepax wrote:
> Mark some additional registers as volatile. The write sequencer control
> registers should not be cached, as we don't ever want their value
> synchronised as this might cause a write sequence to be accidentally
> initiated.
>
> Additionally, the
On Wed, 13 Aug 2014, Charles Keepax wrote:
> From: Mark Brown
>
> During init the core checks if the wm5102 has finished starting by reading
> register 0x19 and looking at the value. This read always fails since this
> is not a readable register, mark it as being one. While we're at it provide
On Tue, 12 Aug 2014, Charles Keepax wrote:
> regmap_add_irq_chip is called from arizona_irq_init with the irq_base
> specified as -1 and regmap_add_irq_chip uses if (irq_base) to check if
> it should use legacy IRQ mapping. As such the irq mappings are currently
> added with
On Tue, 12 Aug 2014, Charles Keepax wrote:
> If one of the internal Arizona IRQs is set as a wake source this needs
> to be propogated back to the actual IRQ line that the Arizona device is
> attached to.
>
> Signed-off-by: Charles Keepax
> ---
> drivers/mfd/arizona-irq.c |8
> 1
On 08/21/2014 01:32 PM, Tomas Henzl wrote:
> On 08/18/2014 08:01 AM, Alexander Gordeev wrote:
>> As result of deprecation of MSI-X/MSI enablement functions
>> pci_enable_msix() and pci_enable_msi_block() all drivers
>> using these two interfaces need to be updated to use the
>> new
2014-08-21 10:29+0200, Paolo Bonzini:
> Il 20/08/2014 22:53, Radim Krčmář ha scritto:
> > Tracepoint for dynamic PLE window, fired on every potential change.
> >
> > Signed-off-by: Radim Krčmář
> > ---
> > arch/x86/kvm/trace.h | 25 +
> > arch/x86/kvm/vmx.c | 8
On Tue, 12 Aug 2014, Charles Keepax wrote:
> We use a dummy IRQ chip to dispatch interrupts to the two seperate IRQ
> domains on the Arizona devices. Currently only the enable and disable
> callbacks are defined however, there are some situations where additional
> callbacks will be used from the
2014-08-21 10:26+0200, Paolo Bonzini:
> Il 20/08/2014 22:53, Radim Krčmář ha scritto:
> > +static int __shrink_ple_window(int val, int shrinker, int minimum)
>
> s/shrinker/factor/ or s/shrinker/param/ (shrinker has another meaning in
> the kernel).
True, thanks.
> > +{
> > + if (shrinker <
Make of_device_id array const, because all OF functions handle it as const.
Signed-off-by: Kiran Padwal
---
drivers/gpu/drm/sti/sti_hda.c |2 +-
drivers/gpu/drm/sti/sti_hdmi.c |2 +-
drivers/gpu/drm/sti/sti_tvout.c |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff
2014-08-21 10:24+0200, Paolo Bonzini:
> Il 20/08/2014 22:53, Radim Krčmář ha scritto:
> > +static void update_ple_window_actual_max(void)
> > +{
> > + ple_window_actual_max =
> > + __shrink_ple_window(max(ple_window_max, ple_window),
>
> Why the max() here?
To have ple_window
Hi Daniel,
On 20/08/14 01:16, Daniel Thompson wrote:
As part of the migration a couple of uart definitions have been copied
from of the platform specific header files.
Note that, in order to keep oldconfig working nicely we must defer the
removal of
This patch fix bug https://bugzilla.kernel.org/show_bug.cgi?id=61411
TPR shadow/threshold feature is important to speed up the Windows guest.
Besides, it is a must feature for certain VMM.
We map virtual APIC page address and TPR threshold from L1 VMCS. If
TPR_BELOW_THRESHOLD VM exit is
Introduce function nested_get_vmcs12_pages() to check the valid
of nested apic access page and virtual apic page earlier.
Signed-off-by: Wanpeng Li
---
v5 -> v6:
* replace the name apic_access_and_virtual_page_valid by
nested_get_vmcs12_pages
arch/x86/kvm/vmx.c | 37
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
This should fix the issue on ehci-exynos, wherein in the absence of
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
This should fix the issue on ohci-exynos, wherein in the absence of
2014-08-21 10:25+0200, Paolo Bonzini:
> Il 20/08/2014 22:53, Radim Krčmář ha scritto:
> > + if (ple_gap)
> > + vmcs_write32(PLE_WINDOW, vmx->ple_window);
>
> Maybe we can add a ple_window_dirty field? It can be tested instead of
> ple_gap to avoid the vmwrite in the common case?
Reduce few code lines by using wrappers for sending
simple hbm client messages
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/hbm.c | 51 +-
1 file changed, 25 insertions(+), 26 deletions(-)
diff --git a/drivers/misc/mei/hbm.c
2014-08-21 10:29+0200, Paolo Bonzini:
> Il 20/08/2014 22:53, Radim Krčmář ha scritto:
> > Introduce preempt notifiers for architecture specific code.
> > Advantage over creating a new notifier in every arch is slightly simpler
> > code and guaranteed call order with respect to kvm_sched_in.
> >
>
To support dynamic addition/remove of clients
it is more convenient to use list instead of
static array
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/client.c | 34 ++---
drivers/misc/mei/debugfs.c | 19
drivers/misc/mei/hbm.c | 116
In order to support dynamic addition/removal of me clients we cannot
It is incontinent to use static array and we can use list.
As the first step we change the lookup function to return
me client address instead of the index.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/amthif.c | 29
On 08/18/2014 08:01 AM, Alexander Gordeev wrote:
> Signed-off-by: Alexander Gordeev
> Cc: Anil Ravindranath
> Cc: linux-s...@vger.kernel.org
> Cc: linux-...@vger.kernel.org
> ---
> drivers/scsi/pmcraid.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/scsi/pmcraid.c
This makes to_phy() macro work with other variable names
besides "dev".
Signed-off-by: Heikki Krogerus
Tested-by: Vivek Gautam
---
include/linux/phy/phy.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
index
On 08/18/2014 08:01 AM, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() or pci_enable_msi_exact()
> and
Hi,
So the idea with these is that they should help to make it possible to
request phys without caring about how they are mapped to the
consumers, meaning, was is the mapping done in DT, ACPI, etc. Mapping
phys to consumers can be now done with lookups similarly how clocks
can be mapped in
The device name is needed when assigning resources like
clocks or GPIOs to devices using lookups. If
PLATFORM_DEVICE_AUTO is used, the device name is not know
before platform_device_add is called after which it's too
late to assign that kind of resources as the drivers most
likely have already
Provide complete association for the phy and it's user
(musb) with the new phy lookup method.
Signed-off-by: Heikki Krogerus
---
arch/arm/mach-omap2/twl-common.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/arch/arm/mach-omap2/twl-common.c
When handling dynamic clients there might be a race
scenario in which two me clients with the same me
address would be linked in the me clients list,
therefore we need to search by both uuid and me address.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/amthif.c | 1 +
Removes the need for the phys to be aware of their users
even when not using DT. The method is copied from clkdev.c.
Signed-off-by: Heikki Krogerus
Tested-by: Vivek Gautam
---
Documentation/phy.txt | 66 ---
drivers/phy/phy-core.c | 135
The users of the old method are now converted to the new one.
Signed-off-by: Heikki Krogerus
Tested-by: Vivek Gautam
---
drivers/phy/phy-bcm-kona-usb2.c | 2 +-
drivers/phy/phy-core.c | 45 +++--
drivers/phy/phy-exynos-dp-video.c | 2 +-
On some platforms a PHY may need to be handled also in the
host controller driver. Exynos5420 SoC requires some "PHY
tuning" based on the USB speed. This patch delivers dwc3's
PHYs to the xhci platform device when it's created.
Signed-off-by: Heikki Krogerus
Tested-by: Vivek Gautam
Acked-by:
To support dynamic addition/remove we add wrappers
for removal of me clients
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/client.c | 22 +-
drivers/misc/mei/client.h | 2 ++
drivers/misc/mei/hbm.c| 21 +++--
3 files changed, 38 insertions(+), 7
HBM uses global list of status values
from which the values of particular commands
are derived
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/hbm.c | 22 --
drivers/misc/mei/hw.h | 39 +--
2 files changed, 53 insertions(+), 8
On 08/18/2014 08:01 AM, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() or pci_enable_msi_exact()
> and
Both responses have same flow only the client status
update is different. We introduce handler mei_hbm_cl_res()
that handles both responses
Also we use per client wait queue (cl->wait) rather then
global dev->wait_recvd_msg
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/client.c | 4 +-
Am 21.08.2014 10:41, schrieb Michal Simek:
> On 08/20/2014 05:56 PM, Soren Brinkmann wrote:
>> Add missing Ethernet phys to Zynq DTs.
>>
>> Signed-off-by: Soren Brinkmann
>> ---
>> arch/arm/boot/dts/zynq-zc702.dts | 6 ++
>> arch/arm/boot/dts/zynq-zc706.dts | 6 ++
>>
Make of_device_id array const, because all OF functions handle it as const.
Signed-off-by: Kiran Padwal
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c|4 ++--
drivers/gpu/drm/tilcdc/tilcdc_panel.c |4 ++--
drivers/gpu/drm/tilcdc/tilcdc_slave.c |4 ++--
Rename mei_cl_irq_close to mei_cl_irq_disconnect
and MEI_FOP_CLOSE to MEI_FOP_DISCONNECT
Remove unused MEI_FOP_OPEN
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/client.c| 3 ++-
drivers/misc/mei/interrupt.c | 8
drivers/misc/mei/mei_dev.h | 6 ++
3 files changed, 8
extract supported hbm features and commands from the hbm version
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/hbm.c | 25 -
drivers/misc/mei/hw-me.c | 6 +-
drivers/misc/mei/mei_dev.h | 4
3 files changed, 29 insertions(+), 6 deletions(-)
diff
There is no need for dynamic allocation for connect_data.
We can use variable on the stack and make code less
error prone and simple
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/main.c | 21 +
1 file changed, 5 insertions(+), 16 deletions(-)
diff --git
Add mei_hbm_cl_find_by_cmd handler to retrieve
the destination client
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/hbm.c | 74 +-
1 file changed, 43 insertions(+), 31 deletions(-)
diff --git a/drivers/misc/mei/hbm.c b/drivers/misc/mei/hbm.c
Handle ioctls in a switch statement so we can
add more commands easily
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/main.c | 53 ++---
1 file changed, 28 insertions(+), 25 deletions(-)
diff --git a/drivers/misc/mei/main.c
From: Alexander Usyskin
We cannot handle user interrupt in context of hbm start
so we only wait for time out which is reasonably short.
1. Add kdoc
2. Rename state to better reflect its function
3. Simplify wait condition and rename
wait_recvd_msg to wait_hbm_start
Signed-off-by: Alexander
On Wed, 13 Aug 2014, Andreas Werner wrote:
> The MEN 14F021P00 Board Management Controller provides an
> I2C interface to the host to access the feature implemented in the BMC.
> The BMC is a PIC Microntroller assembled on CPCI Card from MEN Mikroelektronik
> and on a few Box/Display Computer.
>
Use consistently me_addr name in hbm protocol structures
to represent in firmware client address
Signed-off-by: Tomas Winkler
Signed-off-by: Alexander Usyskin
---
drivers/misc/mei/hbm.c | 6 +++---
drivers/misc/mei/hw.h | 5 ++---
2 files changed, 5 insertions(+), 6 deletions(-)
diff --git
At Wed, 20 Aug 2014 09:05:58 +0200,
Takashi Iwai wrote:
>
> > > > > Also, I'm left wondering why e.g. my Athlon XP system (a very popular
> > > > > choice for longer times) would be affected by Cpufreq...
> > > > > And there are no details on how exactly cpufreq is a problem or how
> > > > >
I think you should cc also linuxppc-dev as it touches common code.
On 08/04/2014 12:45 PM, Jingchang Lu wrote:
Signed-off-by: Jingchang Lu
---
drivers/clk/Kconfig | 7 ---
drivers/clk/clk-ppc-corenet.c | 5 +
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git
Hi,
I'm afraid this patch, in its current form, will not work.
See below for additional comments.
> -Original Message-
> From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
> ow...@vger.kernel.org] On Behalf Of Shawn Bohrer
> Sent: Thursday, August 21, 2014 2:23 AM
> To: Roland
On Thu, 21 Aug 2014, Mika Westerberg wrote:
> From: Alan Cox
>
> This is the same as used in Baytrail so add the new PCI ID to the driver's
> list of supported IDs.
>
> Signed-off-by: Alan Cox
> Signed-off-by: Mika Westerberg
> ---
> Changed the PCI ID to be in lower case letters.
>
>
Hi
On Thu, Aug 21, 2014 at 12:59 PM, Sudeep Holla wrote:
> From: Sudeep Holla
>
> This patch creates a new class called "cpu" and assigns it to all the
> cpu devices. This helps in grouping all the cpu devices and associated
> child devices under the same class.
>
> This patch also:
> 1.
On Thu, 21 Aug 2014, Thierry Reding wrote:
> On Thu, Aug 21, 2014 at 10:45:02AM +0100, Lee Jones wrote:
> [...]
> > > diff --git a/drivers/mfd/sky81452.c b/drivers/mfd/sky81452.c
> [...]
> > > + * This program is free software; you can redistribute it and/or modify
> > > it
> > > + * under the
On 08/18/2014 08:01 AM, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() or pci_enable_msi_exact()
> and
On 08/18/2014 08:01 AM, Alexander Gordeev wrote:
> There is no need to call pci_disable_msix() in case
> the previous call to pci_enable_msix() failed
Patch looks good to me.
Reviewed-by: Tomas Henzl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Hi,
Am 20.08.2014 19:11, schrieb mathieu.poir...@linaro.org:
> From: Pratik Patel
>
> Coresight IP blocks allow for the support of HW assisted tracing
> on ARM SoCs. Bindings for the currently available blocks are
> presented herein.
>
> Signed-off-by: Pratik Patel
> Signed-off-by:
On Wed, 20 Aug 2014, Valdis Kletnieks wrote:
> Both the original and the first attempted patch managed to get the logic
> wrong.
> So we fix it so we only continue if sscanf returns exactly one value, and it
> has to be either 1 or 2. Apparently, programmers are getting out and hacking
> code
On 08/18/2014 08:01 AM, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() and pci_enable_msix_range()
> interfaces.
From: Xiang Wang
There might be such calling sequence for dma channel:
1. register dma device
dma_async_device_register
-> if (dma_has_cap(DMA_PRIVATE, device->cap_mask))
device->privatecnt++;
2. request channel
dma_request_slave_channel
-> of_dma_request_slave_channel
->
From: Sudeep Holla
This patch creates a new class called "cpu" and assigns it to all the
cpu devices. This helps in grouping all the cpu devices and associated
child devices under the same class.
This patch also:
1. modifies the get_parent_device to return the legacy path
From: Sudeep Holla
Many sysfs *_show use cpu{list,mask}_scnprintf to copy cpumap to the
buffer aligned to PAGE_SIZE, append '\n' and '\0' to return null
terminated buffer with newline.
This patch creates a new helper function cpumap_copy_to_buf in
cpumask.h and consolidates most of them using
From: Sudeep Holla
This patch adds initial support for providing processor cache information
to userspace through sysfs interface. This is based on already existing
implementations(x86, ia64, s390 and powerpc) and hence the interface is
intended to be fully compatible.
The main purpose of this
From: Sudeep Holla
This patch removes the redundant sysfs cacheinfo code by making use of
the newly introduced generic cacheinfo infrastructure.
Signed-off-by: Sudeep Holla
Cc: Tony Luck
Cc: Fenghua Yu
Cc: linux-i...@vger.kernel.org
---
arch/ia64/kernel/topology.c | 421
From: Sudeep Holla
This patch removes the redundant sysfs cacheinfo code by making use of
the newly introduced generic cacheinfo infrastructure.
Signed-off-by: Sudeep Holla
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: linuxppc-...@lists.ozlabs.org
---
arch/powerpc/kernel/cacheinfo.c |
On 08/15/2014 11:07 PM, Tony Lindgren wrote:
> Nice, now it mostly works for me with off-idle too :) That is as long
> as I have the DMA channels commented out in the .dts file.
>
> And I'm still seeing an occasional hang with pstore console just
> showing:
>
> [ 289.076538] In-band Error seen
From: Sudeep Holla
In order to support outer cache in the cacheinfo infrastructure, a new
function 'get_info' is added to outer_cache_fns. This function is used
to get the outer cache information namely: line size, number of ways of
associativity and number of sets.
This patch adds 'get_info'
From: Sudeep Holla
This series adds a generic cacheinfo support similar to topology. The
implementation is based on x86 cacheinfo support. Currently x86, powerpc,
ia64 and s390 have their own implementations. While adding similar support
to ARM and ARM64, here is the attempt to make it generic
From: Sudeep Holla
This patch removes the redundant sysfs cacheinfo code by making use of
the newly introduced generic cacheinfo infrastructure.
Signed-off-by: Sudeep Holla
Cc: Martin Schwidefsky
Cc: Heiko Carstens
Cc: linux...@de.ibm.com
Cc: linux-s...@vger.kernel.org
---
From: Sudeep Holla
This patch adds support for cacheinfo on ARM64.
On ARMv8, the cache hierarchy can be identified through Cache Level ID
(CLIDR) register while the cache geometry is provided by Cache Size ID
(CCSIDR) register.
Since the architecture doesn't provide any way of detecting the
501 - 600 of 1478 matches
Mail list logo
