On 10/09/2013 06:29 AM, Laxman Dewangan wrote:
> The ams AS3722 is a compact system PMU suitable for mobile phones,
> tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
> controller, 11 LDOs, RTC, automatic battery, temperature and
> over-current monitoring, 8 GPIOs, ADC and a
On Wed, Oct 09, 2013 at 08:07:35AM -0700, H. Peter Anvin wrote:
> There needs to be an architecturally guaranteed lower bound on the
> entropic content for this to be at all useful. However, the hwrandom
> interface is currently expecting fully entropic output (which is almost
> certainly
On 10/09/2013 02:11 AM, Peter De Schrijver wrote:
> On Wed, Oct 09, 2013 at 12:31:35AM +0200, Stephen Warren wrote:
>> On 10/04/2013 03:12 AM, Peter De Schrijver wrote:
>>> Tegra124 introduces a number of new peripheral clocks. This patch adds those
>>> to the common peripheral clock code.
>>
>>
Hello,
On Tue, Oct 08, 2013 at 11:07:16AM +0200, Alexander Gordeev wrote:
> Multipe MSIs is just a handful of drivers, really. MSI-X impact still
Yes, so it's pretty nice to try out things there before going full-on.
> will be huge. But if we opt a different name for the new pci_enable_msix()
>
On 10/01/2013 11:38 AM, Durgadoss R wrote:
This patch adds Documentation for the new APIs
introduced in this patch set. The documentation
also has a model sysfs structure for reference.
Signed-off-by: Durgadoss R
---
Documentation/thermal/sysfs-api2.txt | 248
Hello, Alexander.
On Tue, Oct 08, 2013 at 09:48:26AM +0200, Alexander Gordeev wrote:
> > If there are many which duplicate the above pattern, it'd probably be
> > worthwhile to provide a helper? It's usually a good idea to reduce
> > the amount of boilerplate code in drivers.
>
> I wanted to
On Tue, 8 Oct 2013, Jens Axboe wrote:
On Tue, Oct 08 2013, Matthew Wilcox wrote:
On Tue, Oct 08, 2013 at 11:34:20AM +0200, Matias Bjørling wrote:
The nvme driver implements itself as a bio-based driver. This primarily because
of high lock congestion for high-performance nvm devices. To remove
On Mon, Oct 07, 2013 at 09:48:01PM +0100, Ben Hutchings wrote:
> > There is one major flaw in min-max approach - the generic MSI layer
> > will have to take decisions on exact number of MSIs to request, not
> > device drivers.
> [...
>
> No, the min-max functions should be implemented using the
git://gitorious.org/thierryreding/linux-next.git
> >
> > A next-20131009 tag is also provided for convenience.
> >
> > Gained a few conflicts, but nothing too exciting. x86, ARM, PowerPC and
> > MIPS default configurations build fine. There were some build failures
&
Hello,
On Wed, Oct 09, 2013 at 02:57:16PM +0200, Alexander Gordeev wrote:
> On Mon, Oct 07, 2013 at 02:01:11PM -0400, Tejun Heo wrote:
> > Hmmm... yean, the race condition could be an issue as multiple msi
> > allocation might fail even if the driver can and explicitly handle
> > multiple
Hello,
On Tue, Oct 08, 2013 at 02:22:16PM +0200, Alexander Gordeev wrote:
> If we talk about pSeries quota, then the current pSeries pci_enable_msix()
> implementation is racy internally and could fail if the quota went down
> *while* pci_enable_msix() is executing. In this case the loop will
On 10/09/2013 12:20 PM, Maxim Patlasov wrote:
Hi Miklos,
On 10/03/2013 08:22 PM, Maxim Patlasov wrote:
On 10/03/2013 08:09 PM, Miklos Szeredi wrote:
On Thu, Oct 3, 2013 at 5:50 PM, Maxim Patlasov wrote:
On 10/03/2013 07:14 PM, Miklos Szeredi wrote:
On Thu, Oct 03, 2013 at 05:28:30PM +0400,
On Tue, Oct 08, 2013 at 03:29:39PM +0200, Krzysztof Kozlowski wrote:
> This allows migration of zbud pages.
>
> Add radix tree to zbud replacing the red-black tree in zswap. Use
> offset as index to this tree so effectively the handle concept is not
> needed anymore. Zswap uses only offset to
Dave,
Please pull this batch of fixes intended for 3.12...
Most of the bits are for iwlwifi -- Johannes says:
"I have a fix for WoWLAN/D3, a PCIe device fix, we're removing a
warning, there's a fix for RF-kill while scanning (which goes together
with a mac80211 fix) and last but not least we
On Wed, Oct 09, 2013 at 04:14:22PM +0200, Thierry Reding wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131009 tag is also provided for
Hello Romain
On 10/8/2013 5:06 PM, Romain Baeriswyl wrote:
In order to avoid system overload, the clock RXC from the Phy should not be
stopped when in LPI mode.
With the RTL8211E PHY which support EEE mode and with Apple Airport Extreme that
supports it also, the kernel get frozen as soon as
On Tue, Oct 08, 2013 at 04:38:17PM +0100, Mark Rutland wrote:
> On Tue, Oct 08, 2013 at 03:36:11PM +0100, Soren Brinkmann wrote:
> > In some use cases Zynq's FPGA clocks are used as static clock
> > generators for IP in the FPGA part of the SOC for which no Linux driver
> > exists and would
On Wed 09-10-13 07:55:02, George Spelvin wrote:
> This is a newly built machine (although out of "tested" parts), so RAM
> problems are not unthinkable, but I had the chance to capture this so
> it seemed worth reporting.
>
> i7-2xxx CPU, 8GB RAM, file system is ext4 on RAID-1.
> The local
On Wed, Oct 9, 2013 at 6:32 AM, Jingoo Han wrote:
> From: Pratyush Anand
>
> Without irq_create_mapping(), the correct irq number cannot be
> provided. In this case, it makes problems such as NULL deference.
> Thus, irq_create_mapping() should be added for MSI.
>
> Signed-off-by: Pratyush Anand
On Sun, Oct 06, 2013 at 11:55:45PM -0700, Greg Kroah-Hartman wrote:
> The dev_attrs field of struct bus_type is going away soon, dev_groups
> should be used instead. This converts the bcma bus code to use the
> correct field.
>
> Cc: Rafał Miłecki
> Cc:
> Signed-off-by: Greg Kroah-Hartman
>
* Roger Quadros [131009 00:19]:
> Hi Tony,
>
> On 10/08/2013 01:06 PM, Roger Quadros wrote:
> > This reverts commit 741532c4a995be11815cb72d4d7a48f442a22fea.
> >
> > The proper clock reference is provided in device tree so we
> > no longer need this.
>
> Could you please Ack this one? I think
Currently, code checks false return value from "regulator_set_voltage"
to show failure message. Modify the code to check proper return
value from "regulator_set_voltage".
Signed-off-by: Manish Badarkhe
---
Based on master branch of linux-mainline.
:100644 100644 0fac344... 1537f32... M
On Wed, 2013-10-09 at 12:52 +0200, Michal Simek wrote:
> Simplify driver probe and release function.
[]
> diff --git a/drivers/video/xilinxfb.c b/drivers/video/xilinxfb.c
[]
> @@ -423,7 +419,7 @@ static int xilinxfb_of_probe(struct platform_device *pdev)
> pdata = xilinx_fb_default_pdata;
>
* Linus Walleij [131009 06:51]:
> On Mon, Oct 7, 2013 at 7:35 PM, Tony Lindgren wrote:
>
> > Hi Linus W,
> >
> > Any comments on the pinctrl patches 3 - 5 in this series?
>
> Yes, after good explanations to my whimsical questions only this:
> Acked-by: Linus Walleij
OK thanks :)
> I guess
On Wed, Oct 09, 2013 at 04:56:19PM +0200, Frederic Weisbecker wrote:
> On Tue, Oct 08, 2013 at 02:12:18PM -0700, Paul E. McKenney wrote:
> > On Tue, Oct 08, 2013 at 10:34:28PM +0200, Frederic Weisbecker wrote:
> > > So I wonder, do we want to continue to allow this nesting? I remember
> > > that
On 10/09/2013 07:46 AM, Stanimir Varbanov wrote:
>
> No, there is no public documentation for the block. Here is the driver
> documentation which I used as a base [1].
>
> My guess was that - if it is PRNG (got from hardware description link
> above) than according to wiki [2] it is also known
* Ingo Molnar wrote:
> > It silently ignores the O= target, as it doesn't exists.
> >
> > Previous, expected behaviour is for the build process to stop,
> > complaining that the target directory doesn't exists.
>
> Yeah. So the reproducer for me is:
>
> rm -rf /tmp/build
> mkdir -p
On Wed, 2013-10-09 at 07:14 -0400, Dan Rosenberg wrote:
> isn't the default value of kptr_restrict 0 now, unless I'm missing
> something? If I recall it was 1 when originally written, and then
> changed to 0 at some point. Could the documentation be updated to
> reflect that?
Yeah, the default
BogoMIPs is a confusing concept to the ill-informed, so allow
architectures to print it only if they find it worthwhile. The delay
calibration code should stick to lpj and avoid trying to draw any
correlation with BogoMIPs, which may be a fixed value derived from a
timer frequency independent of
On Tue, Oct 08, 2013 at 02:12:18PM -0700, Paul E. McKenney wrote:
> On Tue, Oct 08, 2013 at 10:34:28PM +0200, Frederic Weisbecker wrote:
> > So I wonder, do we want to continue to allow this nesting? I remember that
> > DYNTICK_TASK_NEST_*
> > stuff is there to protects against non finishing
On Wed, Oct 09, 2013 at 09:26:21AM +0800, Fengguang Wu wrote:
> Useful for locating buggy drivers on kernel oops.
>
> It may add dozens of new lines to boot dmesg. DEBUG_KOBJECT_RELEASE is
> hopefully only enabled in debug kernels (like maybe the Fedora rawhide
> one, or at developers), so being
Hi Ted,
On 10/04/2013 09:10 PM, Theodore Ts'o wrote:
> On Fri, Oct 04, 2013 at 07:23:50PM +0300, Stanimir Varbanov wrote:
>> I guess that it should follow NIST 800-90 recommendation, but I'm not
>> aware what DRBG mechanism is used.
>>
>> To be honest I really don't know the hardware
This patch adds MOXA ART SoCs clock driver support.
Signed-off-by: Jonas Jensen
---
Notes:
Since last version, Adam Jaremko has been helping providing info on
the clock registers and the SoC in general. He's been looking at
bootloader sources in particular, which seem to do the same
* Arnaldo Carvalho de Melo wrote:
> Em Wed, Oct 09, 2013 at 09:01:49AM +0200, Ingo Molnar escreveu:
> > Arnaldo,
> >
> > Please pull the tools/perf/build git tree from:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> > tmp.tools/perf/build
> >
> ># HEAD:
Met vriendelijke groeten,
Eric Verdonck
Driver Development
Option nv, Gaston Geenslaan 14, B-3001 Leuven
T: +32 16 311 597
F: +32 16 207 164
E-mail: e.verdo...@option.com
Website: www.option.com
Disclaimer:http://www.option.com/company/disclaimer.shtml
RPR Leuven 0429.375.448
On 10/09/2013
Em Wed, Oct 09, 2013 at 09:01:49AM +0200, Ingo Molnar escreveu:
> Arnaldo,
>
> Please pull the tools/perf/build git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tmp.tools/perf/build
>
># HEAD: 165108a92fc554d51e73b143b69b77e7c278da78 tools/perf/build: Clean
On Tue, Oct 08, 2013 at 01:08:53PM -0700, Andrew Morton wrote:
> On Tue, 08 Oct 2013 10:13:20 +0200 Krzysztof Kozlowski
> wrote:
>
> > On pon, 2013-10-07 at 15:03 -0700, Andrew Morton wrote:
> > > On Mon, 07 Oct 2013 17:25:41 +0200 Krzysztof Kozlowski
> > > wrote:
> > >
> > > > During
From: Namjae Jeon
Make the fibmap call the return the proper physical block number for any
offset request in the fallocated range.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/fat/cache.c | 16 ++--
fs/fat/inode.c |4 ++--
2 files changed, 16
On Wed, 2013-10-09 at 16:14 +0200, Thierry Reding wrote:
> IPv6 specific fields in struct sock_common are accessed in various
> places even if IPv6 support is disabled. Fix this by including the
> fields unconditionally.
Well no. There is a reason we keep CONFIG_IPV6 at all.
The right fix is
From: Namjae Jeon
For normal buffered write operations, normally if we try to write to an
offset > than file size, it does a cont_expand_zero till that offset.
Now, in case of fallocated regions, since the blocks are already allocated.
So, make it zero out that buffers for those blocks till the
From: Namjae Jeon
Implement preallocation via the fallocate syscall on VFAT partitions.
This patch is based on an earlier patch of the same name which had some
issues detailed below and did not get accepted.
Refer https://lkml.org/lkml/2007/12/22/130.
a) The preallocated space was not
From: Namjae Jeon
For normal cases of direct IO write, trying to seek to location greater than
file size,
makes it fall back to buffered write to fill that region.
Similarly, in case for write in Fallocated region, make it fall to buffered
write.
Signed-off-by: Namjae Jeon
Signed-off-by:
From: Namjae Jeon
This patch set provides support for doing fallocate operation on FAT filesystem.
After series of review for the the feature
The complete functionality is broken down into smaller subsets.
Namjae Jeon (5):
fat: add i_disksize to represent uninitialized size
fat: add
From: Namjae Jeon
Add i_disksize to represent uninitialized allocated size.
And mmu_private represent initialized allocated size.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/fat/cache.c |4 ++--
fs/fat/fat.h |3 ++-
fs/fat/file.c |4 +++-
fs/fat/inode.c |
Thierry,
On Wed, Oct 09, 2013 at 04:14:27PM +0200, Thierry Reding wrote:
> Today's linux-next merge of the mvebu tree got conflicts in
I looked in your scripts repo, and couldn't find the script you use to
send out this email thread :( Since I can't create a patch, I'll just
ask, could you
On Wed, Oct 09, 2013 at 04:07:34PM +0200, Peter Zijlstra wrote:
> Once I force a x86_64 build using the 'same' config it goes away and
> generates 'sensible' code again (although I don't see why L9 isn't
> merged with L2):
i386-SMP also generates correct code afaict; a tad stupid but not wrong.
* Peter Zijlstra wrote:
> > This is what we are going to return. But note that -20(%ebp) was not
> > initialized if TIF_NOTIFY_RESUME was already set, "jc .L2" skips .L5
> > above. IOW, in this case we seem to return a random value from stack.
>
> I think you're quite right, and I can confirm
OK, thanks...
I didn't notice Richard and Jakub were not cc'ed... Add them, perhaps
they can take a look.
On 10/09, Peter Zijlstra wrote:
>
> On Wed, Oct 09, 2013 at 02:43:10PM +0200, Oleg Nesterov wrote:
> > I'm afraid I am wrong, my asm skills are close to zero... but this
> > code looks wrong
On Wed, Oct 09, 2013 at 08:08:06AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney wrote:
>
> > On Tue, Oct 08, 2013 at 08:28:43PM -0700, Paul E. McKenney wrote:
> > > On Tue, Oct 08, 2013 at 01:40:56PM -0700, Paul E. McKenney wrote:
> > > > On Tue, Oct 08, 2013 at 09:47:18PM +0200, Ingo
On Wed, Oct 09, 2013 at 04:14:27PM +0200, Thierry Reding wrote:
> Today's linux-next merge of the mvebu tree got conflicts in
>
> arch/arm/mach-dove/board-dt.c
> arch/arm/mach-kirkwood/board-dt.c
>
> caused by commits ebd7d3a (ARM: kirkwood: retain MAC address for DT
> ethernet),
Hello,
On 19 September 2013 12:13, Jan Kara wrote:
> On Wed 18-09-13 16:56:08, Michal Suchanek wrote:
>> On 17 September 2013 23:13, Jan Kara wrote:
>> > Hello,
>>
>> The default for dirty_ratio/dirty_background_ratio is 60/40. Setting
> Ah, that's not upstream default. Upstream has 20/10.
Today's linux-next merge of the drm-intel tree got conflicts in
drivers/gpu/drm/i915/i915_dma.c
drivers/gpu/drm/i915/intel_dp.c
caused by commits 0111be4 (drm: Kill drm perf counter leftovers) and
b14c567 (drm/i915: use pointer = k[cmz...]alloc(sizeof(*pointer), ...)
pattern) as
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131009 tag is also provided for convenience.
Gained a few conflicts, but nothing too exciting. x86, ARM, PowerPC and
MIPS default
Today's linux-next merge of the mvebu tree got conflicts in
arch/arm/mach-dove/board-dt.c
arch/arm/mach-kirkwood/board-dt.c
caused by commits ebd7d3a (ARM: kirkwood: retain MAC address for DT
ethernet), 511aaab (ARM: kirkwood: Remove unneeded MBus initialization)
and a169e3a
IPv6 specific fields in struct sock_common are accessed in various
places even if IPv6 support is disabled. Fix this by including the
fields unconditionally.
Signed-off-by: Thierry Reding
---
include/net/sock.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/net/sock.h
Today's linux-next merge of the imx-mxs tree got conflicts in
arch/arm/mach-imx/clk-imx51-imx53.c
arch/arm/mach-imx/mach-imx6q.c
caused by commits 0efe995 (ARM: mach-imx: clk-imx51-imx53: Retrieve base
address and irq from dt), d2b36f6 (ARM: imx: replace imx6q_restart()
with
Today's linux-next merge of the clk tree got a conflict in
drivers/clk/Makefile
caused by commits f00578d (clk: emev2: Add support for emev2 SMU clocks
with DT), 6cfc229 (clk: keystone: Build Keystone clock drivers) and
308964c (clk: Add APM X-Gene SoC clock driver).
I fixed it up (see
On 10/09/2013 03:04 AM, HATAYAMA Daisuke wrote:
>>>
>>> Sorry, I don't understand why relocation size cannot be calculated when
>>> CONFIG_PHYSICALSTART > CONFIG_PHYSICAL_ALIGN. Could you explain that?
>>
>> I just meant that when CONFIG_PHYSICAL_START > CONFIG_PHYSICAL_ALIGN,
>> the 32-bit x86
On Tue, Oct 8, 2013 at 8:45 PM, Linus Torvalds
wrote:
> On Tue, Oct 8, 2013 at 3:48 PM, Greg Kroah-Hartman
> wrote:
>>
>> It's going to make things really noisy at boot time, but then it should
>> settle down and not be bad at all. Let's try it and see if it helps or
>> not.
>
> Yeah. And quite
On Wed, Oct 09, 2013 at 02:43:10PM +0200, Oleg Nesterov wrote:
> I'm afraid I am wrong, my asm skills are close to zero... but this
> code looks wrong to me, and this can explain the oopses.
>
> > task_work_add:
> > pushl %ebp#
> > movl%esp, %ebp #,
> > pushl %edi
If the SPI device is enumerated from ACPI namespace (it has an ACPI handle)
it might have ACPI methods that needs to be called in order to transition
the device to different power states (such as _PSx).
We follow what has been done for platform and I2C buses here and attach the
SPI device to the
Hi,
We originally tried to add runtime PM support for I2C adapter devices in
order to have runtime PM core to power on the I2C host controller device
automatically whenever any of its children I2C device is powered on (See
[1] for the last patch series).
The rationale was that it is what the
Some serial buses like I2C and SPI don't require that the parent device is
in D0 before any of its children transitions to D0, but instead the parent
device can control its own power independently from the children.
This does not follow the ACPI specification as it requires the parent to be
From: Lv Zheng
If the I2C client device is enumerated from ACPI namespace it might have
ACPI methods that needs to be called in order to transition the device to
different power states (such as _PSx).
Implement this for I2C client devices by checking if the device has an ACPI
handle and if
Hi,
All patches (#1-#3) look good to me, FWIW you can add:
Reviewed-by: Bartlomiej Zolnierkiewicz
Please note that (at least) patch #3 conflicts with Lukasz's EXYNOS4412
fixup patchset:
https://lkml.org/lkml/2013/10/9/35
It is up to Eduardo to resolve this but it probably
On Wed, Oct 9, 2013 at 3:28 PM, Christian Ruppert
wrote:
> On Wed, Oct 09, 2013 at 01:58:35PM +0200, Linus Walleij wrote:
>> On Tue, Oct 8, 2013 at 2:25 PM, Christian Ruppert
>> wrote:
>> > +In addition, named groups of pins can be mapped to pin groups of a given
>> > +pin controller using the
On Tue, Oct 08, 2013 at 07:08:11PM -0300, Marcelo Tosatti wrote:
> On Tue, Oct 08, 2013 at 09:37:05AM -0400, Don Zickus wrote:
> > On Mon, Oct 07, 2013 at 10:05:17PM -0300, Marcelo Tosatti wrote:
> > > Implement reset of kernel watchdogs at pvclock read time. This avoids
> > > adding special code
Hi Al,
On Thu, Oct 03, 2013 at 03:50:07AM +0100, Al Viro wrote:
...
> Another thing: I'd rather pull everything about setting the inode
> up (aops, size, etc.) in there.
>
> Anyway, could you take a look at the last couple of commits in
> vfs.git#for-bcrl? Commit message on the last one is an
On 10/9/13 7:33 AM, Jiri Olsa wrote:
+
+ if (size > remaining) {
+ memcpy(rec->mmap_addr + rec->mmap_offset, buf, remaining);
+ rec->bytes_written += remaining;
+
+ size -= remaining;
+ buf += remaining;
+
+
On Mon, Oct 7, 2013 at 7:35 PM, Tony Lindgren wrote:
> Hi Linus W,
>
> Any comments on the pinctrl patches 3 - 5 in this series?
Yes, after good explanations to my whimsical questions only this:
Acked-by: Linus Walleij
I guess you'll take these patches through ARM SoC?
Yours,
Linus Walleij
On Tue, Oct 8, 2013 at 10:35 PM, Wolfram Sang wrote:
> Subsystems like pinctrl and gpio rightfully make use of deferred probing at
> core level. Now, deferred drivers won't be retried if they don't have a .probe
> function specified in the driver struct. Fix this driver to have that, so the
>
On Tue, Oct 08, 2013 at 03:52:17PM +0100, Will Deacon wrote:
> Hi guys,
>
> I've been running trinity on my ARMv7 Cortex-A15 system and managed to
> trigger the following kernel warning:
Adding Kent to the list of recipients since this is in code he wrote. I'd
like to try to track down a test
On Sun, Sep 22, 2013 at 08:05:59PM -0600, David Ahern wrote:
SNIP
> +
> + if (size > remaining) {
> + memcpy(rec->mmap_addr + rec->mmap_offset, buf, remaining);
> + rec->bytes_written += remaining;
> +
> + size -= remaining;
> + buf +=
On Wed, Oct 09, 2013 at 01:58:35PM +0200, Linus Walleij wrote:
> On Tue, Oct 8, 2013 at 2:25 PM, Christian Ruppert
> wrote:
>
> > This patch adds the infrastructure required to register non-linear gpio
> > ranges through gpiolib and the standard GPIO device tree bindings.
> >
> > Signed-off-by:
On Tue, Oct 08, 2013 at 11:58:57PM +0100, Tim Bird wrote:
> From: Roman Bobniev
>
> Move all kmemleak calls into hook functions, and make it so
> that all hooks (both inside and outside of #ifdef CONFIG_SLUB_DEBUG)
> call the appropriate kmemleak routines. This allows for kmemleak
> to be
On Tue, Oct 08, 2013 at 08:20:27PM +0200, Jean-Francois Moine wrote:
> As defined in the DT, clkout2 is not allowed to change the pll inside
> si5351.
>
> This patch extends the properties of clkout2 so that it works as the
> external clock of the audio device in the Cubox.
>
> Also, as the
On Tue, Oct 08, 2013 at 09:26:53PM -0600, David Ahern wrote:
> When enabled dumps a summary of all syscalls by task with the usual
> statistics -- min, max, average and relative stddev. For example,
>
> make - 26341 : 3344 [ 17.4% ] 0.000 ms
>
> read : 520.000
On 08/08/2013 12:30, Boris BREZILLON :
This patch removes the old main clk node which is now useless as sama5d3
SoCs and boards are no longer compatible with the old at91 clk
implementations.
Signed-off-by: Boris BREZILLON
As said earlier, removal of old clock definitions is needed in this
On 08/08/2013 12:29, Boris BREZILLON :
This patch removes the selection of AT91_USE_OLD_CLK when selecting sama5d3
SoC support. This will enable automatically enable COMMON_CLK_AT91 option
and add support for at91 common clk implementation.
Signed-off-by: Boris BREZILLON
One big step!
On 08/08/2013 11:36, Boris BREZILLON :
Define the main clock frequency for the new main clock node
in sama5d3xcm.dtsi.
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
---
arch/arm/boot/dts/sama5d3xcm.dtsi |6 ++
1 file changed, 6 insertions(+)
diff --git
On 08/08/2013 11:31, Boris BREZILLON :
Define sama5d3 clocks in sama5d3 device tree.
Add references to the appropriate clocks in each peripheral.
Signed-off-by: Boris BREZILLON
Do not forget to remove the macros and change file paths...
---
arch/arm/boot/dts/sama5d3.dtsi | 331
On 08/08/2013 11:21, Boris BREZILLON :
This patch enclose sama5d3 old clk registration in
"#if defined(CONFIG_OLD_CLK_AT91) #endif" sections.
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
And... do not forget to remove completely the code when transition is
done (ie: in "[PATCH
On 08/08/2013 11:20, Boris BREZILLON :
This patch prepare the transition to common clk for sama5 dt boards by
replacing the timer init callback.
Clocks registration cannot be done in early init callback (as formerly done
by the old clk implementation) because it requires dynamic allocation
On Wed, Oct 09, 2013 at 02:27:05PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 09, 2013 at 08:19:11PM +0800, Fengguang Wu wrote:
> > > > Fengguang, I do not think this will help, but just in case. Could you
> > > > show the result of
> > > >
> > > > $ kernel/task_work.s
> >
> > Update: I
On Mon, Oct 07, 2013 at 02:01:11PM -0400, Tejun Heo wrote:
> Hmmm... yean, the race condition could be an issue as multiple msi
> allocation might fail even if the driver can and explicitly handle
> multiple allocation if the quota gets reduced inbetween.
BTW, should we care about the quota
* Peter Zijlstra wrote:
> On Wed, Oct 09, 2013 at 08:19:11PM +0800, Fengguang Wu wrote:
> > > > Fengguang, I do not think this will help, but just in case. Could you
> > > > show the result of
> > > >
> > > > $ kernel/task_work.s
> >
> > Update: I recompiled the kernel with gcc 4.4.7
Hi Fengguang,
On 10/09, Fengguang Wu wrote:
>
> Thanks for looking into this. Attached is the task_work.s for you.
Thanks a lot!
I'm afraid I am wrong, my asm skills are close to zero... but this
code looks wrong to me, and this can explain the oopses.
> task_work_add:
> pushl %ebp
* Peter Zijlstra wrote:
> On Wed, Oct 09, 2013 at 01:03:54PM +0200, Ingo Molnar wrote:
> > kernel/sched/fair.c:819:22: warning: 'task_h_load' declared 'static' but
> > never defined [-Wunused-function]
>
> Not too pretty, but it avoids the warning:
>
> ---
> --- a/kernel/sched/fair.c
> +++
On Tue, Oct 08, 2013 at 02:58:22PM +0800, chai wen wrote:
> On 10/02/2013 12:04 AM, chaiwen wrote:
> >On 09/30/2013 08:51 PM, Gleb Natapov wrote:
> >>On Mon, Sep 30, 2013 at 06:03:07PM +0800, chai wen wrote:
> >>>Hi all
> >>>
> >>>Async page fault in kvm currently pin user pages via
On 09/10/13 15:16, Jiri Olsa wrote:
> On Wed, Oct 09, 2013 at 01:38:04PM +0300, Adrian Hunter wrote:
>> On 09/10/13 13:12, Jiri Olsa wrote:
>>> On Wed, Oct 09, 2013 at 10:33:25AM +0300, Adrian Hunter wrote:
On 08/10/13 17:02, Jiri Olsa wrote:
> On Tue, Oct 08, 2013 at 11:45:50AM +0300,
Hi,
On 08/10/13 16:17, Tomi Valkeinen wrote:
> Hi,
>
> I'm seeing the following issue on omap3 with dpll4_m4 clock. dpll4_m4's
> parent is a PLL set to 86400 and dpll4_m4 is a divider, handled by
> clk-divider.c.
>
> Now, if I call clk_round_rate(dpll4_m4, 14399), I get 123428571
>
op 08-10-13 18:58, Thomas Hellstrom schreef:
> On 10/08/2013 06:47 PM, Jerome Glisse wrote:
>> On Tue, Oct 08, 2013 at 06:29:35PM +0200, Thomas Hellstrom wrote:
>>> On 10/08/2013 04:55 PM, Jerome Glisse wrote:
On Tue, Oct 08, 2013 at 04:45:18PM +0200, Christian König wrote:
> Am
Heya,
I've seen this crash thrice so far on an Intel Haswell machine while
doing some nested virtualization tests (KVM on KVM). At this moment, I can't
pin-point an to exact trigger. On two occasions, it crashed when I tried to
reboot a guest hypervisor (as part of nested virtualization testing).
From: Pratyush Anand
Without irq_create_mapping(), the correct irq number cannot be
provided. In this case, it makes problems such as NULL deference.
Thus, irq_create_mapping() should be added for MSI.
Signed-off-by: Pratyush Anand
Suggested-by: Kishon Vijay Abraham I
Signed-off-by: Jingoo
From: Mark Brown
Rather than passing a flag around through the entire call stack store it
in the regmap struct and read it when required. This minimises the
visibility of the feature through the API, minimising the code updates
needed to use it more widely.
Signed-off-by: Mark Brown
---
From: Mark Brown
Make it easier for drivers to include single register writes in
asynchronous sequences by providing async versions of the write
and update bits operations. The update bits operations are only
likely to be effective when used with devices that have caches
but this is common
On Tue, Oct 8, 2013 at 2:25 PM, Christian Ruppert
wrote:
> The pinmux driver of the Abilis Systems TB10x platform based on ARC700 CPUs.
> Used to control the pinmux and is a prerequisite for the GPIO driver.
>
> Signed-off-by: Christian Ruppert
> Signed-off-by: Pierrick Hascoet
Overall this
On Wednesday, October 09, 2013 8:14 PM, Pratyush Anand wrote:
> On Wed, Oct 09, 2013 at 06:49:15PM +0800, Jingoo Han wrote:
> > On Wednesday, October 09, 2013 7:27 PM, Kishon Vijay Abraham I wrote:
> > > On Wednesday 09 October 2013 03:35 PM, Jingoo Han wrote:
> > > > On Wednesday, October 09,
On Wed, Oct 09, 2013 at 08:19:11PM +0800, Fengguang Wu wrote:
> > > Fengguang, I do not think this will help, but just in case. Could you
> > > show the result of
> > >
> > > $ kernel/task_work.s
>
> Update: I recompiled the kernel with gcc 4.4.7 and find it booting fine!
> # 208
.../devicetree/bindings/media/remote-control.txt | 31
1 files changed, 31 insertions(+), 0 deletions(-)
create mode 100644
Documentation/devicetree/bindings/media/remote-control.txt
diff --git
401 - 500 of 1358 matches
Mail list logo
