From: Steve Twiss
Device tree binding information for DA9062 and DA9061 thermal junction
temperature monitor.
Binding descriptions for the DA9061 and DA9062 thermal TJUNC supervisor
device driver, using a single THERMAL_TRIP_HOT trip-wire and allowing for
a
On 2016-10-26 00:38, Chanwoo Choi wrote:
This patch uses the resource-managed to add the devfreq device.
This function will make it easy to handle the devfreq device.
- struct devfreq *devm_devfreq_add_device(struct device *dev,
struct devfreq_dev_profile
From: Steve Twiss
Extend existing DA9062 binding information to include the DA9061 PMIC for
MFD core and regulators.
Add a da9062-onkey link to the existing onkey binding file.
Add a da9062-thermal link to the new temperature monitoring binding file
found in
From: Steve Twiss
The of_device_id match array is added to support "dlg,da9062-watchdog"
as a valid .compatible string.
The watchdog_info structure is linked to this device tree compatible
string in the .data section. Extra code is added into the probe function to
On Tue, 2016-10-25 at 11:39 -0400, Alexander Duyck wrote:
> This reverts commit f9d40f6a9921 ("igb: Revert support for build_skb in
> igb") and adds a few changes to update it to work with the latest version
> of igb. We are now able to revert the removal of this due to the fact
> that with the
From: Steve Twiss
MFD support for DA9061 is provided as part of the DA9062 device driver.
The registers header file adds two new chip variant IDs defined in DA9061
and DA9062 hardware. The core header file adds new software enumerations
for listing the valid
From: Steve Twiss
The of_device_id match array is added to support "dlg,da9062-watchdog"
as a valid .compatible string.
The watchdog_info structure is linked to this device tree compatible
string in the .data section. Extra code is added into the probe function to
search-for and assign this
On Tue, 2016-10-25 at 11:39 -0400, Alexander Duyck wrote:
> This reverts commit f9d40f6a9921 ("igb: Revert support for build_skb in
> igb") and adds a few changes to update it to work with the latest version
> of igb. We are now able to revert the removal of this due to the fact
> that with the
From: Steve Twiss
MFD support for DA9061 is provided as part of the DA9062 device driver.
The registers header file adds two new chip variant IDs defined in DA9061
and DA9062 hardware. The core header file adds new software enumerations
for listing the valid DA9061 IRQs and a
From: Steve Twiss
Device tree binding information for DA9062 and DA9061 thermal junction
temperature monitor.
Binding descriptions for the DA9061 and DA9062 thermal TJUNC supervisor
device driver, using a single THERMAL_TRIP_HOT trip-wire and allowing for
a configurable polling period for
On 2016-10-26 00:38, Chanwoo Choi wrote:
This patch uses the resource-managed to add the devfreq device.
This function will make it easy to handle the devfreq device.
- struct devfreq *devm_devfreq_add_device(struct device *dev,
struct devfreq_dev_profile
From: Steve Twiss
Extend existing DA9062 binding information to include the DA9061 PMIC for
MFD core and regulators.
Add a da9062-onkey link to the existing onkey binding file.
Add a da9062-thermal link to the new temperature monitoring binding file
found in [PATCH V2 03/10].
Delete the
On 10/26/2016 09:36 AM, Marc Zyngier wrote:
> On Wed, Oct 26 2016 at 05:17:34 PM, Vineet Gupta
> wrote:
>> On 10/26/2016 07:05 AM, Marc Zyngier wrote:
>>> It definitely feels weird to encode the interrupt affinity in the DT
>>> (the kernel and possible userspace
On Tue, 2016-10-25 at 11:39 -0400, Alexander Duyck wrote:
> The ARM architecture provides a mechanism for deferring cache line
> invalidation in the case of map/unmap. This patch makes use of this
> mechanism to avoid unnecessary synchronization.
>
> A secondary effect of this change is that the
From: Steve Twiss
Add junction temperature monitoring supervisor device driver, compatible
with the DA9062 and DA9061 PMICs.
If the PMIC's internal junction temperature rises above TEMP_WARN (125
degC) an interrupt is issued. This TEMP_WARN level is defined as the
From: Steve Twiss
Add junction temperature monitoring supervisor device driver, compatible
with the DA9062 and DA9061 PMICs.
If the PMIC's internal junction temperature rises above TEMP_WARN (125
degC) an interrupt is issued. This TEMP_WARN level is defined as the
THERMAL_TRIP_HOT trip-wire
On 10/26/2016 09:36 AM, Marc Zyngier wrote:
> On Wed, Oct 26 2016 at 05:17:34 PM, Vineet Gupta
> wrote:
>> On 10/26/2016 07:05 AM, Marc Zyngier wrote:
>>> It definitely feels weird to encode the interrupt affinity in the DT
>>> (the kernel and possible userspace usually know much better than the
On Tue, 2016-10-25 at 11:39 -0400, Alexander Duyck wrote:
> The ARM architecture provides a mechanism for deferring cache line
> invalidation in the case of map/unmap. This patch makes use of this
> mechanism to avoid unnecessary synchronization.
>
> A secondary effect of this change is that the
From: Steve Twiss
Hi,
Dialog Semiconductor support would like to add to the MAINTAINERS search
terms. This update will allow us to follow files for device tree bindings
and source code relating to input onkey drivers, chip thermal monitoring
and watchdog timers.
From: Steve Twiss
Hi,
Dialog Semiconductor support would like to add to the MAINTAINERS search
terms. This update will allow us to follow files for device tree bindings
and source code relating to input onkey drivers, chip thermal monitoring
and watchdog timers.
Signed-off-by: Steve Twiss
On Tue, 2016-10-25 at 11:39 -0400, Alexander Duyck wrote:
> This patch updates the driver code so that we do bulk updates of the page
> reference count instead of just incrementing it by one reference at a
> time.
> The advantage to doing this is that we cut down on atomic operations and
> this in
On Tue, 2016-10-25 at 11:39 -0400, Alexander Duyck wrote:
> This patch updates the driver code so that we do bulk updates of the page
> reference count instead of just incrementing it by one reference at a
> time.
> The advantage to doing this is that we cut down on atomic operations and
> this in
From: Steve Twiss
Add binding information for DA9062 and DA9061 watchdog.
Example bindings for both devices are added.
The original binding for DA9062 (only) used to reside inside the
Documentation/devicetree/bindings/mfd/da9062.txt MFD document.
The
From: Steve Twiss
Add binding information for DA9062 and DA9061 watchdog.
Example bindings for both devices are added.
The original binding for DA9062 (only) used to reside inside the
Documentation/devicetree/bindings/mfd/da9062.txt MFD document.
The da9062-watchdog section was deleted in that
On Wed, Oct 26, 2016 at 05:12:36PM +, Nicholas Mc Guire wrote:
> On Wed, Oct 26, 2016 at 05:42:13PM +0200, Peter Zijlstra wrote:
> > On Wed, Oct 26, 2016 at 05:10:01AM -0700, Dmitry Torokhov wrote:
> > > On Wed, Oct 26, 2016 at 10:45:35AM +0200, Peter Zijlstra wrote:
> > > > On Tue, Oct 25,
On Wed, Oct 26, 2016 at 05:12:36PM +, Nicholas Mc Guire wrote:
> On Wed, Oct 26, 2016 at 05:42:13PM +0200, Peter Zijlstra wrote:
> > On Wed, Oct 26, 2016 at 05:10:01AM -0700, Dmitry Torokhov wrote:
> > > On Wed, Oct 26, 2016 at 10:45:35AM +0200, Peter Zijlstra wrote:
> > > > On Tue, Oct 25,
From: Steve Twiss
Add binding information for DA9061 onkey.
This patch updates the compatible string "dlg,da9061-onkey" to support
DA9061, removes the reference to KEY_SLEEP (which the driver no longer
supports) and fixes a typo in the example for DA9063.
It also
From: Steve Twiss
Regulator support for the DA9061 is added into the DA9062 regulator driver.
The regulators for DA9061 differ from those of DA9062.
A new DA9061 enumeration list for the LDOs and Bucks supported by this
device is added. Regulator information
From: Steve Twiss
Copyright header is updated to add DA9061 in its description and the module
description macro is extended to include DA9061.
Minor change to the code, alters dev_dbg() statements to report a generic
"PMIC" instead of DA9063. This device driver is
From: Steve Twiss
This patch set adds support for the Dialog DA9061 Power Management IC.
Support is made by altering the existing DA9062 device driver, where
appropriate.
In this patch set the following is provided:
[PATCH V2 01/10] Binding for onkey
[PATCH V2
From: Steve Twiss
Add binding information for DA9061 onkey.
This patch updates the compatible string "dlg,da9061-onkey" to support
DA9061, removes the reference to KEY_SLEEP (which the driver no longer
supports) and fixes a typo in the example for DA9063.
It also adds two new examples, one for
From: Steve Twiss
Regulator support for the DA9061 is added into the DA9062 regulator driver.
The regulators for DA9061 differ from those of DA9062.
A new DA9061 enumeration list for the LDOs and Bucks supported by this
device is added. Regulator information added: the old regulator
From: Steve Twiss
Copyright header is updated to add DA9061 in its description and the module
description macro is extended to include DA9061.
Minor change to the code, alters dev_dbg() statements to report a generic
"PMIC" instead of DA9063. This device driver is compatible with DA9061,
DA9062
From: Steve Twiss
This patch set adds support for the Dialog DA9061 Power Management IC.
Support is made by altering the existing DA9062 device driver, where
appropriate.
In this patch set the following is provided:
[PATCH V2 01/10] Binding for onkey
[PATCH V2 02/10] Binding for watchdog
On Wed, Oct 26, 2016 at 9:32 AM, Linus Torvalds
wrote:
>
> Quite frankly, I think the solution is to just rip out all the insane
> zone crap.
IOW, something like the attached.
Advantage:
- just look at the number of garbage lines removed! 21
insertions(+), 182
On Wed, Oct 26, 2016 at 9:32 AM, Linus Torvalds
wrote:
>
> Quite frankly, I think the solution is to just rip out all the insane
> zone crap.
IOW, something like the attached.
Advantage:
- just look at the number of garbage lines removed! 21
insertions(+), 182 deletions(-)
- it will
On Wednesday 26 October 2016 10:07 PM, David Lechner wrote:
> On 10/26/2016 02:59 AM, Sekhar Nori wrote:
>> On Wednesday 26 October 2016 08:36 AM, David Lechner wrote:
>>> Up to this point, the USB phy clock configuration was handled
>>> manually in
>>> the board files and in the usb drivers. This
On Wednesday 26 October 2016 10:07 PM, David Lechner wrote:
> On 10/26/2016 02:59 AM, Sekhar Nori wrote:
>> On Wednesday 26 October 2016 08:36 AM, David Lechner wrote:
>>> Up to this point, the USB phy clock configuration was handled
>>> manually in
>>> the board files and in the usb drivers. This
On Wed, Oct 26, 2016 at 05:42:13PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 26, 2016 at 05:10:01AM -0700, Dmitry Torokhov wrote:
> > On Wed, Oct 26, 2016 at 10:45:35AM +0200, Peter Zijlstra wrote:
> > > On Tue, Oct 25, 2016 at 03:30:54PM -0700, Dmitry Torokhov wrote:
>
> > > > Or do we need
On Wed, Oct 26, 2016 at 05:42:13PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 26, 2016 at 05:10:01AM -0700, Dmitry Torokhov wrote:
> > On Wed, Oct 26, 2016 at 10:45:35AM +0200, Peter Zijlstra wrote:
> > > On Tue, Oct 25, 2016 at 03:30:54PM -0700, Dmitry Torokhov wrote:
>
> > > > Or do we need
On Wed, 2016-09-21 at 14:57 +0800, Yangbo Lu wrote:
> diff --git a/drivers/soc/fsl/Kconfig b/drivers/soc/fsl/Kconfig
> new file mode 100644
> index 000..b99764c
> --- /dev/null
> +++ b/drivers/soc/fsl/Kconfig
> @@ -0,0 +1,19 @@
> +#
> +# Freescale SOC drivers
> +#
> +
> +source
On Wed, 2016-09-21 at 14:57 +0800, Yangbo Lu wrote:
> diff --git a/drivers/soc/fsl/Kconfig b/drivers/soc/fsl/Kconfig
> new file mode 100644
> index 000..b99764c
> --- /dev/null
> +++ b/drivers/soc/fsl/Kconfig
> @@ -0,0 +1,19 @@
> +#
> +# Freescale SOC drivers
> +#
> +
> +source
On Wed, 2016-10-26 at 18:53 +0200, Abdelrhman Ahmed wrote:
> I think it's at the right place as the current one is a little different from
> the
> commit e1f165032c8bade3a6bdf546f8faf61fda4dd01c.
>
> In the next lines, skb_push is called after copying the hardware header and
> there
> is no
On Wed, 2016-10-26 at 18:53 +0200, Abdelrhman Ahmed wrote:
> I think it's at the right place as the current one is a little different from
> the
> commit e1f165032c8bade3a6bdf546f8faf61fda4dd01c.
>
> In the next lines, skb_push is called after copying the hardware header and
> there
> is no
Add null tests for the internal algorithm to avoid errors when running
in FIPS mode.
Signed-off-by: Marcelo Cerri
---
crypto/testmgr.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index 58f903d..cfafd24 100644
---
Add null tests for the internal algorithm to avoid errors when running
in FIPS mode.
Signed-off-by: Marcelo Cerri
---
crypto/testmgr.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index 58f903d..cfafd24 100644
--- a/crypto/testmgr.c
+++
Add null tests for the internal algorithm to avoid errors when running
in FIPS mode.
Signed-off-by: Marcelo Cerri
---
crypto/testmgr.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index d999373..58f903d 100644
---
Add null tests for the internal algorithm to avoid errors when running
in FIPS mode.
Signed-off-by: Marcelo Cerri
---
crypto/testmgr.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index ded50b6..d999373 100644
---
Add null tests for the internal algorithm to avoid errors when running
in FIPS mode.
Signed-off-by: Marcelo Cerri
---
crypto/testmgr.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index d999373..58f903d 100644
--- a/crypto/testmgr.c
+++
Add null tests for the internal algorithm to avoid errors when running
in FIPS mode.
Signed-off-by: Marcelo Cerri
---
crypto/testmgr.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index ded50b6..d999373 100644
--- a/crypto/testmgr.c
+++
tmpfs seems to be incorrectly returning 0-bytes when reading from
a file that is concurrently being truncated.
This is causing crashes in gocryptfs, a cryptographic FUSE overlay,
when it reads a nonce from disk that should absolutely positively
never be all-zero.
I have written a reproducer in C
tmpfs seems to be incorrectly returning 0-bytes when reading from
a file that is concurrently being truncated.
This is causing crashes in gocryptfs, a cryptographic FUSE overlay,
when it reads a nonce from disk that should absolutely positively
never be all-zero.
I have written a reproducer in C
This series adds null tests for all sha*-mb internal algorithms so they can
be used in FIPS mode without further problems.
Since they are 3 separated modules I decided to use a separated commit for
each one.
Marcelo Cerri (3):
crypto: testmgr - Add missing tests for internal sha1-mb
This series adds null tests for all sha*-mb internal algorithms so they can
be used in FIPS mode without further problems.
Since they are 3 separated modules I decided to use a separated commit for
each one.
Marcelo Cerri (3):
crypto: testmgr - Add missing tests for internal sha1-mb
On Wed, Oct 26, 2016 at 09:52:53PM +1100, Michael Ellerman wrote:
As far as I know, power has nothing like the SRAT that tells us, at
boot, which memory is hotpluggable.
On pseries we have the ibm,dynamic-memory device tree property, which
can contain ranges of memory that are not yet
On Wed, Oct 26, 2016 at 09:52:53PM +1100, Michael Ellerman wrote:
As far as I know, power has nothing like the SRAT that tells us, at
boot, which memory is hotpluggable.
On pseries we have the ibm,dynamic-memory device tree property, which
can contain ranges of memory that are not yet
On 26/10/2016 16:52, Jann Horn wrote:
> On Wed, Oct 26, 2016 at 08:56:36AM +0200, Mickaël Salaün wrote:
>> The loaded Landlock eBPF programs can be triggered by a seccomp filter
>> returning RET_LANDLOCK. In addition, a cookie (16-bit value) can be passed
>> from
>> a seccomp filter to eBPF
On 26/10/2016 16:52, Jann Horn wrote:
> On Wed, Oct 26, 2016 at 08:56:36AM +0200, Mickaël Salaün wrote:
>> The loaded Landlock eBPF programs can be triggered by a seccomp filter
>> returning RET_LANDLOCK. In addition, a cookie (16-bit value) can be passed
>> from
>> a seccomp filter to eBPF
Hi,
On Wednesday, July 13, 2016 04:37:31 PM Arnd Bergmann wrote:
> On Wednesday, July 13, 2016 12:59:23 PM CEST Bartlomiej Zolnierkiewicz wrote:
> >
> > On Friday, July 08, 2016 10:23:48 PM Arnd Bergmann wrote:
> > > On Friday, July 8, 2016 5:24:41 PM CEST Bartlomiej Zolnierkiewicz wrote:
> > >
Hi,
On Wednesday, July 13, 2016 04:37:31 PM Arnd Bergmann wrote:
> On Wednesday, July 13, 2016 12:59:23 PM CEST Bartlomiej Zolnierkiewicz wrote:
> >
> > On Friday, July 08, 2016 10:23:48 PM Arnd Bergmann wrote:
> > > On Friday, July 8, 2016 5:24:41 PM CEST Bartlomiej Zolnierkiewicz wrote:
> > >
On Wed, Oct 26, 2016 at 12:36 AM, Michal Malý wrote:
> Hi all,
>
> maybe instead of stalling the entire init() function it'd be better to put a
> request to disable autocentering on a workqueue and start a delayed work once
> the init() function is done setting the wheel
On Wed, Oct 26, 2016 at 12:36 AM, Michal Malý wrote:
> Hi all,
>
> maybe instead of stalling the entire init() function it'd be better to put a
> request to disable autocentering on a workqueue and start a delayed work once
> the init() function is done setting the wheel up? There'd be a bit more
On Mon, Oct 03, 2016 at 07:07:54PM +0800, Chen-Yu Tsai wrote:
> While DAPM is mono or single channel, its controls can be shared between
> widgets, such as sharing one stereo mixer control between the left and
> right channel widgets.
> This patch introduces support for such shared mixer
On Mon, Oct 03, 2016 at 07:07:54PM +0800, Chen-Yu Tsai wrote:
> While DAPM is mono or single channel, its controls can be shared between
> widgets, such as sharing one stereo mixer control between the left and
> right channel widgets.
> This patch introduces support for such shared mixer
I think it's at the right place as the current one is a little different from
the
commit e1f165032c8bade3a6bdf546f8faf61fda4dd01c.
In the next lines, skb_push is called after copying the hardware header and
there
is no change to the data pointer inside the retry loop. We only need to reset
I think it's at the right place as the current one is a little different from
the
commit e1f165032c8bade3a6bdf546f8faf61fda4dd01c.
In the next lines, skb_push is called after copying the hardware header and
there
is no change to the data pointer inside the retry loop. We only need to reset
Set pv_time_ops.sched_clock to vmware_sched_clock(). It is simplified
version of native_sched_clock() without ring buffer of mult/shift/offset
triplets and preempt toggling.
Since VMware hypervisor provides constant tsc we can use constant
mult/shift/offset triplet calculated at boot time.
Set pv_time_ops.sched_clock to vmware_sched_clock(). It is simplified
version of native_sched_clock() without ring buffer of mult/shift/offset
triplets and preempt toggling.
Since VMware hypervisor provides constant tsc we can use constant
mult/shift/offset triplet calculated at boot time.
On Wed, Oct 26, 2016 at 12:36:09PM -0400, Lyude wrote:
> One of the CI machines began to run into issues with the hpd poller
> suddenly waking up in the midst of the late suspend phase. It looks like
> this is getting caused by the fact we now deinitialize power wells in
> late suspend, which
On Wed, Oct 26, 2016 at 12:36:09PM -0400, Lyude wrote:
> One of the CI machines began to run into issues with the hpd poller
> suddenly waking up in the midst of the late suspend phase. It looks like
> this is getting caused by the fact we now deinitialize power wells in
> late suspend, which
On Wed, Oct 26, 2016 at 9:30 AM, Dave Jones wrote:
>
> I gave this a go last thing last night. It crashed within 5 minutes,
> but it was one we've already seen (the bad page map trace) with nothing
> additional that looked interesting.
Did the bad page map trace have any
On Wed, Oct 26, 2016 at 9:30 AM, Dave Jones wrote:
>
> I gave this a go last thing last night. It crashed within 5 minutes,
> but it was one we've already seen (the bad page map trace) with nothing
> additional that looked interesting.
Did the bad page map trace have any registers that looked
On Wed, Oct 26, 2016 at 09:06:31AM -0700, Alex Gagniuc wrote:
> Thanks for the heads up! Sorry about that. Do you want me to resend
> this as a single mail?
It's fine, no need.
signature.asc
Description: PGP signature
On Wed, Oct 26, 2016 at 09:06:31AM -0700, Alex Gagniuc wrote:
> Thanks for the heads up! Sorry about that. Do you want me to resend
> this as a single mail?
It's fine, no need.
signature.asc
Description: PGP signature
On Wed, Oct 26, 2016 at 06:03:44PM +0200, Arnd Bergmann wrote:
> On Wednesday, October 26, 2016 10:34:08 AM CEST Josh Poimboeuf wrote:
> > The following commit:
> >
> > 3732710ff6f2 ("objtool: Improve rare switch jump table pattern detection")
> >
> > ... improved objtool's ability to detect
On Wed, Oct 26, 2016 at 06:03:44PM +0200, Arnd Bergmann wrote:
> On Wednesday, October 26, 2016 10:34:08 AM CEST Josh Poimboeuf wrote:
> > The following commit:
> >
> > 3732710ff6f2 ("objtool: Improve rare switch jump table pattern detection")
> >
> > ... improved objtool's ability to detect
On 10/26/2016 05:40 PM, David Lechner wrote:
> On 10/26/2016 05:58 AM, Alexandre Bailon wrote:
>> If we configure the da8xx OTG phy in OTG mode, neither device or host
>> mode will work. That is because the PHY is not able to detect and notify
>> the driver that value of ID pin changed.
>> To work
On 10/26/2016 05:40 PM, David Lechner wrote:
> On 10/26/2016 05:58 AM, Alexandre Bailon wrote:
>> If we configure the da8xx OTG phy in OTG mode, neither device or host
>> mode will work. That is because the PHY is not able to detect and notify
>> the driver that value of ID pin changed.
>> To work
Add compatible strings for Pro5, PXs2, LD6b, LD11, LD20 SoCs to use
the generic cpufreq driver.
Signed-off-by: Masahiro Yamada
---
drivers/cpufreq/cpufreq-dt-platdev.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c
Add compatible strings for Pro5, PXs2, LD6b, LD11, LD20 SoCs to use
the generic cpufreq driver.
Signed-off-by: Masahiro Yamada
---
drivers/cpufreq/cpufreq-dt-platdev.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c
On 26 October 2016 at 08:57, Antoine Tenart
wrote:
> This patch adds the possibility for slave drivers to register a
> callback, to be called whenever a new device matching the slave ID
> is connected.
>
> Signed-off-by: Antoine Tenart
On 26 October 2016 at 08:57, Antoine Tenart
wrote:
> This patch adds the possibility for slave drivers to register a
> callback, to be called whenever a new device matching the slave ID
> is connected.
>
> Signed-off-by: Antoine Tenart
> ---
> drivers/w1/w1.c| 10 ++
>
Add a CPU clock to every CPU node and a CPU OPP table to use the
generic cpufreq driver.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-pro5.dtsi | 74
1 file changed, 74 insertions(+)
diff --git
Add a CPU clock to every CPU node and a CPU OPP table to use the
generic cpufreq driver.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-pxs2.dtsi | 46
1 file changed, 46 insertions(+)
diff --git
Add a CPU clock to every CPU node and a CPU OPP table to use the
generic cpufreq driver.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-pro5.dtsi | 74
1 file changed, 74 insertions(+)
diff --git a/arch/arm/boot/dts/uniphier-pro5.dtsi
Add a CPU clock to every CPU node and a CPU OPP table to use the
generic cpufreq driver.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-pxs2.dtsi | 46
1 file changed, 46 insertions(+)
diff --git a/arch/arm/boot/dts/uniphier-pxs2.dtsi
On 26 October 2016 at 08:57, Antoine Tenart
wrote:
GKH won't accept an empty commit log.
> Signed-off-by: Antoine Tenart
> ---
> drivers/w1/w1.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git
On 26 October 2016 at 08:57, Antoine Tenart
wrote:
GKH won't accept an empty commit log.
> Signed-off-by: Antoine Tenart
> ---
> drivers/w1/w1.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
> index bb34362e930a..80d0cc4e6e7f
On Wed, Oct 26 2016 at 05:17:34 PM, Vineet Gupta
wrote:
> On 10/26/2016 07:05 AM, Marc Zyngier wrote:
>> It definitely feels weird to encode the interrupt affinity in the DT
>> (the kernel and possible userspace usually know much better than the
>> firmware). What is
One of the CI machines began to run into issues with the hpd poller
suddenly waking up in the midst of the late suspend phase. It looks like
this is getting caused by the fact we now deinitialize power wells in
late suspend, which means that intel_hpd_poll_init() gets called in late
suspend
On Wed, Oct 26 2016 at 05:17:34 PM, Vineet Gupta
wrote:
> On 10/26/2016 07:05 AM, Marc Zyngier wrote:
>> It definitely feels weird to encode the interrupt affinity in the DT
>> (the kernel and possible userspace usually know much better than the
>> firmware). What is the actual reason for
One of the CI machines began to run into issues with the hpd poller
suddenly waking up in the midst of the late suspend phase. It looks like
this is getting caused by the fact we now deinitialize power wells in
late suspend, which means that intel_hpd_poll_init() gets called in late
suspend
On 10/26/2016 02:59 AM, Sekhar Nori wrote:
On Wednesday 26 October 2016 08:36 AM, David Lechner wrote:
Up to this point, the USB phy clock configuration was handled manually in
the board files and in the usb drivers. This adds proper clocks so that
the usb drivers can use clk_get and clk_enable
On 10/26/2016 02:59 AM, Sekhar Nori wrote:
On Wednesday 26 October 2016 08:36 AM, David Lechner wrote:
Up to this point, the USB phy clock configuration was handled manually in
the board files and in the usb drivers. This adds proper clocks so that
the usb drivers can use clk_get and clk_enable
On Wed, Oct 26, 2016 at 09:23:41AM +0800, Jin, Yao wrote:
> If I change it to, for example: removed iterations: 20%
>
> Is that OK?
No it should be average iterations, not percentage.
Also "iterations", not "removed iterations"
-Andi
On Wed, Oct 26, 2016 at 09:23:41AM +0800, Jin, Yao wrote:
> If I change it to, for example: removed iterations: 20%
>
> Is that OK?
No it should be average iterations, not percentage.
Also "iterations", not "removed iterations"
-Andi
On Wed, Oct 26, 2016 at 8:51 AM, Andy Lutomirski wrote:
>>
>> I get the following BUG with 4.9-rc2, CONFIG_VMAP_STACK and
>> CONFIG_DEBUG_VIRTUAL turned on:
>>
>> kernel BUG at arch/x86/mm/physaddr.c:26!
>
> const struct zone *zone = page_zone(virt_to_page(word));
>
> If
On Wed, Oct 26, 2016 at 8:51 AM, Andy Lutomirski wrote:
>>
>> I get the following BUG with 4.9-rc2, CONFIG_VMAP_STACK and
>> CONFIG_DEBUG_VIRTUAL turned on:
>>
>> kernel BUG at arch/x86/mm/physaddr.c:26!
>
> const struct zone *zone = page_zone(virt_to_page(word));
>
> If the stack is vmalloced,
Hi Antoine,
Please find my comments below.
On 26 October 2016 at 08:57, Antoine Tenart
wrote:
> The overlay manager is an in-kernel library helping to handle dt overlay
> loading when using capes.
>
> Signed-off-by: Antoine Tenart
From: Ioana Ciornei
align function arguments that were not aligned to the starting parenthesis
Signed-off-by: Ioana Ciornei
Signed-off-by: Stuart Yoder
---
-v2
-patch is result of split of original patch, updated
901 - 1000 of 2598 matches
Mail list logo