Hi,
A few comments, mostly about style.
On 20/06/2016 at 10:52:14 +0800, Chen-Yu Tsai wrote :
> +struct ac100_rtc_dev {
> + struct rtc_device *rtc;
> + struct device *dev;
> + struct regmap *regmap;
> + struct mutex mutex;
I don't think that mutex is needed. Instead, you can take
On Saturday, June 25, 2016 06:49:09 AM Linus Torvalds wrote:
> On Sat, Jun 25, 2016 at 1:25 AM, Thomas Gleixner wrote:
> >
> > please pull the latest x86-urgent-for-linus git tree from:
>
> Nope.
>
> > This update contains:
> >
> > - The final fix for the hibernation resume path which addresse
On 20/06/2016 at 10:52:15 +0800, Chen-Yu Tsai wrote :
> +struct ac100_clk32k {
> + struct clk_hw hw;
> + struct regmap *regmap;
> + u8 offset;
> +};
> +
> +#define to_ac100_clk32k(_hw) container_of(_hw, struct ac100_clk32k, hw)
> +
> +#define AC100_RTC_32K_NAME "ac100-rtc-32k"
> +#def
On 20/06/2016 at 10:52:14 +0800, Chen-Yu Tsai wrote :
> +static int ac100_rtc_probe(struct platform_device *pdev)
> +{
> + struct ac100_dev *ac100 = dev_get_drvdata(pdev->dev.parent);
> + struct ac100_rtc_dev *chip;
> + int ret;
> +
> + chip = devm_kzalloc(&pdev->dev, sizeof(*chip),
On Fri, Jun 24, 2016 at 04:20:32PM +0200, Michal Suchanek wrote:
> The check is supposed to warn about spidev specified directly in
> devicetree as compatible. This just does not work. I have a devicetree
> with no compatible whatsoever and hacked my kernel so I can manually
> bind spidev. This st
On Thu, Jun 23, 2016 at 05:41:19PM -, Michal Suchanek wrote:
> The check is supposed to warn about spidev specified directly in
> devicetree as compatible. This just does not work. I have a devicetree
> with no compatible whatsoever and hacked my kernel so I can manually
> bind spidev. This st
On Thu, Jun 23, 2016 at 05:41:20PM -, Michal Suchanek wrote:
> SPI slave devices are not created when looking up driver for the slave
> fails. Create a device anyway so it can be manually bound to a driver.
> @@ -1543,11 +1542,10 @@ of_register_spi_device(struct spi_master *master,
> struct d
Only register power off if the PMIC is defined as system power
controller (see Documentation/devicetree/bindings/power/
power-controller.txt).
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
---
drivers/mfd/rn5t618.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
dif
This patchset adds RN5T567 PMIC support which is used on the
Toradex Colibri iMX7S/iMX7D modules. The existing RN5T618 is from
the same family, hence this patchset uses the same driver and adds
variant support.
The Colibris currently do not use the PMIC's power off capabilities,
as do the current
Extend the driver to support Ricoh RN5T567. Support the additional
DCDC and slightly different voltage range of LDORTC1.
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Mark Brown
Acked-by: Lee Jones
---
drivers/regulator/Kconfig | 5 +++--
drivers/regulator/rn
The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is,
the differences are:
+ DCDC4
+ Slightly different output voltage/currents
+ 32kHz Output
- ADC/Charger capabilities
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Rob Herring
---
Documentation/devicetree/bi
The PMIC driver used to register itself as poweroff controller by
default, hence assuming that this device is using the PMIC as
system power controller.
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
---
arch/arm/boot/dts/meson8-minix-neo-x8.dts | 1 +
1 file changed, 1 insertion(+)
Use the PMIC's repower capability for reboots. Register a restart
handler and use a slightly elevated priority of 192 since the PMIC
has suprior reset capability (causing a system wide reset).
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
---
drivers/mfd/rn5t618.c | 42 ++
Hi,
> -Original Message-
> From: Pavel Machek [mailto:pa...@ucw.cz]
> Sent: Sunday, June 26, 2016 12:51 AM
> To: Chen, Yu C
> Cc: linux...@vger.kernel.org; x...@kernel.org; Rafael J. Wysocki; Len Brown;
> Peter Zijlstra; H. Peter Anvin; Borislav Petkov; Brian Gerst; Thomas Gleixner;
> Ingo
On Thu, Jun 23, 2016 at 05:41:20PM -, Michal Suchanek wrote:
> This allows binding spidev on any slave device by hand using sysfs
> without adding superfluous compatibles or any other needless
> complication.
This says "spidev" but it's a change to the driver core, not something
that is speci
Hi,
> -Original Message-
> From: Pavel Machek [mailto:pa...@ucw.cz]
> Sent: Sunday, June 26, 2016 12:52 AM
> To: Chen, Yu C
> Cc: linux...@vger.kernel.org; x...@kernel.org; Rafael J. Wysocki; Len Brown;
> Peter Zijlstra; H. Peter Anvin; Borislav Petkov; Brian Gerst; Thomas Gleixner;
> In
Hi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: da2f6aba4a21f8da3331e5251a117c52764da579
commit: 5d2acfc7b974bbd3858b4dd3f2cdc6362dd8843a kconfig: make allnoconfig
disable options behind EMBEDDED and EXPERT
date
On Sat, Jun 25, 2016 at 4:30 PM, Andy Lutomirski wrote:
>
> Maybe I'm misunderstanding the role of release_task. It looks like
> there's this path in the scheduler I can borrow:
>
> if (unlikely(prev_state == TASK_DEAD)) {
>
> With a kludge in place to free the stack in there and release_task
Hi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: da2f6aba4a21f8da3331e5251a117c52764da579
commit: abec1a806e0c3cf168999667d5fb6218398ef12a percpu: Make __verify_pcu_ptr
handle per cpu pointers to arrays
date: 2
Hi,
> -Original Message-
> From: Pavel Machek [mailto:pa...@ucw.cz]
> Sent: Sunday, June 26, 2016 12:53 AM
> To: Chen, Yu C
> Cc: linux...@vger.kernel.org; x...@kernel.org; Rafael J. Wysocki; Len Brown;
> Peter Zijlstra; H. Peter Anvin; Borislav Petkov; Brian Gerst; Thomas Gleixner;
> Ingo
Hi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: da2f6aba4a21f8da3331e5251a117c52764da579
commit: ea8daa7b97842aab8507b5b5b1e3226cf2d514a6 kbuild: Add option to turn
incompatible pointer check into error
date:
On 26 June 2016 at 03:09, Mark Brown wrote:
> On Fri, Jun 24, 2016 at 04:20:32PM +0200, Michal Suchanek wrote:
>
>> The check is supposed to warn about spidev specified directly in
>> devicetree as compatible. This just does not work. I have a devicetree
>> with no compatible whatsoever and hacked
On 26 June 2016 at 03:13, Mark Brown wrote:
> On Thu, Jun 23, 2016 at 05:41:19PM -, Michal Suchanek wrote:
>
>> The check is supposed to warn about spidev specified directly in
>> devicetree as compatible. This just does not work. I have a devicetree
>> with no compatible whatsoever and hacked
On Sat, Jun 25, 2016 at 09:20:25PM +0200, Peter Zijlstra wrote:
> On Sun, Jun 26, 2016 at 01:27:56AM +0800, panxinhui wrote:
> > >> Would that not have issues where the owner cpu is kept running but the
> > >> spinner (ie. _this_ vcpu) gets preempted? I would think that in that
> > >> case we too w
On 26 June 2016 at 03:15, Mark Brown wrote:
> On Thu, Jun 23, 2016 at 05:41:20PM -, Michal Suchanek wrote:
>> SPI slave devices are not created when looking up driver for the slave
>> fails. Create a device anyway so it can be manually bound to a driver.
>
>> @@ -1543,11 +1542,10 @@ of_registe
By registering a cleanup function with devm_add_action(), we can
simplify the error path in the probe function and drop the remove
function entirely.
Signed-off-by: Guenter Roeck
---
v2: No change
drivers/hwmon/tmp102.c | 54 ++
1 file changed, 19
So far the chip was forced into polarity 0, even if it was preconfigured
differently. Do not touch the polarity when configuring the chip.
Also, the configuration register was read beack to check if the
configuration 'sticks'. Ultimately, that is similar to checking if the
chip is a tmp102 in the
The FSF address can change, so drop it from the driver.
Signed-off-by: Guenter Roeck
---
v2: No change
drivers/hwmon/tmp102.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/hwmon/tmp102.c b/drivers/hwmon/tmp102.c
index befd06b6f3a5..5bdf262e6a0e 100644
--- a/drivers/hwmon/tmp102
By concerting the driver to regmap, we can use regmap to cache non-volatile
registers. Stop caching the temperature register; while potentially reading
it more often can result in reading it more often than necessary, this is
offset by the gain due to not re-reading the limit registers.
Cc: Mark B
If the chip was in shutdown mode when the driver was loaded, the first
conversion is ready no more than 35 milli-seconds after the chip was
taken out of shutdown. The driver delay was so far set to 333 ms (HZ / 3),
which is much higher than the maximum time needed by the chip.
Reduce the time to 3
None of these files have anything modular in them, so they
don't need to be bringing in module.h and all its dependencies.
Cc: Linus Walleij
Cc: linux-g...@vger.kernel.org
Signed-off-by: Paul Gortmaker
---
drivers/pinctrl/freescale/pinctrl-imx.c | 1 -
drivers/pinctrl/freescale/pinctrl-im
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_MXS
drivers/pinctrl/freescale/Kconfig: bool
...meaning that it currently is not being built as a module by anyone.
It also doesn't have any modular functionality, so it doesn't ne
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX23
drivers/pinctrl/freescale/Kconfig: bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX35
drivers/pinctrl/freescale/Kconfig: bool "IMX35 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is es
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX7D
drivers/pinctrl/freescale/Kconfig: bool "IMX7D pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is es
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6Q
drivers/pinctrl/freescale/Kconfig: bool "IMX6Q/DL pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6SL
drivers/pinctrl/freescale/Kconfig: bool "IMX6SL pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
This series covers the audit of non-modular module code use in the
drivers/pinctrl/freescale directory. It has a few more commits than
I'd normally like in a single series, but fortunately the most of them
are dead simple. That said, I can put the branch on kernel.org if
that makes life easier fo
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX1
drivers/pinctrl/freescale/Kconfig: bool "IMX1 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is esse
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX53
drivers/pinctrl/freescale/Kconfig: bool "IMX53 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is es
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6Q
drivers/pinctrl/freescale/Kconfig: bool "IMX6Q/DL pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6SX
drivers/pinctrl/freescale/Kconfig: bool "IMX6SX pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX51
drivers/pinctrl/freescale/Kconfig: bool "IMX51 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is es
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX28
drivers/pinctrl/freescale/Kconfig: bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX21
drivers/pinctrl/freescale/Kconfig: bool "i.MX21 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is e
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6UL
drivers/pinctrl/freescale/Kconfig: bool "IMX6UL pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX50
drivers/pinctrl/freescale/Kconfig: bool "IMX50 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is es
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX27
drivers/pinctrl/freescale/Kconfig: bool "IMX27 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is es
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_VF610
drivers/pinctrl/freescale/Kconfig: bool "Freescale Vybrid VF610 pinctrl
driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modul
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX25
drivers/pinctrl/freescale/Kconfig:bool "IMX25 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
Hi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: da2f6aba4a21f8da3331e5251a117c52764da579
commit: 3194c6870158e305dac2af52f83681e9cb67280f NFC: nfcmrvl: add firmware
download support
date: 8 months ago
config:
Hi,
[auto build test WARNING on tip/sched/core]
[also build test WARNING on next-20160624]
[cannot apply to v4.7-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/riel-redhat-com/sched-time-fi
Now that we have a proper binding for Ethernet switches hanging off
different buses, and a driver for the BCM53125 switch, add its Device
Tree as a child MDIO node, at MDIO address 30 (Broadcom pseudo-PHY
address) and describe the ports layout of the Lamobo R1 board.
This switch is hanging off the
Up to now, each hwmon driver has to implement its own sysfs attributes.
This requires a lot of template code, and distracts from the driver's
core function to read and write chip registers.
To be able to reduce driver complexity, move sensor attribute handling
and thermal zone registration into th
Signed-off-by: Guenter Roeck
---
drivers/hwmon/hwmon.c | 16
include/linux/hwmon.h | 27 +++
2 files changed, 43 insertions(+)
diff --git a/drivers/hwmon/hwmon.c b/drivers/hwmon/hwmon.c
index 363ec5660d0c..ca18a6f4f9bc 100644
--- a/drivers/hwmon/hwmon.c
+
Signed-off-by: Guenter Roeck
---
drivers/hwmon/hwmon.c | 30
include/linux/hwmon.h | 54 +++
2 files changed, 84 insertions(+)
diff --git a/drivers/hwmon/hwmon.c b/drivers/hwmon/hwmon.c
index 8c3c7ffe828b..dff07e8f9509
Signed-off-by: Guenter Roeck
---
drivers/hwmon/hwmon.c | 20
include/linux/hwmon.h | 29 +
2 files changed, 49 insertions(+)
diff --git a/drivers/hwmon/hwmon.c b/drivers/hwmon/hwmon.c
index dff07e8f9509..363ec5660d0c 100644
--- a/drivers/hwmon/hwm
Describe the new registration API function as well as the data
structures it requires.
Signed-off-by: Guenter Roeck
---
Documentation/hwmon/hwmon-kernel-api.txt | 229 ++-
1 file changed, 227 insertions(+), 2 deletions(-)
diff --git a/Documentation/hwmon/hwmon-kernel
Signed-off-by: Guenter Roeck
---
drivers/hwmon/hwmon.c | 21 +
include/linux/hwmon.h | 36
2 files changed, 57 insertions(+)
diff --git a/drivers/hwmon/hwmon.c b/drivers/hwmon/hwmon.c
index d2916074befd..8c3c7ffe828b 100644
--- a/drivers/h
Signed-off-by: Guenter Roeck
---
drivers/hwmon/hwmon.c | 21 +
include/linux/hwmon.h | 35 +++
2 files changed, 56 insertions(+)
diff --git a/drivers/hwmon/hwmon.c b/drivers/hwmon/hwmon.c
index 9530644ae297..d2916074befd 100644
--- a/drivers/hw
Up to now, each hwmon driver has to implement its own sysfs attributes.
This requires a lot of template code, and distracts from the driver's core
function to read and write chip registers.
To be able to reduce driver complexity, move sensor attribute handling
and thermal zone registration into hw
Hi,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.7-rc4 next-20160624]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Marcel-Ziswiler/arm-tegra-initial-support-for-apalis
v5: Remove #ifdef CONFIG_X86 from setup-bus.c, making it neutral to archs.
v4: Add comments explaining when to call acpi_ioapic_add().
v3: Previous versions break mips. This version fixes it.
IOAPICs present during system boot aren't added to ioapic_list,
thus are unable to be hot-removed. Fix it
On Sun, Jun 26, 2016 at 2:03 AM, PaX Team wrote:
> On 25 Jun 2016 at 3:13, Jann Horn wrote:
>
>> Since 2009 or so, PaX had reference count overflow mitigation code. My main
>> reasons for reinventing the wheel are:
>>
>> - PaX adds arch-specific code, both in the atomic_t operations and in
>>
Hi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: da2f6aba4a21f8da3331e5251a117c52764da579
commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove
HAVE_LATENCYTOP_SUPPORT
date: 5 months ago
config: ia64
On Thu, Jun 23, 2016 at 10:41 AM, Michal Suchanek wrote:
> This allows binding spidev on any slave device by hand using sysfs
> without adding superfluous compatibles or any other needless
> complication.
>
> Note that any slave driver that requires configuration will fail to
> probe anyway. Only
On Fri, 2016-24-06 at 17:43:00 UTC, Colin King wrote:
> From: Colin Ian King
>
> trivial fix to spelling mistake "rgistration" and minor clean up
> of the printk error message
Can you also:
- use pr_err()
- unsplit the message, ie. keep the string all on one line.
cheers
Daniel Lezcano writes:
> The init functions do not return any error. They behave as the following:
>
> - panic, thus leading to a kernel crash while another timer may work and
>make the system boot up correctly
>
> or
>
> - print an error and let the caller unaware if the state of the syst
> -Original Message-
> From: Chen, Yu C
> Sent: Sunday, June 26, 2016 9:17 AM
> To: 'Pavel Machek'
> Cc: linux...@vger.kernel.org; x...@kernel.org; Rafael J. Wysocki; Len Brown;
> Peter Zijlstra; H. Peter Anvin; Borislav Petkov; Brian Gerst; Thomas Gleixner;
> Ingo Molnar; Varun Koyyalagun
For ipv6+udp+geneve encapsulation data, the max_mtu should subtract
sizeof(ipv6hdr), instead of sizeof(iphdr).
Signed-off-by: Haishuang Yan
---
drivers/net/geneve.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/net/geneve.c b/drivers/net/geneve.c
index aa61
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/vmap_stack
commit a550c94136a5253a727e3af39f306b8c55b1721e ("sched: Free the stack early
if CONFIG_THREAD_INFO_IN_TASK")
on test machine: vm-lkp-wsx03-quantal-x86_64: 2 threads qemu-system
Hi,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: da2f6aba4a21f8da3331e5251a117c52764da579
commit: f69405ce6c0fc9f4a039011007371b31f80b470d openrisc: include: asm:
Kbuild: add default "vga.h"
date:
> 在 2016年6月26日，03:12，Peter Zijlstra 写道：
>
> On Sun, Jun 26, 2016 at 01:27:51AM +0800, panxinhui wrote:
>
>> by the way I still think mutex_unlock has a big overload too.
>
> Do you mean overhead?
>
oh, maybe you are right.
mutex_unlock ’s implementation uses inc_return variant on ppc, and
> 在 2016年6月26日，03:20，Peter Zijlstra 写道：
>
> On Sun, Jun 26, 2016 at 01:27:56AM +0800, panxinhui wrote:
Would that not have issues where the owner cpu is kept running but the
spinner (ie. _this_ vcpu) gets preempted? I would think that in that
case we too want to stop spinning.
>>>
The msm8974 pinctrl variant has a couple USB HSIC "glue"
registers that let us mux between the pinctrl register settings
or the HSIC core settings for the HSIC pins (gpio 144 and gpio
145). Support this method of operation by adding hsic_data and
hsic_strobe pins that can select between hsic_ctl an
This is part of a larger patch series that adds support for the
USB HSIC controller on msm8974 based SoCs. The first patch here
is a minor fix for a problem that isn't happening yet but could
happen in the future. The second patch adds an hsic pin so
we can configure the hsic bits that live in the
The function selection bitfield is not always 3 bits wide.
Sometimes it is 4 bits wide. Let's use the npins struct member to
determine how many bits wide the function selection bitfield is
so we clear the correct amount of bits in the register while
remuxing the pins.
Cc: Bjorn Andersson
Signed-o
This is a minimal driver to support bringing a usb4604 device
from microchip out of reset and into hub mode. The usb4604 device
is related to the usb3503 device, but it didn't seem close enough
to warrant putting both into the same file. This patch borrows
some of the usb3503 structure and trims it
Let's follow other driver registration functions and
automatically set the driver's owner member to THIS_MODULE when
ulpi_driver_register() is called. This allows ulpi driver writers
to forget about this boiler plate detail and avoids common bugs
in the process.
Cc: Heikki Krogerus
Signed-off-by:
While rewriting the USB support for MSM SoCs I ran into a few
minor bugs with the pm8941 regulator driver that hadn't been found
before. These patches are part of a larger series that allows me
to get proper USB OTG support working on the apq8074 dragonboard.
Stephen Boyd (3):
regulator: qcom_sp
The voltage switches support mode switching, so add support for
these ops to those types of regulators.
Cc: Bjorn Andersson
Fixes: e92a4047419c ("regulator: Add QCOM SPMI regulator driver")
Signed-off-by: Stephen Boyd
---
drivers/regulator/qcom_spmi-regulator.c | 2 ++
1 file changed, 2 inserti
The mvs1 and mvs2 switches are actually called 5vs1 and 5vs2 on
some datasheets. Let's rename them to match the datasheets and
also match the RPM based regulator driver which calls these by
their 5vs names (see qcom_smd-regulator.c). There aren't any
users of these regulators so far, so there aren'
The S4 supply is sometimes called the boost regulator because it
outputs 5V. Typically it's connected to the 5vs1 and 5vs2
switches for use in USB OTG and HDMI applications. Add support
for this regulator which was mistakenly left out from the initial
submission of this driver.
Cc: Bjorn Andersson
On these PMICs the usb cable connection/disconnection is
indicated by the usb-valid interrupt being high or low
respectively. Let's make an extcon for that, so we can notify usb
drivers of the cable state.
Cc: Bjorn Andersson
Cc: Chanwoo Choi
Signed-off-by: Stephen Boyd
---
drivers/power/qcom_
Some Qualcomm PMICs have a misc device that performs USB id pin
detection via an interrupt. When the interrupt triggers, we
should read the interrupt line to see if it has gone high or low.
If the interrupt is low then the ID pin is grounded, and if the
interrupt is high then the ID pin is being he
On Sun, Jun 26, 2016 at 01:21:04PM +0800, panxinhui wrote:
>
> > 在 2016年6月26日，03:20，Peter Zijlstra 写道：
> >
> > On Sun, Jun 26, 2016 at 01:27:56AM +0800, panxinhui wrote:
> Would that not have issues where the owner cpu is kept running but the
> spinner (ie. _this_ vcpu) gets preempted?
On Sat, Jun 25, 2016 at 04:26:01PM -0700, Andrew Pinski wrote:
> On Fri, Jun 24, 2016 at 4:38 AM, Florian Weimer wrote:
> > On 06/23/2016 09:56 AM, Andreas Schwab wrote:
> >>
> >> Andrew Pinski writes:
> >>
> >>> So the question becomes do we care enough about the incompatibles
> >>> between AARC
James,
This patch set contains two new major features:
* Multi-instance TPM proxy driver
* Rework of sharing common TIS code with different physical interfaces.
In addition, there are a vast number of small fixes and cleanups.
/Jarkko
Multi-instance TPM proxy driver
===
On Tue, May 24, 2016 at 11:37 PM, Rob Rice wrote:
> From: Rob Rice
>
> The Broadcom PDC mailbox driver is a mailbox controller that
> manages data transfers to and from one or more offload engines.
>
> Signed-off-by: Rob Rice
> Reviewed-by: Scott Branden
> Reviewed-by: Ray Jui
> ---
> drivers
This is to fix some bad issues on an over-commited guest.
test-caes:
perf record -a perf bench sched messaging -g 400 -p && perf report
18.09% sched-messaging [kernel.vmlinux] [k] osq_lock
12.28% sched-messaging [kernel.vmlinux] [k] rwsem_spin_on_owner
5.27% sched-messaging [kernel.vmlin
From: pan xinhui
this supports to fix lock holder preempted issue which run as a guest
two interfaces,
bool vcpu_is_preempted(int cpu);
unsigned int vcpu_get_yield_count(int cpu);
arch may need implement anyone of them.
some spinneris may also need call need_yield_to(int cpu, unsigned int
old_y
An over-committed guest with more vCPUs than pCPUs has a heavy overload
in osq_lock().
This is because vCPU A hold the osq lock and yield out, vCPU B wait
per_cpu node->locked to be set. IOW, vCPU B wait vCPU A to run and
unlock the osq lock.
So lets also use neet_yield_to() to detect if we need
Hello,
On 26 June 2016 at 06:14, Dan Williams wrote:
> On Thu, Jun 23, 2016 at 10:41 AM, Michal Suchanek wrote:
>> This allows binding spidev on any slave device by hand using sysfs
>> without adding superfluous compatibles or any other needless
>> complication.
>>
>> Note that any slave driver
On Sun, Jun 26, 2016 at 02:10:57PM +0800, Boqun Feng wrote:
> On Sun, Jun 26, 2016 at 01:21:04PM +0800, panxinhui wrote:
> >
> > > 在 2016年6月26日，03:20，Peter Zijlstra 写道：
> > >
> > > On Sun, Jun 26, 2016 at 01:27:56AM +0800, panxinhui wrote:
> > Would that not have issues where the owner cpu
> 在 2016年6月26日，14:10，Boqun Feng 写道：
>
> On Sun, Jun 26, 2016 at 01:21:04PM +0800, panxinhui wrote:
>>
>>> 在 2016年6月26日，03:20，Peter Zijlstra 写道：
>>>
>>> On Sun, Jun 26, 2016 at 01:27:56AM +0800, panxinhui wrote:
>> Would that not have issues where the owner cpu is kept running but the
201 - 295 of 295 matches
Mail list logo
