On Mon, Nov 03, 2014 at 03:48:56PM +0100, Mike Looijmans wrote:
> On 11/03/2014 01:09 PM, Mark Brown wrote:
> >No function calls, just use regulators_node. What is unclear about the
> >functionality?
> I don't understand what you mean by "regulators_node".
> "grep -R regulators_node *" in the
Hi Joonsoo,
On Mon, Nov 03, 2014 at 05:02:08PM +0900, Joonsoo Kim wrote:
> On Sat, Nov 01, 2014 at 11:15:54PM -0400, Johannes Weiner wrote:
> > Memory cgroups used to have 5 per-page pointers. To allow users to
> > disable that amount of overhead during runtime, those pointers were
> > allocated
On Mon, 2014-11-03 at 15:17 +0100, Takashi Iwai wrote:
> At Mon, 3 Nov 2014 16:04:12 +0530,
> Sudip Mukherjee wrote:
> >
> > added reference of struct echoaudio to free_firmware function.
> > this structure will be later used to get a reference of the card
> > when converting snd_printk to dev_*
On Friday 31 October 2014 23:53:28 Rafael J. Wysocki wrote:
> On Saturday, November 01, 2014 05:13:45 AM Rob Herring wrote:
> > On Fri, Oct 31, 2014 at 6:59 AM, Gilad Avidov
> > wrote:
> > >
> > > Device-Tree compact API
> > >
> > >
> > > Common code seen in driver’s
On Mon, 27 Oct 2014, Vignesh R wrote:
> From: Brad Griffis
>
> TSC interrupt handler had udelay to avoid reporting of false pen-up
> interrupt to user space. This patch implements workaround suggesting in
> Advisory 1.0.31 of silicon errata for am335x, thus eliminating udelay
> and touchscreen
On Mon, 2014-11-03 at 14:48 +, Tomeu Vizoso wrote:
> On 29 September 2014 17:53, Pawel Moll wrote:
> > On Mon, 2014-09-29 at 16:32 +0100, Peter Zijlstra wrote:
> >> Also none of the many words above describe
> >> PERF_SAMPLE_USERSPACE_EVENT(), wth is that about?
> >
> > Hopefully description
On Sunday, November 02, 2014 08:49:37 PM Darren Hart wrote:
>
> On 11/1/14 4:11, Grant Likely wrote:
> > On Tue, 28 Oct 2014 22:59:57 +0100
> > , "Rafael J. Wysocki"
> > wrote:
> >> On Tuesday, October 28, 2014 01:15:27 PM Mika Westerberg wrote:
> >>> acpi_dev_add_driver_gpios() makes it
Hi everyone,
I was playing with iperf on my Cubietruck today when I hit this lockdep
report/breakage on stmmac. It seems to be fairly reproducible by
1) Being on a GbE network
2) "iperf -s" on the stmmmac device
3) "iperf -c -d -P 5" on some other device on the LAN
Here it goes:
On Mon, Nov 3, 2014 at 10:54 PM, Jiri Olsa wrote:
> On Mon, Nov 03, 2014 at 04:27:52PM +0900, Namhyung Kim wrote:
>
> SNIP
>
>> #
>> # Overhead Command Shared ObjectSymbol
>> # ... ...
>>
Hi Jiri,
On Mon, Nov 3, 2014 at 10:51 PM, Jiri Olsa wrote:
> On Mon, Nov 03, 2014 at 04:27:51PM +0900, Namhyung Kim wrote:
>
> SNIP
>
>> +static int decompress_dummy(const char *input __maybe_unused,
>> + int output __maybe_unused)
>> +{
>> + return -1;
>> +}
>> +
>>
On Mon, Nov 03, 2014 at 11:24:02AM +0200, Mika Westerberg wrote:
> On Fri, Oct 31, 2014 at 11:45:09AM -0700, David Cohen wrote:
> > > I think adding the module exit + allowing this driver to be a module
> > > would be a good approach. Then we don't need to force generic x86 kernel
> > > binaries
On Fri, 24 Oct 2014, Dmitry Eremin-Solenikov wrote:
> Some boards with TC6393XB chip require full state restore during system
> resume thanks to chip's VCC being cut off during suspend (Sharp SL-6000
> tosa is one of them). Failing to do so would result in ohci Oops on
> resume due to internal
> > @@ -1164,6 +1164,9 @@ int cmd_diff(int argc, const char **argv, const
> char *prefix __maybe_unused)
> > if (setup_sorting() < 0)
> > usage_with_options(diff_usage, options);
> >
> > + if (sort__has_sym_name)
> > + tool.mmap2 = perf_event__process_mmap2;
>
> why
On Mon, Nov 03, 2014 at 02:57:31AM -0800, tip-bot for Jiang Liu wrote:
> Commit-ID: e22ce93870deae0e9a54e1539f0088538f187780
> Gitweb: http://git.kernel.org/tip/e22ce93870deae0e9a54e1539f0088538f187780
> Author: Jiang Liu
> AuthorDate: Mon, 27 Oct 2014 13:21:34 +0800
> Committer: Thomas
Some regulators can run on different operating modes (opmodes). This
allows systems to choose the most efficient opmode for each regulator.
This patch builds on top of (291d761 regulator: Document binding for
regulator suspend state for PM state) adding a regulator-initial-mode
DT property to
Drivers can use the of_regulator_match() function to parse the regulator
init_data from DT. A match table is used to specify the name of the node
containing the regulators, the device node and to return the init_data
to the caller.
But also the static regulator descriptor is needed to correctly
On Mon, Nov 03, 2014 at 06:34:13AM -0800, Jeff Kirsher wrote:
> From: Mark Rustad
>
> The macro __compiletime_error_fallback has an error in that it
> lacks parens around the expansion of an expression. It also
> lacks a conversion to a boolean value. The first problem can
> result in a
On 11/03/2014 01:09 PM, Mark Brown wrote:
On Mon, Nov 03, 2014 at 09:10:08AM +0100, Mike Looijmans wrote:
On 10/30/2014 05:51 PM, Mark Brown wrote:
+ np_child = of_get_child_by_name(np_regulators,
+ ltc3562_regulators[i].name);
+ if
On Mon, Nov 03, 2014 at 03:18:29PM +0100, Stephan Mueller wrote:
>
> > > + * CRYPTO_ALG_TYPE_DIGESTRaw message digest
> > > + * CRYPTO_ALG_TYPE_HASH Alias for CRYPTO_ALG_TYPE_DIGEST
> > > + * CRYPTO_ALG_TYPE_SHASH Synchronous multi-block hash
> > > + * CRYPTO_ALG_TYPE_AHASH
On 29 September 2014 17:53, Pawel Moll wrote:
> On Mon, 2014-09-29 at 16:32 +0100, Peter Zijlstra wrote:
>> Also none of the many words above describe
>> PERF_SAMPLE_USERSPACE_EVENT(), wth is that about?
>
> Hopefully description of the v2 makes better job in this:
>
>
Hi Linus,
this kernel cycle has been calm for both pin control and GPIO
so far but here are three pin control patches for you anyway,
only really dealing with Baytrail.
Please pull them in!
Yours,
Linus Walleij
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
El 03/11/14 a las 11:39, Giuseppe CAVALLARO escibió:
Hello Emilio
I have a subset of new patches to review and fix locks in the
driver. I will plan to send them in the next days.
Great then :) Please Cc: me on the patches when you send them
Cheers,
Emilio
--
To unsubscribe from this list:
On Mon, Nov 03, 2014 at 03:18:29PM +0100, Stephan Mueller wrote:
>
> > > + * CRYPTO_ALG_TYPE_CIPHERRaw block cipher
> > > + * CRYPTO_ALG_TYPE_COMPRESS Compression
> > > + * CRYPTO_ALG_TYPE_AEAD Authenticated Encryption with
> Associated Data
> > > (MAC) + *
All function dealing with operating modes use unsigned int for modes
so change max77802_map_mode() function signature for consistency.
Signed-off-by: Javier Martinez Canillas
---
drivers/regulator/max77802.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The struct of_regulator_match rmatch[] is declared as a non-static local
variable so the structure members are not auto-initialized.
Initialize the array at declaration time to avoid the structure members
values to be indeterminate and have sane defaults instead.
Signed-off-by: Javier Martinez
The struct of_regulator_match is declared as a non-static local variable
so the structure members are not auto-initialized.
Initialize the struct at declaration time to avoid the structure members
values to be indeterminate and have sane defaults instead.
Signed-off-by: Javier Martinez Canillas
The struct of_regulator_match rmatch[] is declared as a non-static local
variable so the structure members are not auto-initialized.
Initialize the array at declaration time to avoid the structure members
values to be indeterminate and have sane defaults instead.
Signed-off-by: Javier Martinez
Some regulators from the max77802 PMIC support to be configured in one
of two operating mode: Output ON (normal) and Output On Low Power Mode.
Not all regulators support these two modes and for some of them, the
mode can be changed while the system is running in normal operation
while others only
The struct of_regulator_match is declared as a non-static local variable
so the structure members are not auto-initialized.
Initialize the struct at declaration time to avoid the structure members
values to be indeterminate and have sane defaults instead.
Signed-off-by: Javier Martinez Canillas
The regulator core now has support to choose if a regulator
has to be enabled or disabled during system suspend and also
the supports changing the regulator operating mode during
runtime and when the system enters into sleep mode.
To lower power during suspend, configure the regulators state
Hi Nishant,
On 10/21/2014 05:38 PM, Nishanth Menon wrote:
> DRA7 Data Manual (SPRS857L - August 2014) section 4.1.1 states: "All
> unused power supply balls must be supplied with the voltages specified
> in the Section 5.2, Recommended Operating Conditions".
>
> This implies that all unused
The of_get_regulator_init_data() function is used to extract the regulator
init_data but information on how to extract certain data is defined in the
static regulator descriptor (e.g: how to map the hardware operating modes).
Add a const struct regulator_desc * parameter to the function signature
The regulator-initial-mode and regulator-mode DT properties allows to
configure the regulator operating modes at startup or when a system
enters into a susend state.
But these properties use as valid values the operating modes supported
by each device while the core deals with the standard
The struct of_regulator_match rmatch[] is declared as a non-static local
variable so the structure members are not auto-initialized.
Initialize the array at declaration time to avoid the structure members
values to be indeterminate and have sane defaults instead.
Signed-off-by: Javier Martinez
The state of a PWM output is not clearly defined after resume. Some PWM
drivers do not restore the duty cycle upon resume, thus it is necessary to
manually restore the correct value.
Signed-off-by: Kamil Debski
---
drivers/hwmon/pwm-fan.c | 13 ++---
1 file changed, 10 insertions(+),
Add pwm-fan node to the Odroid-U3 board file to enable PWM control of the
cooling fan.
Signed-off-by: Kamil Debski
---
arch/arm/boot/dts/exynos4412-odroidu3.dts | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4412-odroidu3.dts
Some regulators support their operating mode to be changed on startup
or by consumers when the system is running while others only support
their operating mode to be changed while the system has entered in a
suspend state.
The regulator Device Tree binding documents a set of properties to
The max77802 PMIC regulators output can be configured in one of two
modes: Output ON (normal) and Output ON in Low Power Mode. Some of
the regulators support their operating mode to be changed on startup
or by consumers when the system is running while others only support
their operating mode to
Hello Mark,
This is the fourth version of the series that adds operating modes
support for the regulators in the max77802 PMIC. This version uses
the standard suspend states bindings and the opmodes are parsed by
the regulator core while drivers only define a translation function
to map between
On Mon, Nov 3, 2014 at 8:28 AM, bpqw wrote:
>>This patch is used to add vendor prefix for
>>Micron Technology Inc in the vendor-prefixes.txt file.
>
>>Micron Technology, Inc. is an American
>>multinational corporation based in Boise,
>>Idaho, best known for producing many forms
>>of semiconductor
Hello Emilio
I have a subset of new patches to review and fix locks in the
driver. I will plan to send them in the next days.
Sincerely
Peppe
On 11/3/2014 3:36 PM, Emilio López wrote:
Hi everyone,
I was playing with iperf on my Cubietruck today when I hit this lockdep
report/breakage on
On Sun, Nov 2, 2014 at 9:20 PM, Sören Brinkmann
wrote:
(...)
> common {
> groups = "uart1_10_grp";
> function = "uart1";
> bias-pull-up = <0>;
> slew-rate = <0>;
>
On Sat, 1 Nov 2014 18:21:30 -0700
Greg Kroah-Hartman wrote:
> Here's some reasons why I feel it is better to have kdbus in the kernel
> rather than trying to implement the same thing in a userspace daemon:
No - these are reasons to have *something* in the kernel. I think it
would be far more
On Mon, Nov 03, 2014 at 03:07:05PM +0100, Krzysztof Kozlowski wrote:
> Driver allocated on stack struct regulator_config but didn't initialize
> it fully. Few fields (driver_data, ena_gpio) were left untouched. This
> lead to using random ena_gpio values as GPIOs for max77693 regulators.
Applied,
On Mon, 2014-11-03 at 17:20 +0800, Ian Kent wrote:
> On Mon, 2014-11-03 at 00:25 -0800, Joe Perches wrote:
> > On Mon, 2014-11-03 at 16:12 +0800, Ian Kent wrote:
> > > Use the AUTOFS_*() print defines instead of raw printks.
Hi again Ian
> > It's probably better to simply use
> > #define
From: Mark Rustad
The macro __compiletime_error_fallback has an error in that it
lacks parens around the expansion of an expression. It also
lacks a conversion to a boolean value. The first problem can
result in a mis-evaluation. The second problem can also result
in an error if the value comes
There have been several times where I have had to rebuild a kernel to
cause a panic when hitting a WARN() in the code in order to get a crash
dump from a system. Sometimes this is easy to do, other times (such as
in the case of a remote admin) it is not trivial to send new images to the
user.
A
>This patch is used to add vendor prefix for
>Micron Technology Inc in the vendor-prefixes.txt file.
>Micron Technology, Inc. is an American
>multinational corporation based in Boise,
>Idaho, best known for producing many forms
>of semiconductor devices. This includes DRAM,
>SDRAM, flash
On Sat, 1 Nov 2014 01:01:57 +0900
Masanari Iida wrote:
> This patch add 1GB large page support information on
> x86_64 architecture in Documentation/vm/hugetlbpage.txt.
>
> Signed-off-by: Masanari Iida
> ---
> Documentation/vm/hugetlbpage.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1
This patch is used to add vendor prefix
for Micron Technology Inc in the
vendor-prefixes.txt file.
Micron Technology, Inc. is an American
multinational corporation based in Boise,
Idaho, best known for producing many forms
of semiconductor devices. This includes DRAM,
SDRAM, flash memory,
On Mon, Nov 3, 2014 at 4:27 PM, SF Markus Elfring
wrote:
>> dput() also checks for NULL argument, but the check is wrapped into
>> unlikely(), which is why I presume it wasn't picked up. It would be
>> great if you could improve your coccinelle script to handle
>> {un,}likely() as well.
>
>
Am Montag, 3. November 2014, 08:34:39 schrieb Jonathan Corbet:
Hi Jonathan,
> On Sun, 02 Nov 2014 21:35:11 +0100
>
> Stephan Mueller wrote:
> > The design of the kernel crypto API as well as hints to program with
> > the kernel crypto API are given.
>
> Cool to see this, thanks. Please
> > It's a reasonable ask but answers even if available are likely
> > to be things like "because GPE36" and GPE36 will just be some connection
> > to something that could be anything from a lid switch to a light sensor
> > or even a smart wifi chip deciding it wants the CPU to help out because
>
At Mon, 3 Nov 2014 16:04:12 +0530,
Sudip Mukherjee wrote:
>
> added reference of struct echoaudio to free_firmware function.
> this structure will be later used to get a reference of the card
> when converting snd_printk to dev_* in the next patch of the series.
>
> Signed-off-by: Sudip
At Mon, 03 Nov 2014 15:10:40 +0100,
SF Markus Elfring wrote:
>
> > Your patch can't be applied cleanly due to your MUA breaking the
> > lines. Please fix your MUA setup, or use an attachment if it's
> > impossible, and resend the patch.
>
> Thanks for your feedback.
>
> Does this example show
On Mon, Nov 03, 2014 at 12:10:49PM +, One Thousand Gnomes wrote:
> On Sun, 2 Nov 2014 09:33:01 -0800
> Josh Triplett wrote:
>
> > On the vast majority of modern systems, no processes will use the
> > userspsace IO syscalls, iopl and ioperm. Add a new config option,
> > CONFIG_X86_IOPORT, to
On 11/03/2014 02:42 PM, Laurent Pinchart wrote:
> On Monday 03 November 2014 14:36:26 Hans Verkuil wrote:
>> On 11/03/2014 02:13 PM, Laurent Pinchart wrote:
>>> Hi Jean-Michel,
>>>
>>> Thank you for the patch.
>>
>>> On Wednesday 10 September 2014 11:43:54 Jean-Michel Hautbois wrote:
>>
>>
> Your patch can't be applied cleanly due to your MUA breaking the
> lines. Please fix your MUA setup, or use an attachment if it's
> impossible, and resend the patch.
Thanks for your feedback.
Does this example show a conflict between long comments like
"snd_emu10k1_ctl_private_free( ...
On Sat, Nov 1, 2014 at 8:03 AM, Alexandre Courbot wrote:
> The issue with this patch is its use of kzalloc() in gpiochip_add(), a
> function potentially called during early boot, before kzalloc() becomes
> usable. Hence its [RFC] status until we can find a solution for this or
> agree that this
On 03/11/14 09:50, Marc Zyngier wrote:
>> @@ -843,10 +847,14 @@ static int gic_irq_domain_alloc(struct irq_domain
>> *domain, unsigned int virq,
>> unsigned int type = IRQ_TYPE_NONE;
>> struct of_phandle_args *irq_data = arg;
>>
>> - ret = gic_irq_domain_xlate(domain,
Hi Boris, Laurent,
My apologies, I missed this patch when it was posted.
First of all, please convert all existing kernel drivers that use V4L2_MBUS_FMT
to the new macro. It's easy to automate, and I see no reason why we shouldn't
do this.
If you don't do that now, then we'll be stuck with two
Driver allocated on stack struct regulator_config but didn't initialize
it fully. Few fields (driver_data, ena_gpio) were left untouched. This
lead to using random ena_gpio values as GPIOs for max77693 regulators.
On occasion these values could match real GPIO numbers leading to
interfering with
On 11/03/2014 02:03 AM, Ming Lei wrote:
> On Sun, Nov 2, 2014 at 9:00 PM, Richard Weinberger wrote:
>> Convert the driver to blk-mq.
>
> It is always helpful to include some performance comparison data(
> randrw, rw) between blk-mq and non-mq.
>
UBI block support is read-only for now so you'll
If there is more then one UBI device mounted, there is no way to
distinguish between messages from different UBI devices.
Add device number to all ubi layer message types.
The R/O block driver messages were replaced by pr_* since
ubi_device structure is not used by it.
Amended a bit by Artem.
On Mon, 2014-11-03 at 11:32 +0100, Guillaume Nault wrote:
> On Sat, Nov 01, 2014 at 10:28:02PM +, Ben Hutchings wrote:
> > This is the start of the stable review cycle for the 3.2.64 release.
> > There are 102 patches in this series, which will be posted as responses
> > to this one. If
Hi Martin,
On Sat, Nov 1, 2014 at 6:51 PM, Martin Mares wrote:
> The support for hwdb has finally landed in mainline pciutils.
>
> I have modified your patch to bring it closer to the rest of device
> naming logic. Namely:
Great! Thanks for merging this, and for working on it.
> Aside of the
On Mon, Nov 03, 2014 at 04:27:52PM +0900, Namhyung Kim wrote:
SNIP
> #
> # Overhead Command Shared ObjectSymbol
> # ... ...
> ..
> #
>
>0.04%
On Mon, Nov 03, 2014 at 04:27:51PM +0900, Namhyung Kim wrote:
SNIP
> +static int decompress_dummy(const char *input __maybe_unused,
> + int output __maybe_unused)
> +{
> + return -1;
> +}
> +
> +static const struct {
> + const char *fmt;
> + int
On Sun, 2014-11-02 at 10:44 +0200, Nadav Amit wrote:
> Sorry, but this patch is incomplete due to a bug.
> The following patch - http://www.spinics.net/lists/kvm/msg109664.html - is
> needed as well (on top of the previous one).
Thanks, I've added that (commit 7e466f6c).
Ben.
> Nadav
>
>
On Fri, Oct 31, 2014 at 12:40 PM, Mika Westerberg
wrote:
> Commit 21f2aae91e902aad ("leds: leds-gpio: Add support for GPIO
> descriptors") already converted most of the driver to use GPIO descriptors.
> What is still missing is the platform specific hook gpio_blink_set() and
> board files which
On Sun, 2014-11-02 at 10:03 +0100, Paolo Bonzini wrote:
> You can just use the same scheme as your patch 88/102:
Why is that? Why should I not use the upstream version?
Ben.
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index 685b8448d6e2..bd8cc9055fe2 100644
> ---
On 10/30/2014 08:25 PM, Rusty Russell wrote:
> Prarit Bhargava writes:
>> On 10/22/2014 12:27 AM, Rusty Russell wrote:
>>> Prarit Bhargava writes:
There have been several times where I have had to rebuild a kernel to
cause a panic when hitting a WARN() in the code in order to get a
On Monday 03 November 2014 14:36:26 Hans Verkuil wrote:
> On 11/03/2014 02:13 PM, Laurent Pinchart wrote:
> > Hi Jean-Michel,
> >
> > Thank you for the patch.
>
> > On Wednesday 10 September 2014 11:43:54 Jean-Michel Hautbois wrote:
>
>
> >> +static int lmh0395_s_routing(struct v4l2_subdev
On Mon, Oct 13, 2014 at 04:47:33PM +0200, Mark Brown wrote:
> On Wed, Oct 08, 2014 at 03:47:07PM +0200, Markus Pargmann wrote:
> > Use gpio_is_valid instead of an explicit comparison with 0.
> >
> > Signed-off-by: Markus Pargmann
> > ---
> > drivers/regulator/fixed.c | 2 +-
> > 1 file changed,
On 11/03/2014 02:13 PM, Laurent Pinchart wrote:
> Hi Jean-Michel,
>
> Thank you for the patch.
>
> On Wednesday 10 September 2014 11:43:54 Jean-Michel Hautbois wrote:
>
>> +static int lmh0395_s_routing(struct v4l2_subdev *sd, u32 input, u32 output,
>> +u32 config)
On Sun, 02 Nov 2014 21:35:11 +0100
Stephan Mueller wrote:
> The design of the kernel crypto API as well as hints to program with
> the kernel crypto API are given.
Cool to see this, thanks. Please forgive me if I go into full grumpy
editor mode here. There's a lot of good information here,
On 10/30/2014 09:58 PM, Hedi Berriche wrote:
> On Thu, Oct 30, 2014 at 17:06 Prarit Bhargava wrote:
> | There have been several times where I have had to rebuild a kernel to
> | cause a panic when hitting a WARN() in the code in order to get a crash
> | dump from a system. Sometimes this is
On Fri, 31 Oct 2014, Alan Wu wrote:
> From: alanwu
>
> Surface Pro 3 Type Cover that works with Ubuntu (and possibly Arch) from this
> thread. Both trackpad and keyboard work after compiling my own kernel.
> http://ubuntuforums.org/showthread.php?t=2231207=2=44910e0c56047e4f93dfd9fea58121ef
>
> dput() also checks for NULL argument, but the check is wrapped into
> unlikely(), which is why I presume it wasn't picked up. It would be
> great if you could improve your coccinelle script to handle
> {un,}likely() as well.
Thanks for your suggestion.
Should I consider any more fine-tuning
On Mon, Nov 03, 2014 at 01:07:02PM +0100, Krzysztof Kozlowski wrote:
> On pią, 2014-10-31 at 10:32 +, Mark Brown wrote:
> > We could always add a callback for the driver to handle any custom
> > properties... one of the advantages of an OS like Linux is that we can
> > improve the core code.
On Thu, Oct 30, 2014 at 8:48 PM, Antoine Tenart
wrote:
> Maybe the of_pinctrl_utils_node_is_mux/config() solution is more
> appropriate to avoid having a confusing function. Plus we would have a
> dedicated of_pinctrl_utils_read_pins() function.
>
> I think I prefer the second solution because
Hi,
Sorry for the delay, holiday and so on.
On Mon, Oct 13, 2014 at 04:42:35PM +0200, Mark Brown wrote:
> On Wed, Oct 08, 2014 at 03:47:06PM +0200, Markus Pargmann wrote:
>
> > --- a/drivers/regulator/max8952.c
> > +++ b/drivers/regulator/max8952.c
> > @@ -225,6 +225,8 @@ static int
On Sat, Oct 25, 2014 at 12:05 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Provide a way for device drivers using GPIOs described by ACPI
> GpioIo resources in _CRS to tell the GPIO subsystem what names
> (connection IDs) to associate with specific GPIO pins defined
> in there.
>
Em Sun, 12 Oct 2014 22:01:53 +0200
Beniamino Galvani escreveu:
> Amlogic Meson SoCs include a infrared remote control receiver that can
> operate in two modes: in "NEC" mode the hardware can decode frames
> using the NEC IR protocol, while in "general" mode the receiver simply
> reports the
Hi Jean-Michel,
Thank you for the patch.
On Wednesday 10 September 2014 11:43:54 Jean-Michel Hautbois wrote:
> This device is a SPI based device from TI.
> It is a 3 Gbps HD/SD SDI Dual Output Low Power
> Extended Reach Adaptive Cable Equalizer.
>
> LMH0395 enables the use of up to two outputs.
On Thu, Oct 30, 2014 at 04:09:45PM +0200, Adrian Hunter wrote:
> Enhance the thread stack to output detailed information
> about paired calls and returns.
>
> The enhanced processing consumes sample information via
> thread_stack__process() and outputs information about
> paired calls / returns
On Mon, 03 Nov 2014, Andy Shevchenko wrote:
> On Mon, 2014-11-03 at 15:39 +0800, Raymond Tan wrote:
> > In Quark X1000, there's a single PCI device that provides both
> > an I2C controller and a GPIO controller. This MFD driver will
> > split the 2 devices for their respective drivers.
> >
> >
Instead of directly using the cache mode bits in the pte switch to
using the cache mode type.
Based-on-patch-by: Stefan Bader
Signed-off-by: Juergen Gross
Reviewed-by: Thomas Gleixner
---
arch/x86/pci/i386.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
When modifying page attributes via change_page_attr_set_clr() don't
test for setting _PAGE_PAT_LARGE, as this is
- never done
- PAT support for large pages is not included in the kernel up to now
Signed-off-by: Juergen Gross
---
arch/x86/mm/pageattr.c | 2 +-
1 file changed, 1 insertion(+), 1
The x86 architecture offers via the PAT (Page Attribute Table) a way to
specify different caching modes in page table entries. The PAT MSR contains
8 entries each specifying one of 6 possible cache modes. A pte references one
of those entries via 3 bits: _PAGE_PAT, _PAGE_PWT and _PAGE_PCD.
The
Instead of directly using the cache mode bits in the pte switch to
using the cache mode type.
Based-on-patch-by: Stefan Bader
Signed-off-by: Juergen Gross
Reviewed-by: Thomas Gleixner
---
drivers/video/fbdev/vermilion/vermilion.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
Instead of directly using the cache mode bits in the pte switch to
using the cache mode type. This requires to change
io_reserve_memtype() as well.
Based-on-patch-by: Stefan Bader
Signed-off-by: Juergen Gross
Reviewed-by: Thomas Gleixner
---
arch/x86/include/asm/pat.h | 2 +-
On Thu, Oct 30, 2014 at 04:09:42PM +0200, Adrian Hunter wrote:
> Add a thread stack for synthesizing call chains from call
> and return events.
>
> Signed-off-by: Adrian Hunter
Acked-by: Jiri Olsa
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
Instead of directly using the cache mode bits in the pte switch to
using the cache mode type in the functions for modifying page
attributes.
Based-on-patch-by: Stefan Bader
Signed-off-by: Juergen Gross
Reviewed-by: Thomas Gleixner
---
arch/x86/mm/pageattr.c | 52
Instead of directly using the cache mode bits in the pte switch to
using the cache mode type.
Based-on-patch-by: Stefan Bader
Signed-off-by: Juergen Gross
Reviewed-by: Thomas Gleixner
---
arch/x86/mm/init_64.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git
Instead of directly using the cache mode bits in the pte switch to
using the cache mode type. This requires changing some callers of
is_new_memtype_allowed() to be changed as well.
Based-on-patch-by: Stefan Bader
Signed-off-by: Juergen Gross
Reviewed-by: Thomas Gleixner
---
Instead of directly using the cache mode bits in the pte switch to
using the cache mode type. As those are the main callers of
lookup_memtype(), change this as well.
Based-on-patch-by: Stefan Bader
Signed-off-by: Juergen Gross
Reviewed-by: Thomas Gleixner
---
arch/x86/mm/pat.c | 32
Dumping page table protection bits is not correct for entries on levels
2 and 3 regarding the PAT bit, which is at a different position as on
level 4.
Based-on-patch-by: Stefan Bader
Signed-off-by: Juergen Gross
Reviewed-by: Thomas Gleixner
---
arch/x86/mm/dump_pagetables.c | 24
With the dynamical mapping between cache modes and pgprot values it is
now possible to use all cache modes via the Xen hypervisor PAT settings
in a pv domain.
All to be done is to read the PAT configuration MSR and set up the
translation tables accordingly.
Signed-off-by: Juergen Gross
The PAT bit in the ptes is not moved to the correct position when
copying page protection attributes between entries of different sized
pages. Translate the ptes according to their page size.
Based-on-patch-by: Stefan Bader
Signed-off-by: Juergen Gross
Reviewed-by: Thomas Gleixner
---
701 - 800 of 2138 matches
Mail list logo
