On Wed, 2015-07-22 at 11:41 +1000, Michael Ellerman wrote:
> On Wed, 2015-07-15 at 03:30 -0700, Jeff Kirsher wrote:
> > On Tue, 2015-07-14 at 13:54 +1000, Michael Ellerman wrote:
> > > e1000e_disable_aspm_locked() is only used in __e1000_resume()
> which is
> > > inside CONFIG_PM. So when
debugfs files are not necessary for the usual operation of the driver
and the device. No need to check for the return values from the debugfs
file creation. Even if one debugfs file fails to create we try with the
next debugfs file and ultimately return success always so that the
driver continues
On 2015/07/23 5:22, Tom Zanussi wrote:
> Hi Masami,
>
> On Wed, 2015-07-22 at 17:20 +0900, Masami Hiramatsu wrote:
>> Hi Tom,
>>
>> On 2015/07/17 2:22, Tom Zanussi wrote:
>>> Allow users to append 'pause' or 'continue' to an existing trigger in
>>> order to have it paused or to have a paused
Octavian Purdila writes:
On Fri, Jun 5, 2015 at 4:59 PM, Octavian Purdila
wrote:
Since patch "i2c / ACPI: Use 0 to indicate that device does not have
interrupt assigned" [1], 0 is not a valid i2c client irq anymore, so
change all driver's checks accordingly.
The same issue occurs when the
Hi Jan,
On Thu, Jul 23, 2015 at 3:47 PM, Jan Kara wrote:
> On Thu 23-07-15 13:18:06, Valentin Rothberg wrote:
>> commit 106542e7987c ("fs: Remove ext3 filesystem driver") removed ext3
>> and JBD, hence remove the superfluous condition.
>>
>> Signed-off-by: Valentin Rothberg
>> ---
>> I detected
Em Thu, Jul 23, 2015 at 10:13:22PM +0900, Masami Hiramatsu escreveu:
> On 2015/07/22 23:12, Hemant Kumar wrote:
> > On 07/17/2015 08:51 AM, Masami Hiramatsu wrote:
> >> On 2015/07/16 12:13, Hemant Kumar wrote:
> > The idea behind '%' was to identify the SDT events and take a different path
> > to
On 07/23/2015 09:32 AM, WingMan Kwok wrote:
The CPSW driver keeps internally some, but not all, of
the statistics available in the hw statistics modules. Furthermore,
some of the locations in the hw statistics modules are reserved and
contain no useful information. Prior to this patch, the
On 07/22/2015 04:40 PM, Stephen Smalley wrote:
> On 07/22/2015 04:25 PM, Stephen Smalley wrote:
>> On 07/22/2015 12:14 PM, Seth Forshee wrote:
>>> On Wed, Jul 22, 2015 at 12:02:13PM -0400, Stephen Smalley wrote:
On 07/16/2015 09:23 AM, Stephen Smalley wrote:
> On 07/15/2015 03:46 PM, Seth
Hi Suneel,
On Thu, 2015-07-23 at 04:22PM +0530, Suneel Garapati wrote:
> adds rtc controller node to zynqmp devicetree.
>
> Signed-off-by: Suneel Garapati
> ---
> arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts | 4
> arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 9 +
> 2 files
On Thu 23-07-15 13:18:06, Valentin Rothberg wrote:
> commit 106542e7987c ("fs: Remove ext3 filesystem driver") removed ext3
> and JBD, hence remove the superfluous condition.
>
> Signed-off-by: Valentin Rothberg
> ---
> I detected the issue with undertaker-checkpatch
>
On Fri, 17 Jul 2015, Javier Martinez Canillas wrote:
> The Device Tree binding documentation for the Maxim max77686 regulators
> has been moved from the Multi-Function Device DT binding section to its
> own Documentation/devicetree/bindings/regulator/max77686.txt file.
>
> Use a wilcard so both
On Fri, 17 Jul 2015, Steve Twiss wrote:
> From: Steve Twiss
>
> Fix a missing DVC_RDY interrupt mask in struct regmap_irq definition.
>
> The original submission of this driver did not contain all interrupt
> masking definitions in the struct regmap_irq contained in the file
> da9063-irq.c
>
On 07/23/2015 03:36 PM, Michael Kerrisk (man-pages) wrote:
...
Ok, I guess we could revisit/clarify that at a later point in time. I'd add
a TODO comment to the source or the like, as this also is related to the 2nd
below use case (aggregation/accounting), where an array is typically used.
Hi Daniel,
On 07/23/2015 02:47 PM, Daniel Borkmann wrote:
> On 07/23/2015 01:23 PM, Michael Kerrisk (man-pages) wrote:
> ...
>>> Btw, a user obviously can close() the map fds if he
>>> wants to, but ultimatively they're freed when the program unloads.
>>
>> Okay. (Not sure if you meant that
Different Keystone2 platforms have different number and
layouts of hw statistics modules. This patch consolidates
the statistics processing of different Keystone2 platforms
for easy maintenance.
Signed-off-by: WingMan Kwok
---
drivers/net/ethernet/ti/netcp_ethss.c | 99
This patch fixes error in the setting of the hw statistics
module base for K2HK platform. In K2HK although there are
4 hw statistics modules, but only 2 are visible at a time.
Thus when setting up the pointers to the base of the
corresponding hw statistics modules, modules 0 and 2 should
point to
In certain applications it's beneficial to allow the CPSW h/w
stats counters to continue to increment even while the kernel
polls them. This patch implements this behavior for both 1G
and 10G ethernet subsystem modules.
Signed-off-by: WingMan Kwok
---
drivers/net/ethernet/ti/netcp_ethss.c |
The CPSW driver keeps internally some, but not all, of
the statistics available in the hw statistics modules. Furthermore,
some of the locations in the hw statistics modules are reserved and
contain no useful information. Prior to this patch, the driver
allocates memory of the size of the the
This patch adds the missing statistics for the host
and slave ports of the CPSW on K2L and K2E platforms.
Signed-off-by: WingMan Kwok
---
drivers/net/ethernet/ti/netcp_ethss.c | 177 -
1 file changed, 174 insertions(+), 3 deletions(-)
diff --git
This patch set contains bug fixes and enhencements of hw ethernet
statistics processing on TI's Keystone2 CPSW ethernet switches.
WingMan Kwok (6):
net: netcp: Fixes the use of spin_lock_bh in timer function
net: netcp: Fixes hw statistics module base setting error
net: netcp: Fixes error
This patch fixes a bug in which the timer routine synchronized
against the ethtool-triggered statistics updates with spin_lock_bh().
A timer function is itself a bottom-half, so this should be
spin_lock().
Signed-off-by: WingMan Kwok
---
drivers/net/ethernet/ti/netcp_ethss.c |5 +++--
1
On Thu, Jul 23, 2015 at 3:23 PM, Octavian Purdila
wrote:
> On Thu, Jul 23, 2015 at 4:11 PM, Linus Walleij
> wrote:
>> Me or Torvalds?
>>
>> This looks more like a Wolfram patch to me if it should not
>> go through IIO.
>>
>
> Hi Linus,
>
> This patch fixes one issue introduced by "i2c / ACPI:
Hi Pali,
There are a few reports in psmouse-base.c/alps.c code as well.
Here is a couple of them that are printed one right after another.
The second one tells about a race on ps2dev->cmdcnt.
==
ThreadSanitizer: data-race in
On Mon, 13 Jul 2015, Bjorn Andersson wrote:
> On Tue 07 Jul 05:16 PDT 2015, Lee Jones wrote:
>
> > FAO Mark and DT chaps,
> >
> > > From: Bjorn Andersson
> > >
> > > Add binding documentation for the Qualcomm Resource Power Manager (RPM)
> > > using shared memory (Qualcomm SMD) as transport
On Wed, 22 Jul 2015 11:10:57 -0600
Alex Williamson wrote:
> On Wed, 2015-07-22 at 10:54 -0600, Alex Williamson wrote:
> > On Tue, 2015-07-21 at 19:44 +0200, Gerald Schaefer wrote:
> > > When a user completes the VFIO_SET_IOMMU ioctl and the vfio-pci
> > > device is removed thereafter (before any
On 23/07/2015 at 15:11:47 +0200, Linus Walleij wrote :
> On Thu, Jul 23, 2015 at 12:59 PM, Octavian Purdila
> wrote:
> > On Fri, Jun 5, 2015 at 4:59 PM, Octavian Purdila
> > wrote:
> >> Since patch "i2c / ACPI: Use 0 to indicate that device does not have
> >> interrupt assigned" [1], 0 is not a
Hi Henry,
On Thu, Jul 23, 2015 at 7:04 PM, Henry Chen wrote:
>
> On Thu, 2015-07-23 at 11:07 +0200, Javier Martinez Canillas wrote:
>
> > > +
> > > + if (ret < 0)
> > > + dev_err(>dev, "Failed to initialize regulator:
> > > %d\n", ret);
> > > +
> >
> > I don't think this is
Remove macro and use explicit case statements. Code is a little
longer but clearer. Checkpatch.pl does not complain anymore.
Signed-off-by: Ioan-Adrian Ratiu
---
drivers/staging/rtl8192e/rtllib_rx.c | 80 +++-
1 file changed, 52 insertions(+), 28 deletions(-)
On Thu, Jul 23, 2015 at 4:11 PM, Linus Walleij wrote:
> On Thu, Jul 23, 2015 at 12:59 PM, Octavian Purdila
> wrote:
>> On Fri, Jun 5, 2015 at 4:59 PM, Octavian Purdila
>> wrote:
>>> Since patch "i2c / ACPI: Use 0 to indicate that device does not have
>>> interrupt assigned" [1], 0 is not a
On Mon, 13 Jul 2015, Bjorn Andersson wrote:
> On Tue 07 Jul 05:37 PDT 2015, Lee Jones wrote:
>
> > On Fri, 26 Jun 2015, bj...@kryo.se wrote:
> >
> > > From: Bjorn Andersson
> [..]
>
> > > diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
>
> [..]
>
> > > +config MFD_QCOM_SMD_RPM
> > >
On Thu, Jul 23, 2015 at 11:51:35AM +1000, Dave Chinner wrote:
> On Wed, Jul 22, 2015 at 01:41:00PM -0400, J. Bruce Fields wrote:
> > On Wed, Jul 22, 2015 at 12:52:58PM -0400, Austin S Hemmelgarn wrote:
> > > On 2015-07-22 10:09, J. Bruce Fields wrote:
> > > >On Wed, Jul 22, 2015 at 05:56:40PM
On Thu, Jul 23, 2015 at 10:26:19AM +0100, Marc Zyngier wrote:
> MSI-like interrupts are starting to creep out of the PCI world, and
> can now be seen into a number of "platform"-type busses. The
> introduction of the MSI domains feature in v3.19 recognised that fact,
> and started providing a way
Subject: "PCI/MSI: xgene: Get rid of ..."
On Thu, Jul 23, 2015 at 10:26:37AM +0100, Marc Zyngier wrote:
> The XGene MSI driver only uses the msi_controller structure as
s/XGene/X-Gene/
> a way to match the host bridge with its MSI HW, and thus the
> msi_domain.
>
> But now that we can
On 07/23/2015 01:49 AM, David Rientjes wrote:
> On Wed, 22 Jul 2015, Mike Kravetz wrote:
>
>> On 07/21/2015 05:41 PM, David Rientjes wrote:
>>> munmap(2) will fail with an errno of EINVAL for hugetlb memory if the
>>> length is not a multiple of the underlying page size.
>>>
>>>
On Thu, Jul 23, 2015 at 10:26:26AM +0100, Marc Zyngier wrote:
> Now that we can easily find which MSI domain a PCI device is
> using, use dev_get_msi_domain as a way to retrieve the information.
>
> The original code is still used as a fallback.
>
> Signed-off-by: Marc Zyngier
Acked-by: Bjorn
On Thu, Jul 23, 2015 at 10:26:25AM +0100, Marc Zyngier wrote:
> A number of platforms do not need to use the msi-parent property,
> as the host bridge itself provides the MSI controller.
>
> Allow this configuration by performing an irq domain lookup based
> on the host bridge node if it doesn't
On 2015/07/22 23:12, Hemant Kumar wrote:
> Hi Masami,
>
> Apologies for the delayed response.
>
> On 07/17/2015 08:51 AM, Masami Hiramatsu wrote:
>> Hi Hemant,
>>
>> On 2015/07/16 12:13, Hemant Kumar wrote:
>>> Hi Masami,
>>>
>>> On 07/15/2015 02:43 PM, Masami Hiramatsu wrote:
Hi,
On Thu, Jul 23, 2015 at 10:26:24AM +0100, Marc Zyngier wrote:
> In order to populate the PCI host bridge msi_domain, use the
> "msi-parent" attribute to lookup a corresponding irq domain.
> If found, this is our MSI domain.
>
> This gets plugged into the core PCI code.
>
> Signed-off-by: Marc
On Thu, Jul 23, 2015 at 12:59 PM, Octavian Purdila
wrote:
> On Fri, Jun 5, 2015 at 4:59 PM, Octavian Purdila
> wrote:
>> Since patch "i2c / ACPI: Use 0 to indicate that device does not have
>> interrupt assigned" [1], 0 is not a valid i2c client irq anymore, so
>> change all driver's checks
As the only user of drivers/acpi/gsi.c is now using acpi_set_irq_model
to set acpi_gsi_descriptor_populate to something meaningful, we can
always rely on that information to be present (its absence is an error),
and guarantee that new interrupt controllers will use this API.
Take this opportunity
On Wednesday 22 July 2015 15:14:42 Andrey Konovalov wrote:
> Hi!
>
> We are working on a dynamic data race detector for Linux kernel called
> KernelThreadSanitizer (ktsan) (https://github.com/google/ktsan/wiki).
>
> Here is a report we got while running ktsan (upstream revision
>
Now that the basic ACPI GSI code is irq domain aware, make sure
that the ACPI support in the GIC doesn't pointlessly deviate from
the DT path.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/irq-gic.c | 45 ++---
include/linux/irqchip/arm-gic.h | 2 +-
On 07/23/2015 12:03 AM, David Rientjes wrote:
> On Wed, 22 Jul 2015, Michael Kerrisk (man-pages) wrote:
>
>>> diff --git a/man2/mmap.2 b/man2/mmap.2
>>> --- a/man2/mmap.2
>>> +++ b/man2/mmap.2
>>> @@ -383,6 +383,10 @@ All pages containing a part
>>> of the indicated range are unmapped, and
The struct irq_domain contains a "struct device_node *" field
(of_node) that is almost the only link between the irqdomain
and the device tree infrastructure.
In order to prepare for the removal of that field, convert all
users outside of kernel/irq/irqdomain.c to use an accessor.
Signed-off-by:
Instead of directly passing NULL to the various irq_domain functions,
start by looking up the domain with a domain_token.
As domain_token is permanently set to NULL, the lookup function will
return the same value (no domain found) and the default will be used,
preserving the current behaviour.
Den 14.07.2015 14:59, skrev Henri Chain:
This is a driver chip for 240x160 4-bit greyscale LCDs.
It is capable of 4-wire (8 bit) or 3-wire (9 bit) SPI that have both been
tested. (It also has a 6800 or 8080-style parallel interface, but I have
not included support for it.)
Signed-off-by: Henri
In order to start embrassing irqdomains at the GSI level, introduce
a new initializer:
void acpi_set_irq_model(enum acpi_irq_model_id model,
unsigned long domain_token,
int (*populate)(struct acpi_gsi_descriptor *,
On Thu, Jul 23, 2015 at 10:26:23AM +0100, Marc Zyngier wrote:
> In order to be able to populate the device msi_domain field,
> add the necessary hooks to propagate the host bridge msi_domain
> across secondary busses to devices.
>
> So far, nobody populates the initial msi_domain.
>
>
struct device_node is very much DT specific, and the original authors
of the irqdomain subsystem recognized that tie, and went as far as
mentionning that this could be replaced by some "void *token",
should another firmware infrastructure be using it.
As we move ACPI on arm64 towards this model
Nit: "PCI/MSI" in subject so it matches the rest.
On Thu, Jul 23, 2015 at 10:26:21AM +0100, Marc Zyngier wrote:
> When creating a PCI/MSI domain, tag it with DOMAIN_BUS_PCI_MSI so
> that it can be looked-up using irq_find_matching_host().
>
> Signed-off-by: Marc Zyngier
Acked-by: Bjorn Helgaas
In order to help ACPI on arm64 to make use of most of the irqdomain
goodies, add a new entry point (irq_create_acpi_mapping) which
mimics irq_create_of_mapping, except that it takes a new
struct acpi_gsi_descriptor, which is the pendent of of_phandle_args
in the OF world.
We assume that the way
The irqdomain code is not entierely really ACPI friendly, as it has
some built-in knowledge of the device-tree. Nothing too harmful, but
enough to scare the ARM ACPI developpers which end up with their own
version of the square wheel.
This small patch series adapt the irqdomain code to remove the
On Thu, Jul 23, 2015 at 07:45:53PM +0800, yalin wang wrote:
> A little change to patch_map() function,
> use set_fixmap_offset() to make code more clear.
>
> Signed-off-by: yalin wang
> ---
> arch/arm64/kernel/insn.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git
On Wed, Jul 22, 2015 at 7:33 PM, Alban Bedel wrote:
> Currently CONFIG_ARCH_HAVE_CUSTOM_GPIO_H is defined for all MIPS
> machines, and each machine type provides its own gpio.h. However only
> the Alchemy machine really use the feature, all other machines only
> use the default wrappers.
>
> For
On Wed, 22 Jul 2015 10:54:35 -0600
Alex Williamson wrote:
> On Tue, 2015-07-21 at 19:44 +0200, Gerald Schaefer wrote:
> > When a user completes the VFIO_SET_IOMMU ioctl and the vfio-pci
> > device is removed thereafter (before any other ioctl like
> > VFIO_GROUP_GET_DEVICE_FD), then the
Commit e513229b4c38 ("Drivers: hv: vmbus: prevent cpu offlining on newer
hypervisors") was altering smp_ops.cpu_disable to prevent CPU offlining.
We can bo better by using cpu_hotplug_enable/disable functions instead of
such hard-coding.
Reported-by: Radim Krčmář
Signed-off-by: Vitaly Kuznetsov
Hyper-V module needs to disable cpu hotplug (offlining) as there is no
support from hypervisor side to reassign already opened event channels
to a different CPU. Currently it is been done by altering
smp_ops.cpu_disable but it is hackish.
Signed-off-by: Vitaly Kuznetsov
Reviewed-by: Thomas
As a prerequisite to exporting cpu_hotplug_enable/cpu_hotplug_disable
functions to modules we need to convert cpu_hotplug_disabled to a counter
to properly support disable -> disable -> enable call sequences. E.g.
after Hyper-V vmbus module (which is supposed to be the first user of
exported
Changes since v6:
- Rearrange patches. [Thomas Gleixner]
- Fix a typo in PATCH 2 description [Thomas Gleixner].
- Add Reviewed-by: [Thomas Gleixner].
Changes since v5:
- Split PATCH 1 into two (PATCH 1/3 and 3/3), rewrite changelogs. [Thomas
Gleixner]
Changes since v4:
- In
Hi,
On Sunday 12 July 2015 04:01 PM, Jingoo Han wrote:
> On Friday, July 03, 2015 8:04 PM, Kishon Vijay Abraham I wrote:
>>
>> Certain platforms require MSE bit to be cleared to set the master
>> in standby mode. (In DRA7xx TRM_vE, section 24.9.4.5.2.2.1 PCIe
>
> This patch is a work-around
On Thu, 23 Jul 2015 10:13:11 +0100
Lee Jones wrote:
> On Thu, 23 Jul 2015, Boris Brezillon wrote:
>
> > Hi Lee,
> >
> > On Thu, 23 Jul 2015 08:32:17 +0100
> > Lee Jones wrote:
> >
> > > On Wed, 22 Jul 2015, Cyrille Pitchen wrote:
> > > > + for_each_child_of_node(np, child) {
> > > > +
Regards,
Igal Liberman.
> -Original Message-
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
> Sent: Wednesday, July 22, 2015 7:56 PM
> To: Liberman Igal-B31950
> Cc: net...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org; Wood Scott-B07421;
On 07/23/2015 01:23 PM, Michael Kerrisk (man-pages) wrote:
...
Btw, a user obviously can close() the map fds if he
wants to, but ultimatively they're freed when the program unloads.
Okay. (Not sure if you meant that something should be added to the page.)
I think not necessary.
[...]
Regards,
Igal Liberman.
> +static struct platform_driver fm_driver = {
> + .driver = {
> +.name = "fsl-fman",
> +.of_match_table = fm_match,
> +},
> + .probe = fm_probe,
> +};
> +
> +builtin_platform_driver(fm_driver);
> +
> +static int
On 23/07/2015 at 15:44:25 +0530, Harini Katakam wrote :
> JUMBO and NO_GIGABIT_HALF have the same capability masks.
> Change one of them.
>
> Signed-off-by: Harini Katakam
Acked-by: Alexandre Belloni
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
On 07/23/2015 04:18 AM, Michael Ellerman wrote:
On Mon, 2015-20-07 at 19:01:42 UTC, Tim Gardner wrote:
From: Tim Gardner
drivers/macintosh/ans-lcd.c:201:1: warning: data definition has no type or
storage class
module_init(anslcd_init);
^
drivers/macintosh/ans-lcd.c:201:1: error: type
On Thu, Jul 23, 2015 at 02:48:03AM +0200, Sebastian Reichel wrote:
> Having the !ARCH_MULTIPLATFORM dependency in the Kconfig file results
> in one option less to think about when configuring the kernel.
> -#if defined(CONFIG_ARM_ERRATA_430973) && !defined(CONFIG_ARCH_MULTIPLATFORM)
> +#ifdef
Le 23/07/2015 12:14, Harini Katakam a écrit :
> JUMBO and NO_GIGABIT_HALF have the same capability masks.
> Change one of them.
>
> Signed-off-by: Harini Katakam
Yes, indeed:
Acked-by: Nicolas Ferre
> ---
> drivers/net/ethernet/cadence/macb.h |2 +-
> 1 file changed, 1 insertion(+), 1
>From 0a8e0d63a9887735c6782d7b0c15c2c1fdf1952a Mon Sep 17 00:00:00 2001
From: "Du, Changbin"
Date: Thu, 23 Jul 2015 20:08:04 +0800
Subject: [PATCH] usb/gadget: make composite gadget meet usb compliance for
vbus draw
USB-IF compliance requirement limits the vbus current according to
current
From: Xunlei Pang
cpuidle_device::safe_state_index need to be initialized before use,
so assign the driver's safe_state_index to it.
Signed-off-by: Xunlei Pang
---
drivers/cpuidle/cpuidle.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/cpuidle/cpuidle.c
On Tue, Jul 21, 2015 at 05:08:42PM -0700, David Rientjes wrote:
> On Mon, 20 Jul 2015, Mel Gorman wrote:
>
> > From: Mel Gorman
> >
> > File-backed pages that will be immediately dirtied are balanced between
> > zones but it's unnecessarily expensive. Move consider_zone_balanced into
> > the
The debug_read_tlb() uses the sprintf() functions directly on the buffer
allocated by buf = kmalloc(count), without taking into account the size
of the buffer, with the consequence corrupting the heap, depending on
the count requested by the user.
The patch fixes the issue replacing sprintf() by
On Thu, Jul 23, 2015 at 01:59:33PM +0300, Ioan-Adrian Ratiu wrote:
> Enclose defined macro in paranthesis to avoid checkpatch complaint
> "ERROR: Macros with complex values should be enclosed in parentheses"
>
> Signed-off-by: Ioan-Adrian Ratiu
> ---
> drivers/staging/rtl8192e/rtllib_rx.c | 2
Den 15.07.2015 11:36, skrev Paul Bolle:
On di, 2015-07-14 at 14:59 +0200, Henri Chain wrote:
--- /dev/null
+++ b/drivers/staging/fbtft/fb_uc1611.c
+#define DRVNAME"fb_uc1611"
+MODULE_ALIAS("spi:" DRVNAME);
+MODULE_ALIAS("platform:" DRVNAME);
+MODULE_ALIAS("spi:uc1611");
To make the file more organize move mei client driver api
to the start of the file and add Kdoc.
There are no functional changes in this patch.
Signed-off-by: Tomas Winkler
---
V2: resend
V3: rebase
drivers/misc/mei/bus.c | 799 +++--
1 file changed,
Do not enable events implicitly in mei_cl_enable_device, it should be
done explicitly using mei_cl_register_event_cb so the events
are enabled only when needed.
The NFC drivers has been already using it that way so no need for
further changes just remove the code from mei_cl_enable_device.
Rename mei_cl_uevent to mei_cl_device_uevent to match
the naming convention of mei_cl_bus_type functions
Signed-off-by: Tomas Winkler
---
V2: a new patch in the 2nd series
V3: rebase
drivers/misc/mei/bus.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git
Instead of holding the list of host clients (me_cl)
we want to keep the list me client devices (mei_cl_device)
This way we can create host to me client connection only when needed.
Add list head to mei_cl_device and cl_bus_lock
Add bus_added flag to the me client (mei_me_client) to track if
the
If event registeration has failed, the caller should know
about it.
Signed-off-by: Tomas Winkler
---
V2: fix the commit message
V3: rebase
drivers/misc/mei/bus.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/misc/mei/bus.c b/drivers/misc/mei/bus.c
index
MEI bus was designed around nfc and was hard to extend.
Instead of the hard coded way of adding the devices on the mei bus
we scan the whole me client list and create a device for each
eligible me client (mei_cl_bus_rescan); currently we support
only clients with single connection and fixed
mei_cl_device_match now calls mei_cl_device_find that returns
the matching device id in the device id table.
We will utilize the mei_cl_device_find during probing
to locate the matching entry.
Signed-off-by: Tomas Winkler
---
V2: fix the commit message
V3: rebase
drivers/misc/mei/bus.c | 63
Add reference to the bus device (mei_device) for easier access.
To ensures that referencing cldev->bus is valid during cldev life time
we increase the bus ref counter on a client device creation and drop it
on the device release.
Signed-off-by: Tomas Winkler
---
V2: resend
V3: rebase
Currently we support only clients with single connection
and fixed address clients so all other clients are blacklisted
Signed-off-by: Tomas Winkler
---
V2: a new patch in the 2nd series
V3: rebase
drivers/misc/mei/bus-fixup.c | 19 +++
1 file changed, 19 insertions(+)
diff
Split the device registration into allocation and device struct
initialization, device setup, and the final device registration.
This why it is possible to run fixups and quirks during the setup stage
on an initialized device. Each fixup routine effects do_match flag.
If the flag is set to false
Instead of generating device id on the fly during probing we
find the matching id entry on the device id table.
Get bus the module reference counter so it cannot
be unloaded after the driver has bounded to the client
device
Signed-off-by: Tomas Winkler
---
V2: resend
V3: rebase
Blacklist nfc info client which is only used for retrieval
of the NFC radio version
Signed-off-by: Tomas Winkler
---
V2: a new patch in the 2nd series
V3: rebase
drivers/misc/mei/bus-fixup.c | 23 +++
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git
In the mei bus layer there is use of different variables
of driver and device types with no clear naming convention.
There are generic struct device and struct driver,
then mei_cl_{device, driver}, and finally mei_device which
in this context serves as a bus device.
The patch sets following
Remove the dependency on struct ndev from the nfc device
name creation function so it is possible to use it
in a fixup routine
Signed-off-by: Tomas Winkler
---
V2: fix the commit message
V3: rebase
drivers/misc/mei/bus-fixup.c | 115 ---
The bus-fixup.c will be a place for fixups and quirks
for all types of me client devices.
As for now it contians only the fixup for setting
the nfc device name on the me client bus.
Signed-off-by: Tomas Winkler
---
V2: resend
V3: rebase
drivers/misc/mei/Makefile | 2 +-
MEI bus was designed around nfc and was hard to extend.
Instead of hard coded way of adding the devices on the mei bus
we scan whole me client list and create a device for each
eligible me client
V2: Rephrase the commit message of most of the patches
Remove few patches that didn't bring
On Tue 2015-07-21 09:21:32, Sascha Hauer wrote:
> The thermal code uses int, long and unsigned long for temperatures
> in different places.
>
> Using an unsigned type limits the thermal framework to positive
> temperatures without need. Also several drivers currently will report
> temperatures
On Thu, Jul 23, 2015 at 11:51:49AM +0100, Suneel Garapati wrote:
> adds file for description on device node bindings for RTC
> found on Xilinx Zynq Ultrascale+ MPSoC.
>
> Signed-off-by: Suneel Garapati
> ---
> Documentation/devicetree/bindings/rtc/xlnx-rtc.txt | 25
> ++
>
Hi, Alexi
Thank you for your guidence, and by referencing your last mail
and other llvm backends, I found setting
BPFMCAsmInfo::SupportsDebugInformation = true in BPFMCAsmInfo.h
and fix some unhandeled switch can make llc output debug_info,
but important information is missing in the result:
A little change to patch_map() function,
use set_fixmap_offset() to make code more clear.
Signed-off-by: yalin wang
---
arch/arm64/kernel/insn.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/kernel/insn.c b/arch/arm64/kernel/insn.c
index dd9671c..7dafd5a
On Mon, 2015-07-06 at 15:22 +0300, Andy Shevchenko wrote:
> The new coming Intel platforms such as Skylake will contain
> Sunrisepoint PCH.
>
> The driver is based on MFD framework since the main device, i.e.
> serial bus
> controller, contains register space for itself, DMA part, and an
>
Am 23.07.2015 um 07:09 schrieb Maxime Coquelin:
> This patch replaces use of linux,stdout-path by stdout-path as per
s/by/with/
> "chosen" DT bindings documentation.
>
> Doing that, the "console" argument is no more needed in kernel command
> line.
>
> Reported-by: Olof Johansson
>
23.07.2015 12:43, Oliver Neukum пишет:
On Mon, 2015-07-20 at 21:13 +0300, Eugene Shatokhin wrote:
[Race #5]
Race on dev->rx_urb_size. I reproduced it a similar way as the races
#2
and #3 (changing MTU while downloading files).
dev->rx_urb_size is written to here:
#0 usbnet_change_mtu
Oliver Neukum [mailto:oneu...@suse.com]
[...]
> If the device does not support remote wakeup and the driver enables it,
> runtime
> power management will be switched off.
> That is the current state and it means that devices which don't support remote
> wakeup cannot do runtime power management
> -Original Message-
> From: Alexander Stein [mailto:alexander.st...@systec-electronic.com]
> Sent: Thursday, July 23, 2015 3:41 PM
> To: Badola Nikhil-B46172
> Cc: linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org
> Subject: Re: [PATCH 3/3]
On Thu 23-07-15 19:11:03, Hidehiro Kawai wrote:
> Hi,
>
> Thanks for the feedback.
>
> (2015/07/23 17:25), Michal Hocko wrote:
> > Hi,
> >
> > On Wed 22-07-15 11:14:21, Hidehiro Kawai wrote:
> >> When an HA cluster software or administrator detects non-response
> >> of a host, they issue an NMI
601 - 700 of 1842 matches
Mail list logo
