Signed-off-by: Ludovic Barre
Signed-off-by: Lee Jones
---
drivers/remoteproc/Kconfig | 9 ++
drivers/remoteproc/Makefile| 1 +
drivers/remoteproc/st_remoteproc.c | 297 +
3 files changed, 307 insertions(+)
create mode 100644
Doing so saves quite a bit of code in the driver.
For more information on the 'reserved-memory' bindings see:
Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
Suggested-by: Suman Anna
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/stih407-family.dtsi | 46
On Wed, Oct 21, 2015 at 01:27:33PM +0200, Tomasz Nowicki wrote:
> On 21.10.2015 13:02, Liviu Dudau wrote:
> >On Wed, Oct 21, 2015 at 11:57:53AM +0200, Tomasz Nowicki wrote:
> >>On 14.10.2015 08:29, Jiang Liu wrote:
> >>>Introduce common interface acpi_pci_root_create() and related data
>
On Thu, Sep 24, 2015 at 11:32 AM, Yang Yingliang
wrote:
> When cpu is disabled, all irqs will be migratged to another cpu.
> In some cases, a new affinity is different, the old affinity need
> to be updated and if irq_set_affinity's return value is IRQ_SET_MASK_OK_DONE,
> the old affinity can not
On Wed, Oct 21, 2015 at 04:27:43AM -0400, George Spelvin wrote:
> After having worked out the basics of a non-blocking /dev/urandom read,
> (patches poated; I'm hoping someone will comment on them!), I need to
> work out the crypto.
Can we just use my multi pool patch for now? It works and is
On Wed, Oct 21, 2015 at 01:27:33PM +0200, Tomasz Nowicki wrote:
> On 21.10.2015 13:02, Liviu Dudau wrote:
> >On Wed, Oct 21, 2015 at 11:57:53AM +0200, Tomasz Nowicki wrote:
> >>On 14.10.2015 08:29, Jiang Liu wrote:
> >>>Introduce common interface acpi_pci_root_create() and related data
>
On Fri, 2015-16-10 at 21:38:45 UTC, Christophe Jaillet wrote:
> of_get_property() is used inside the loop, but then the reference to the
> node is dropped before dereferencing the prop pointer, which could by then
> point to junk if the node has been freed.
>
> Instead use of_property_read_u32()
The subject should be "ARM: dts: uniphier: DTS updates for UniPhier
SoCs for Linux 4.4-rc1"
I cannot wait until Linux 4.14-rc1 :)
--
Best Regards
Masahiro Yamada
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, 21 Oct 2015, Andy Shevchenko wrote:
> From: Mika Westerberg
>
> Intel Broxton has the same LPSS block than Intel Sunrisepoint so add
> Broxton ACPI IDs to the list.
>
> Signed-off-by: Mika Westerberg
> Signed-off-by: Andy Shevchenko
> ---
> drivers/mfd/intel-lpss-acpi.c | 16
On Wed, 21 Oct 2015, Andy Shevchenko wrote:
> Intel Broxton has the same LPSS block than Intel Sunrisepoint so add
> Broxton PCI IDs to the list.
>
> Signed-off-by: Mika Westerberg
> Signed-off-by: Andy Shevchenko
> ---
> drivers/mfd/intel-lpss-pci.c | 45
>
DO YOU NEED A LOAN AT 3% RATE ANNUALLY,IF YES CONTACT US FOR MORE INFO
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Wed, 21 Oct 2015 10:01:42 +0200
Peter Zijlstra wrote:
> > I should probably add a "if (in_nmi()) return" somewhere.
>
> But if there's an arch that doesn't use a separate NMI stack, the NMI
> might cause the largest stack, which would then remain invisible from
> the stack-tracer.
>
>
The user space should not expect that a particular I2C channel is
always visible through the same character device.
No reason to fix the I2C indexes with aliases.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ph1-ld4-ref.dts | 4
Specifying both console and stdout-path is redundant. Add options
":115200n8" to stdout-path and drop "console=ttyS0,115200".
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ph1-ld4-ref.dts | 3 +--
arch/arm/boot/dts/uniphier-ph1-ld6b-ref.dts | 3 +--
Hi Arnd,
I dropped I2C aliases.
(I want this policy to be consistent for all the uniphier DTS files.
2/4 deletes them from existing DTS files too.)
Please pull this series for the next merge window.
Thanks,
Masahiro
Masahiro Yamada (4):
ARM: dts: uniphier: use stdout-path instead of
On 2015/10/21 17:12, Peter Zijlstra wrote:
On Tue, Oct 20, 2015 at 03:53:02PM -0700, Alexei Starovoitov wrote:
On 10/20/15 12:22 AM, Kaixu Xia wrote:
diff --git a/kernel/events/core.c b/kernel/events/core.c
index b11756f..5219635 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
Initial version of DTS for ProXstream2 Vodka board.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/uniphier-proxstream2-vodka.dts | 74
2 files changed, 76 insertions(+), 1 deletion(-)
create mode 100644
Initial version of DTS for ProXstream2 Gentil board.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/Makefile| 3 +-
arch/arm/boot/dts/uniphier-proxstream2-gentil.dts | 74 +++
2 files changed, 76 insertions(+), 1 deletion(-)
create mode
On Wed, Oct 21, 2015 at 06:31:04PM +0800, xiakaixu wrote:
> The RFC patch set contains the necessary commit log [1].
That's of course the wrong place, this should be in the patch's
Changelog. It doesn't become less relevant.
> In some scenarios we don't want to output trace data when perf
On Oct 20, 2015, at 5:00 PM, AKASHI Takahiro wrote:
Hi Akashi,
> Adding an extra dummy stack frame for interrupt has one side-effect that
> dump_backtrace() shows inccorect data of struct pt_regs at
> "Exception stack ..." because we are still on an interrupt stack when
> dump_backtrace()
Hi Tomeu,
On Mon, Sep 7, 2015 at 2:23 PM, Tomeu Vizoso wrote:
> Walks the OF tree up and finds the closest ancestor that has a struct
> device associated with it, probing it if isn't bound to a driver yet.
>
> The above should ensure that the dependency represented by the passed OF
> node is
On 21.10.2015 13:02, Liviu Dudau wrote:
On Wed, Oct 21, 2015 at 11:57:53AM +0200, Tomasz Nowicki wrote:
On 14.10.2015 08:29, Jiang Liu wrote:
Introduce common interface acpi_pci_root_create() and related data
structures to create PCI root bus for ACPI PCI host bridges. It will
be used to kill
On Wed, 21 Oct 2015, Mark Brown wrote:
> On Wed, Oct 21, 2015 at 09:46:33AM +0100, Lee Jones wrote:
> > On Tue, 20 Oct 2015, Andrew F. Davis wrote:
>
> > > I could change the core to be "tps65086-pmic", then call the regulator
> > > driver "tps65086-regulator" if this works for you, this seems
On Sun, 11 Oct 2015, Jiri Slaby wrote:
> Some drivers indent some lines in a very weird manner. Fix that.
>
> Signed-off-by: Jiri Slaby
> Cc: Josenivaldo Benito Junior
> Cc: Franco Catrin
> Cc: Nikolai Kondrashov
> Cc: Don Prince
> Cc: srinivas pandruvada
Some of the are not really worth
On 21/10/15 12:01, Ulf Hansson wrote:
On 21 October 2015 at 12:25, Sudeep Holla wrote:
On 21/10/15 11:21, Nicolas Ferre wrote:
Le 21/10/2015 12:10, Sudeep Holla a écrit :
Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
check for/support the legacy
On Wed, Oct 21, 2015 at 08:24:11PM +1100, Paul Mackerras wrote:
> On Tue, Oct 20, 2015 at 04:00:31PM +0200, Peter Zijlstra wrote:
> >
> > Should we not take this opportunity to get rid of these open-coded wait
> > loops?
> >
> >
> > Does this work?
>
> No, on Book3S HV (POWER8) the VM hangs
On Wed, Oct 21, 2015 at 11:18:09AM +0200, Petr Mladek wrote:
> There are few situations when we reinitialize (zap) ticket spinlocks. It
> typically happens when the system is going down after an error and we
> want to avoid deadlock in some important services. For example,
> zap_locks() in
* tip-bot for Taku Izumi wrote:
> Commit-ID: 0f96a99dab366333439e110d6ad253bc7c557c09
> Gitweb: http://git.kernel.org/tip/0f96a99dab366333439e110d6ad253bc7c557c09
> Author: Taku Izumi
> AuthorDate: Wed, 30 Sep 2015 23:01:56 +0900
> Committer: Matt Fleming
> CommitDate: Mon, 12 Oct
On Wed, Oct 21, 2015 at 02:28:36PM +0900, Minchan Kim wrote:
> I detach this report from my patchset thread because I see below
> problem with removing MADV_FREE related code and I can reproduce
> same oops with MADV_FREE + recent patches(both my SetPageDirty
> and Kirill's pte_mkdirty) within 7
On 2015/10/21 18:01, He Kuang wrote:
hi, Alexei
I've tested the sample in next patch and it works well. I think more
work on
the perf side needs to be done for parsing PERF_COUNT_SW_BPF_OUTPUT
event type,
are you working on that?
Thank you.
We need to add something into parse-event.y/l
> "Bartosz" == Bartosz Golaszewski writes:
> Chips from the at24cs EEPROM series have an additional read-only memory area
> containing a factory pre-programmed serial number. In order to access it, a
> dummy write must be executed before reading the serial number bytes.
> This series
On Wed, Oct 21, 2015 at 11:57:53AM +0200, Tomasz Nowicki wrote:
> On 14.10.2015 08:29, Jiang Liu wrote:
> >Introduce common interface acpi_pci_root_create() and related data
> >structures to create PCI root bus for ACPI PCI host bridges. It will
> >be used to kill duplicated arch specific code for
On 21 October 2015 at 12:25, Sudeep Holla wrote:
>
>
> On 21/10/15 11:21, Nicolas Ferre wrote:
>>
>> Le 21/10/2015 12:10, Sudeep Holla a écrit :
>>>
>>> Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
>>> check for/support the legacy "gpio-key,wakeup" boolean property to
On Wed, Oct 21, 2015 at 11:50:07AM +0200, Geert Uytterhoeven wrote:
> Hi Mike, Russell,
>
> On Tue, Oct 20, 2015 at 2:40 PM, Michael Turquette
> wrote:
> > Why not keep the reference to the struct clk after get'ing it the first
> > time?
>
> And store it where?
Not my problem :)
Users are
Use of resource managed function devm_led_classdev_register to
make initialization path simpler. Also removed redundant remove
function.
Signed-off-by: Fida Mohammad
---
drivers/leds/leds-wrap.c | 26 --
1 file changed, 4 insertions(+), 22 deletions(-)
diff --git
Hi,
during regression tests with libisofs i found two bugs
in fs/isofs, which i reported to Debian
"fs/isofs/util.c iso_date() will map years >= 2028 to 1970"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800627
"fs/isofs/rock.c coarsely truncates file names of 254 or 255 bytes
On (10/21/15 08:57), Steffen Klassert wrote:
> > --- a/net/xfrm/xfrm_user.c
> > +++ b/net/xfrm/xfrm_user.c
> > @@ -2659,7 +2659,7 @@ static int xfrm_notify_sa(struct xfrm_state *x, const
> > struct km_event *c)
> > if (attr == NULL)
> > goto out_free_skb;
> >
> >
On Wednesday 21 October 2015 19:06:52 glen lee wrote:
> Hi arnd,
>
> Thanks for the all the patches.
> About the patch ( use proper naming for global symbols ),
> We are planning to use this driver not only for wilc1000 but also for
> other atmel wireless driver. I'd appreciate if you could use
* Wangnan (F) wrote:
>
>
> On 2015/10/21 18:20, Ingo Molnar wrote:
> >* He Kuang wrote:
> >
> >>ping and add a...@plumgrid.com, what's your opinion on this?
> >Firstly, two days isn't nearly enough for a 'review timeout', secondly, have
> >you
> >seen the kbuild test reports?
> >
>
On Wed, Oct 21, 2015 at 05:50:02PM +0800, Ken Xue wrote:
> On Wed, 2015-10-21 at 12:49 +0300, Mika Westerberg wrote:
> > On Wed, Oct 21, 2015 at 05:37:53PM +0800, Ken Xue wrote:
> > > On Wed, 2015-10-21 at 12:25 +0300, Mika Westerberg wrote:
> > > > On Wed, Oct 21, 2015 at 04:42:23PM +0800, Ken
The thinkpad_acpi driver currently emits error messages on unsupported
brightness interfaces, giving the impression that someone will implement
those. However, this error is spit out on nearly every thinkpad in
production since 2 years now. Furthermore, the backlight interfaces on
those devices
Cc'ing Frederic.
On 20-10-15, 15:47, Yunhong Jiang wrote:
> On Sun, Oct 11, 2015 at 08:12:39PM +0200, Thomas Gleixner wrote:
> > On Mon, 28 Sep 2015, Yunhong Jiang wrote:
> > > static void internal_add_timer(struct tvec_base *base, struct timer_list
> > > *timer)
> > > {
> > > + bool kick_nohz
On Sun, 18 Oct 2015 17:52:56 +0200
Karsten Merker wrote:
> Hello,
>
> this is v3 of my "Input: goodix - add axis swapping and axis inversion
> support" patchset.
>
> The goodix touchscreen driver has gained device-tree support in kernel
> 4.1, but doesn't currently support the
On 2015/10/21 18:20, Ingo Molnar wrote:
* He Kuang wrote:
ping and add a...@plumgrid.com, what's your opinion on this?
Firstly, two days isn't nearly enough for a 'review timeout', secondly, have you
seen the kbuild test reports?
Thirdly, I suspect others will do a deeper review, but even
On Wednesday 21 October 2015 18:30:05 Masahiro Yamada wrote:
> >
> >> I am trying to implement OF_EARLYCON_DECLARE() for that.
> >>
> >> I was just wondering if console_initcall() should work as well.
> >>
> >>
> >> As I said, I noticed the console_initcall() in 8250_core.c
> >> only works on very
Hello,
We are conducting a standard process investigation involving a client who
shares the same name with you and also the circumstances surrounding
investments made by this client. Are you aware of any relative/relation having
the same surname?
This is a confidential message from Foale
On Fri, 2015-10-09 at 19:19 +0100, Will Deacon wrote:
> On Fri, Oct 09, 2015 at 06:41:51PM +0100, Robin Murphy wrote:
> > On 09/10/15 16:57, Will Deacon wrote:
> > >On Tue, Sep 22, 2015 at 03:12:47PM +0100, Yong Wu wrote:
> > >> I would like to show you a problem I met, The recursion here may
于 2015/10/21 17:12, Peter Zijlstra 写道:
> On Tue, Oct 20, 2015 at 03:53:02PM -0700, Alexei Starovoitov wrote:
>> On 10/20/15 12:22 AM, Kaixu Xia wrote:
>>> diff --git a/kernel/events/core.c b/kernel/events/core.c
>>> index b11756f..5219635 100644
>>> --- a/kernel/events/core.c
>>> +++
On Tue, Oct 20, 2015 at 10:19:56AM -0700, Moritz Fischer wrote:
> This gets rid of the code to strip away the header and byteswap,
> as well as the check for the sync word.
>
> Signed-off-by: Moritz Fischer
Simpler is better.
Reviewed-by: Josh Cartwright
Josh
--
To unsubscribe from this
Hi, Namhyung
Thanks for your review.
> On Oct 21, 2015, at 1:20 PM, Namhyung Kim wrote:
>
> On Sun, Oct 04, 2015 at 04:35:05PM +0900, Taeung Song wrote:
>> Which config file is used is decided in only perf_config().
>> And a perf-config command depend on perf_config() to list
>> config
On Wed, Oct 21, 2015 at 09:46:33AM +0100, Lee Jones wrote:
> On Tue, 20 Oct 2015, Andrew F. Davis wrote:
> > I could change the core to be "tps65086-pmic", then call the regulator
> > driver "tps65086-regulator" if this works for you, this seems to be the
> > way new drivers name the regulator
Hi, Anand.
On 10/14/2015 12:58 PM, Anand Moon wrote:
> hi Krzysztof,
>
> On 14 October 2015 at 05:29, Krzysztof Kozlowski
> wrote:
>> On 14.10.2015 01:27, Anand Moon wrote:
>>> Hi Krzysztof,
>>>
>>> On 13 October 2015 at 09:13, Krzysztof Kozlowski
>>> wrote:
On 13.10.2015 12:08,
On Mon, Oct 19, 2015 at 02:24:37PM +0100, Suzuki K. Poulose wrote:
> Resending the series with fixed mail ids.
>
> ---
> This series introduces a new infrastructure to keep track of the CPU
> feature registers on ARMv8-A for arm64 kernel. It provides the safe value
> of a CPU feature register
On 21/10/15 11:21, Nicolas Ferre wrote:
Le 21/10/2015 12:10, Sudeep Holla a écrit :
Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
check for/support the legacy "gpio-key,wakeup" boolean property to
enable gpio buttons as wakeup source, "wakeup-source" is the new
On 21/10/15 11:18, Geert Uytterhoeven wrote:
On Wed, Oct 21, 2015 at 12:10 PM, Sudeep Holla wrote:
Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
check for/support the legacy "gpio-key,wakeup" boolean property to
enable gpio buttons as wakeup source, "wakeup-source"
On Wed, Oct 21, 2015 at 11:03:57AM +0900, Namhyung Kim wrote:
> Hi Jiri,
>
> On Fri, Oct 16, 2015 at 12:40:35PM +0200, Jiri Olsa wrote:
> > hi,
> > sending another version of stat scripting.
> >
> > v4 changes:
> > - added attr update event for event's cpumask
> > - forbig aggregation on
Le 21/10/2015 12:10, Sudeep Holla a écrit :
> Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
> check for/support the legacy "gpio-key,wakeup" boolean property to
> enable gpio buttons as wakeup source, "wakeup-source" is the new
> standard binding.
>
> This patch replaces
On Wed, 2015-10-21 at 10:28 +0300, Mika Westerberg wrote:
> On Wed, Oct 21, 2015 at 09:11:33AM +0800, Ken Xue wrote:
> > On Tue, 2015-10-20 at 14:17 +0300, Mika Westerberg wrote:
> > > On Tue, Oct 20, 2015 at 02:38:01PM +0800, Ken Xue wrote:
> > > > DW I2C driver tries to register a clk from
* He Kuang wrote:
> ping and add a...@plumgrid.com, what's your opinion on this?
Firstly, two days isn't nearly enough for a 'review timeout', secondly, have
you
seen the kbuild test reports?
Thirdly, I suspect others will do a deeper review, but even stylistically the
patch is a bit
On Thu, Sep 17 2015, Vitaly Kuznetsov wrote:
> +
> +static __init void test_string_get_size(void)
> +{
> + test_string_get_size_one(16384, 512, STRING_UNITS_2, "8.00 MiB");
> + test_string_get_size_one(8192, 4096, STRING_UNITS_10, "32.7 MB");
This is a little late, but I just noticed
On Intel Broxton the GPIO hardware consists of several chips that all share
the parent interrupt. It is not possible to handle this by setting chained
handler for each chip (as they will overwrite each other).
To overcome this we need to request the interrupt using devm_request_irq()
and pass
This driver adds pinctrl/GPIO support for Intel Broxton. The GPIO
controller is based on the same hardware design that is already used in
Intel Sunrisepoint so we leverage the core driver here.
Signed-off-by: Mika Westerberg
---
drivers/pinctrl/intel/Kconfig |8 +
On Wed, Oct 21, 2015 at 12:10 PM, Sudeep Holla wrote:
> Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
> check for/support the legacy "gpio-key,wakeup" boolean property to
> enable gpio buttons as wakeup source, "wakeup-source" is the new
> standard binding.
>
> This
Hi,
This series adds pinctrl/GPIO support for Intel Broxton SoC. The GPIO
hardware is based on the same design already found in Intel Skylake
(Sunrisepoint PCH).
This series adds a new driver pinctrl-broxton.c which reuses the existing
Intel pinctrl core functionality and provides Broxton
Currently different drivers use multiple forms of annotating devices
that should be set up as wakeup sources for the system.
This patch adds a separate binding document inorder to standardize and
consolidate to use "wakeup-source" boolean property to mark the devices
as wakeup capable.
Cc: Rob
This patch marks all the reference to the legacy wakeup bindings
and replaces them with the standard "wakeup-source" property.
All these legacy property are also listed under a separate section in
the generic wakeup-source binding document.
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc:
Hi,
This series attempts to consolidate the various existing bindings and
standardize on the widely accepted "wakeup-source" property.
Regards,
Sudeep
Sudeep Holla (19):
Documentation: devicetree: standardize/consolidate on "wakeup-source"
property
Documentation: devicetree: fix
Though the isl12057 rtc driver should and will continue to support the
legacy "isil,irq2-can-wakeup-machine" property to enable RTC as the
wakeup source, we need to add support for the new standard property
"wakeup-source".
This patch adds support for "wakeup-source" property in addition to the
Though the mmc core driver should/will continue to support the legacy
"enable-sdio-wakeup" property to enable SDIO as the wakeup source, we
need to add support for the new standard property "wakeup-source".
This patch adds support for "wakeup-source" property in addition to the
existing
Though the opal rtc driver should and will continue to support the legacy
"has-tpo" property to enable RTC as the wakeup source, we need to add
support for the new standard property "wakeup-source"
This patch adds support for "wakeup-source" property in addition to the
existing "has-tpo"
Keyboard driver for GPIO buttons(gpio-keys) checks for the legacy
"gpio-key,wakeup" boolean property to enable gpio buttons as wakeup
source.
Few dts files assign value "1" to gpio-key,wakeup which is incorrect.
Since the presence of the boolean property indicates it is enabled,
value of "0" or
Keyboard driver for GPIO buttons(gpio-keys) checks for the legacy
"gpio-key,wakeup" boolean property to enable gpio buttons as wakeup
source.
Few dts files assign value "1" to gpio-key,wakeup and in one instance a
value "0" is assigned probably assuming it won't be enabled as a wakeup
source.
Though the mmc core driver should/will continue to support the legacy
"nvidia,wakeup-source" property to enable SDIO as the wakeup source, we
need to add support for the new standard property "wakeup-source".
This patch adds support for "wakeup-source" property in addition to the
existing
Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
check for/support the legacy "gpio-key,wakeup" boolean property to
enable gpio buttons as wakeup source, "wakeup-source" is the new
standard binding.
This patch replaces the legacy "gpio-key,wakeup" with the unified
Though the keyboard and other driver will continue to support the legacy
"gpio-key,wakeup", "linux,wakeup" boolean property to enable the wakeup
source, "wakeup-source" is the new standard binding.
This patch replaces all the legacy wakeup properties with the unified
"wakeup-source" property in
Dear Michael,
On Wed, 21 Oct 2015 02:54:54 -0700
Michael Turquette wrote:
> Quoting Michael Turquette (2015-10-21 02:30:39)
> > Quoting Jisheng Zhang (2015-10-20 04:16:46)
> > > Since we have added the necessary two clks' properties in dts, we can
> > > remove the "sdio" clk's
On Tue, 2015-10-20 at 14:16 -0400, Peter Hurley wrote:
> ECHO is on by default and the cdc-acm driver does not implement the
> put_char() and flush_chars() tty driver methods, which made the
> problem
> _way worse_, since every echoed char is sent as it's own URB.
That can be fixed. How can I
Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
check for/support the legacy "gpio-key,wakeup" boolean property to
enable gpio buttons as wakeup source, "wakeup-source" is the new
standard binding.
This patch replaces the legacy "gpio-key,wakeup" with the unified
Though the keyboard and other driver will continue to support the legacy
"gpio-key,wakeup", "linux,wakeup" boolean property to enable the wakeup
source, "wakeup-source" is the new standard binding.
This patch replaces all the legacy wakeup properties with the unified
"wakeup-source" property in
Though the driver will continue to check for and support the legacy
"isil,irq2-can-wakeup-machine" boolean property to wakeup source,
"wakeup-source" is the new standard binding.
This patch replaces the legacy "isil,irq2-can-wakeup-machine" with the
unified "wakeup-source" property in order to
Though the keyboard and other driver will continue to support the legacy
"gpio-key,wakeup", "linux,input-wakeup" boolean property to enable the
wakeup source, "wakeup-source" is the new standard binding.
This patch replaces all the legacy wakeup properties with the unified
"wakeup-source"
Though the keyboard and other driver will continue to support the legacy
"gpio-key,wakeup", "linux-keypad,wakeup" boolean property to enable the
wakeup source, "wakeup-source" is the new standard binding.
This patch replaces all the legacy wakeup properties with the unified
"wakeup-source"
Though the keyboard and other driver will continue to support the legacy
"gpio-key,wakeup", "nvidia,wakeup-source" boolean property to enable the
wakeup source, "wakeup-source" is the new standard binding.
This patch replaces all the legacy wakeup properties with the unified
"wakeup-source"
Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
check for/support the legacy "gpio-key,wakeup" boolean property to
enable gpio buttons as wakeup source, "wakeup-source" is the new
standard binding.
This patch replaces the legacy "gpio-key,wakeup" with the unified
Though the keyboard and other driver will continue to support the legacy
"gpio-key,wakeup", "linux,wakeup" boolean property to enable the wakeup
source, "wakeup-source" is the new standard binding.
This patch replaces all the legacy wakeup properties with the unified
"wakeup-source" property in
Commit-ID: 79ebdc9536c132eb92b4bcce26daaed7f4bf359e
Gitweb: http://git.kernel.org/tip/79ebdc9536c132eb92b4bcce26daaed7f4bf359e
Author: Borislav Petkov
AuthorDate: Tue, 20 Oct 2015 11:54:49 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:22:13 +0200
MAINTAINERS: Unify the
Commit-ID: c595ac2bac930ce79f336c7a7e45e1ea38abfe16
Gitweb: http://git.kernel.org/tip/c595ac2bac930ce79f336c7a7e45e1ea38abfe16
Author: Borislav Petkov
AuthorDate: Tue, 20 Oct 2015 11:54:48 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:22:12 +0200
x86/microcode/intel:
Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
check for/support the legacy "gpio-key,wakeup" boolean property to
enable gpio buttons as wakeup source, "wakeup-source" is the new
standard binding.
This patch replaces the legacy "gpio-key,wakeup" with the unified
Commit-ID: 6f7fc44bf1eef6768f9dcb527c737ab24a3203ac
Gitweb: http://git.kernel.org/tip/6f7fc44bf1eef6768f9dcb527c737ab24a3203ac
Author: Borislav Petkov
AuthorDate: Tue, 20 Oct 2015 11:54:47 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:22:12 +0200
x86/microcode/amd:
Commit-ID: fe055896c040df571e4ff56fb196d6845130057b
Gitweb: http://git.kernel.org/tip/fe055896c040df571e4ff56fb196d6845130057b
Author: Borislav Petkov
AuthorDate: Tue, 20 Oct 2015 11:54:45 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:22:12 +0200
x86/microcode: Merge
Commit-ID: 6b26e1bf66bb4bf1b1b9b4f27d1f324875689cf0
Gitweb: http://git.kernel.org/tip/6b26e1bf66bb4bf1b1b9b4f27d1f324875689cf0
Author: Borislav Petkov
AuthorDate: Tue, 20 Oct 2015 11:54:46 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:22:12 +0200
x86/microcode: Remove
Logic was changed in kernel 3.4 by commit e9aba5158a80 ("tty: rework pty
count limiting") but still isn't documented. Better late than never.
Signed-off-by: Konstantin Khlebnikov
---
Documentation/filesystems/devpts.txt |9 +
Documentation/sysctl/kernel.txt |7 +++
2
On Wed, 2015-10-21 at 16:59 +1100, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm-current tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
> arch/powerpc/include/asm/pgtable.h: In function 'pte_pgprot':
> arch/powerpc/include/asm/pte-common.h:104:18:
Reserved for ACPI actually means that in such case the GPIO hardware will
not update the interrupt status register (GPI_IS) even if the pin is
configured to trigger an interrupt. It will update GPI_GPE_STS instead and
does not trigger an interrupt.
Allow using such pins as GPIOs, only prevent
Commit-ID: 9a2bc335f100a0f6ee6392b9f97ac4188d84db1d
Gitweb: http://git.kernel.org/tip/9a2bc335f100a0f6ee6392b9f97ac4188d84db1d
Author: Borislav Petkov
AuthorDate: Tue, 20 Oct 2015 11:54:44 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:22:11 +0200
x86/microcode:
Commit-ID: 221836e92cd5664de6fc2f1d836f6343ae5f2e43
Gitweb: http://git.kernel.org/tip/221836e92cd5664de6fc2f1d836f6343ae5f2e43
Author: Borislav Petkov
AuthorDate: Mon, 19 Oct 2015 10:41:17 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:12:56 +0200
x86/Kconfig/cpus:
Commit-ID: 81ffdcdd97d94110627caa81c23d5d780083731d
Gitweb: http://git.kernel.org/tip/81ffdcdd97d94110627caa81c23d5d780083731d
Author: Andi Kleen
AuthorDate: Mon, 19 Oct 2015 11:17:48 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:10:57 +0200
x86/mce: Fix thermal
ping and add a...@plumgrid.com, what's your opinion on this?
On 2015/10/19 13:34, He Kuang wrote:
This patch implements a timer map type inherited from array map. eBPF
programs can deloy a timer by updating an entry in timer map, and
destroy that by deleting the entry. The timer delay time(ns)
Commit-ID: 3d45ac4b35cbdf942f2a45b2b927f2ef6a8bda48
Gitweb: http://git.kernel.org/tip/3d45ac4b35cbdf942f2a45b2b927f2ef6a8bda48
Author: Jan Beulich
AuthorDate: Mon, 19 Oct 2015 04:35:44 -0600
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:17:32 +0200
timers/x86/hpet: Type
Commit-ID: 6f3760570e26eefc214e641b6daeddb7106240bb
Gitweb: http://git.kernel.org/tip/6f3760570e26eefc214e641b6daeddb7106240bb
Author: Borislav Petkov
AuthorDate: Mon, 19 Oct 2015 11:17:46 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Oct 2015 11:10:56 +0200
x86/setup/crash: Check
801 - 900 of 2156 matches
Mail list logo
