Some of kernel driver uses the IIO framework to get the sensor
value via ADC or IIO HW driver. The client driver get iio channel
by iio_channel_get() and release it by calling iio_channel_release().
Add resource managed version (devm_*) of these APIs so that if client
calls the devm_iio_channel_ge
Some of kernel driver uses the IIO framework to get the sensor
value via ADC or IIO HW driver. The client driver get iio channel
by iio_channel_get_all() and release it by calling
iio_channel_release_all().
Add resource managed version (devm_*) of these APIs so that if client
calls the devm_iio_ch
Add following APIs in the list of managed resources of IIO:
devm_iio_channel_get()
devm_iio_channel_get_all()
devm_iio_channel_release()
devm_iio_channel_release_all()
Signed-off-by: Laxman Dewangan
---
Documentation/driver-model/devres.txt | 4
1 file change
Hi Geert,
On Wed, Apr 06, 2016 at 08:51:50AM +0200, Geert Uytterhoeven wrote:
> Hi Yuri,
>
> On Wed, Apr 6, 2016 at 12:08 AM, Yury Norov wrote:
> > This version is rebased on kernel v4.6-rc2, and has fixes in signal
> > subsystem.
> > It works with updated glibc [1] (though very draft), and tes
CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE specifies the default value for the
memory hotplug onlining policy. Add a command line parameter to make it
possible to override the default. It may come handy for debug and testing
purposes.
Signed-off-by: Vitaly Kuznetsov
---
Documentation/kernel-parameters
Introduce config option to set the default value for memory hotplug
onlining policy (/sys/devices/system/memory/auto_online_blocks). The
reason one would want to turn this option on are to have early onlining
for hotpluggable memory available at boot and to not require any userspace
actions to make
This patchset continues the work I started with:
commit 31bc3858ea3ebcc3157b3f5f0e624c5962f5a7a6
Author: Vitaly Kuznetsov
Date: Tue Mar 15 14:56:48 2016 -0700
memory-hotplug: add automatic onlining policy for the newly added memory
Initially I was going to stop there and bring the policy
On Wed, Apr 6, 2016 at 1:31 PM, Laxman Dewangan wrote:
> Some of kernel driver uses the IIO framework to get the sensor
> value via ADC or IIO HW driver. The client driver get iio channel
> by iio_channel_get() and release it by calling iio_channel_release().
>
> Add resource managed version (devm
On Tue, 5 Apr 2016 21:46:44 +0800
Yongji Xie wrote:
> This patch enables mmapping MSI-X tables if
> hardware supports interrupt remapping which
> can ensure that a given pci device can only
> shoot the MSIs assigned for it.
>
> Signed-off-by: Yongji Xie
> ---
> drivers/vfio/pci/vfio_pci.c
Hi Daniel,
On Wednesday 06 April 2016 07:19 PM, Daniel Baluta wrote:
On Wed, Apr 6, 2016 at 1:31 PM, Laxman Dewangan wrote:
Some of kernel driver uses the IIO framework to get the sensor
value via ADC or IIO HW driver. The client driver get iio channel
by iio_channel_get() and release it by c
On Wed, 6 Apr 2016 15:45:10 +0200 Vitaly Kuznetsov wrote:
> This patchset continues the work I started with:
>
> commit 31bc3858ea3ebcc3157b3f5f0e624c5962f5a7a6
> Author: Vitaly Kuznetsov
> Date: Tue Mar 15 14:56:48 2016 -0700
>
> memory-hotplug: add automatic onlining policy for the ne
When building with both CONFIG_HIBERNATION and CONFIG_RANDOMIZE_BASE,
one or the other must be chosen at boot-time. Until now, hibernation
was selected when no choice was made on the command line.
To make the security benefits of kASLR more widely available to end
users (since the use of hibernati
Hi!
> When building with both CONFIG_HIBERNATION and CONFIG_RANDOMIZE_BASE,
> one or the other must be chosen at boot-time. Until now, hibernation
> was selected when no choice was made on the command line.
>
> To make the security benefits of kASLR more widely available to end
> users (since the
On Wed, Apr 6, 2016 at 1:17 PM, Pavel Machek wrote:
>
> Why is kASLR incompatible with hibernation? We can hibernate have
> 4.3 kernel resume hibernation image of 4.2 kernel (on x86-64, and I
> have patches for x86). Resuming kernel with different randomization
> does not look that much different.
On Wed, Apr 6, 2016 at 1:56 PM, Linus Torvalds
wrote:
> On Wed, Apr 6, 2016 at 1:17 PM, Pavel Machek wrote:
>>
>> Why is kASLR incompatible with hibernation? We can hibernate have
>> 4.3 kernel resume hibernation image of 4.2 kernel (on x86-64, and I
>> have patches for x86). Resuming kernel with
On 04/06/2016 02:21 PM, Rafael J. Wysocki wrote:
On Wed, Apr 6, 2016 at 10:30 PM, Saravana Kannan wrote:
On 09/09/2015 05:53 PM, Rafael J. Wysocki wrote:
Hi,
On Thu, Sep 10, 2015 at 2:39 AM, Viresh Kumar
wrote:
On 10-09-15, 01:26, Rafael J. Wysocki wrote:
On Monday, August 03, 2015 08:3
On Wed, Apr 6, 2016 at 11:29 PM, Saravana Kannan wrote:
> On 04/06/2016 02:21 PM, Rafael J. Wysocki wrote:
>>
>> On Wed, Apr 6, 2016 at 10:30 PM, Saravana Kannan
>> wrote:
>>>
>>> On 09/09/2015 05:53 PM, Rafael J. Wysocki wrote:
[cut]
>>
>> Well, nobody was using that event.
>>
>
> True, b
* Kees Cook wrote:
> On Wed, Apr 6, 2016 at 1:56 PM, Linus Torvalds
> wrote:
> > On Wed, Apr 6, 2016 at 1:17 PM, Pavel Machek wrote:
> >>
> >> Why is kASLR incompatible with hibernation? We can hibernate have
> >> 4.3 kernel resume hibernation image of 4.2 kernel (on x86-64, and I
> >> have pa
On Wed, Apr 6, 2016 at 9:44 PM, Kees Cook wrote:
> When building with both CONFIG_HIBERNATION and CONFIG_RANDOMIZE_BASE,
> one or the other must be chosen at boot-time. Until now, hibernation
> was selected when no choice was made on the command line.
>
> To make the security benefits of kASLR mor
On 04/06/2016 02:45 PM, Rafael J. Wysocki wrote:
On Wed, Apr 6, 2016 at 11:29 PM, Saravana Kannan wrote:
On 04/06/2016 02:21 PM, Rafael J. Wysocki wrote:
On Wed, Apr 6, 2016 at 10:30 PM, Saravana Kannan
wrote:
On 09/09/2015 05:53 PM, Rafael J. Wysocki wrote:
[cut]
Well, nobody was u
* Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
> > On Wed, Apr 6, 2016 at 1:56 PM, Linus Torvalds
> > wrote:
> > > On Wed, Apr 6, 2016 at 1:17 PM, Pavel Machek wrote:
> > >>
> > >> Why is kASLR incompatible with hibernation? We can hibernate have
> > >> 4.3 kernel resume hibernation image of
* Rafael J. Wysocki wrote:
> On Wed, Apr 6, 2016 at 9:44 PM, Kees Cook wrote:
> > When building with both CONFIG_HIBERNATION and CONFIG_RANDOMIZE_BASE,
> > one or the other must be chosen at boot-time. Until now, hibernation
> > was selected when no choice was made on the command line.
> >
> >
On Wed, Apr 6, 2016 at 11:56 PM, Ingo Molnar wrote:
>
> * Rafael J. Wysocki wrote:
>
>> On Wed, Apr 6, 2016 at 9:44 PM, Kees Cook wrote:
>> > When building with both CONFIG_HIBERNATION and CONFIG_RANDOMIZE_BASE,
>> > one or the other must be chosen at boot-time. Until now, hibernation
>> > was s
On Wed, 6 Apr 2016, Andrew Morton wrote:
> > This patchset continues the work I started with:
> >
> > commit 31bc3858ea3ebcc3157b3f5f0e624c5962f5a7a6
> > Author: Vitaly Kuznetsov
> > Date: Tue Mar 15 14:56:48 2016 -0700
> >
> > memory-hotplug: add automatic onlining policy for the newly a
On Wed, Apr 6, 2016 at 3:04 PM, Rafael J. Wysocki wrote:
> On Wed, Apr 6, 2016 at 11:56 PM, Ingo Molnar wrote:
>>
>> * Rafael J. Wysocki wrote:
>>
>>> On Wed, Apr 6, 2016 at 9:44 PM, Kees Cook wrote:
>>> > When building with both CONFIG_HIBERNATION and CONFIG_RANDOMIZE_BASE,
>>> > one or the ot
On Wed, Apr 6, 2016 at 11:52 PM, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
>>
>> * Kees Cook wrote:
>>
>> > On Wed, Apr 6, 2016 at 1:56 PM, Linus Torvalds
>> > wrote:
>> > > On Wed, Apr 6, 2016 at 1:17 PM, Pavel Machek wrote:
>> > >>
>> > >> Why is kASLR incompatible with hibernation? We c
On wo, 2016-04-06 at 15:16 -0700, Kees Cook wrote:
> And it seems like Fedora either doesn't either, or has a lot of people
> for whom it doesn't work:
> https://bugzilla.redhat.com/show_bug.cgi?id=1206936
> https://bugzilla.redhat.com/show_bug.cgi?id=1224151
> http://blog.kriptonium.com/2015/12/fe
* Kees Cook wrote:
> >> I don't think this is a good idea, as it turns off emergency hibernation
> >> of
> >> laptops - many desktop distros support it by default.
> >
> > Right, I forgot about this one.
>
> When I last checked Ubuntu doesn't enable hibernation by default any more:
> https:/
Hi Boris,
On 04/05/2016 12:31 AM, Borislav Petkov wrote:
On Tue, Apr 05, 2016 at 12:25:33AM -0500, Thor Thayer wrote:
I realize that I'm not calling iounmap(ecc_block_base) and I'll fix that in
the next revision with a goto.
I'm assuming nothing else changes. Because I've applied 1-4 already.
* Rafael J. Wysocki wrote:
> [...]
>
> One of the weak points is the final jump, because it has to be done to the
> physical location of the image kernel's entry point even though the virtual
> addresses of it may differ between the boot and the image kernels. The seed
> is
> not needed fo
Commit 'b09d6d991' removes include/linux/clk-private.h and
re-arranges the clock related structures contained in it in
different files. The documentation has not been updated
accordingly, thus it wasn't anymore consistent.
Place the structures referenced by Documentation/clk.txt in the
correct fil
This patchset adds support for the CoreSight STM IP block.
Changes from V4:
- Rebased the whole patch set onto [4] (v4.6-rc1).
- Made a few minor modifications according to the code changes since v4.5.
- Replaced the original 1/4 with a new patch the Alex provided.
- Another new patch 2/4 in t
From: Pratik Patel
This driver adds support for the STM CoreSight IP block, allowing any
system compoment (HW or SW) to log and aggregate messages via a
single entity.
The CoreSight STM exposes an application defined number of channels
called stimulus port. Configuration is done using entries i
From: Mathieu Poirier
The System Trace Macrocell (STM) is an IP block falling under the
CoreSight umbrella. It's main purpose it so expose stimulus channels
to any system component for the purpose of information logging.
Bindings for this IP block adds a couple of items to the current
mandatory
From: Alexander Shishkin
Some STM devices adjust software assigned master numbers depending on
the trace source and its runtime state and whatnot. This patch adds
a sysfs attribute to inform the trace-side software that master numbers
assigned to software sources will not match those in the STP s
From: Mathieu Poirier
>From a core framework point of view an STM device is a source that is
treated the same way as any other tracers. Unlike tracers though STM
devices are not associated with a CPU. As such it doesn't make sense
to associate the path from an STM device to its sink with a per-
36 matches
Mail list logo
