From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Cc: Deepak Sikri
Acked-by: Viresh Kumar
Signed-off-by: Sudeep
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Cc: Viresh Kumar
Cc: Dmitry Eremin-Solenikov
Signed-off-by:
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Acked-by: Viresh Kumar
Signed-off-by: Sudeep KarkadaNagesha
---
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes DT parsing and uses cpu->of_node instead.
Cc: Viresh Kumar
Cc: Benjamin Herrenschmidt
Signed-off-by: Sudeep
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Cc: Viresh Kumar
Cc: Benjamin Herrenschmidt
Signed-off-by: Sudeep
Hello again
I have made some experiments and have replaced alloc_pages_exact with
alloc_pages of order N. Unfortunatelly vm_insert_page and vm_map_ram
does not work as expected.
vm_insert_page, only insert the PAGE_SIZE bytes of the higher order
page, if I try to add the other pages manually,
This is the at91 programmable clocks implementation using common clk
framework.
A programmable clock is a clock which can be exported on a given pin to clock
external devices.
Each programmable clock is given an id (from 0 to 8).
The number of available programmable clocks depends on the SoC
On Mon, Jul 15, 2013 at 01:33:53PM +0200, Lars-Peter Clausen wrote:
> On 07/15/2013 01:09 PM, Kozaruk, Oleksandr wrote:
> [...]
> >
> >>> + ret = devm_request_threaded_irq(dev, irq, NULL,
> >>> + twl6030_gpadc_irq_handler,
> >>> + IRQF_ONESHOT, "twl6030_gpadc", gpadc);
> >>
> >> You access
This is the at91 peripheral clock implementation using common clk framework.
Almost all peripherals provided by an at91 SoC need a clock to work properly.
This clock is enabled/disabled using PCER/PCDR resgisters.
Each peripheral is given an id (see atmel's datasheets) which is used as bit
On 13-07-16 07:38 PM, Steven Rostedt wrote:
> On Tue, 2013-07-16 at 16:12 -0700, Sarah Sharp wrote:
>
[...]
>
>> We need to define what behavior we want
>> from both maintainers and patch submitters. E.g. "No regressions" and
>> "don't break userspace"
>
> Yes, those do need to be
On Wed, Jul 17, 2013 at 4:17 AM, Stefano Stabellini
wrote:
> On Tue, 16 Jul 2013, H. Peter Anvin wrote:
>> Linux took off in a way that the other OSS operating systems didn't, and
>> several of them had started earlier and with way more funding available.
>>
>> You really have to think about why
This is the documentation of the dt bindings used by at91 clks.
Signed-off-by: Boris BREZILLON
---
.../devicetree/bindings/clock/at91-clock.txt | 262
1 file changed, 262 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/at91-clock.txt
diff
This is the at91 usb clock implementation using common clk framework.
This clock is used to clock usb ports (ohci, ehci and udc).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/Kconfig | 11 ++
drivers/clk/at91/Makefile |1 +
drivers/clk/at91/clk-usb.c | 303
This is the at91 smd (Soft Modem) clock implementation using common clk
framework.
Not used by any driver right now.
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/Kconfig |5 ++
drivers/clk/at91/Makefile |1 +
drivers/clk/at91/clk-smd.c | 157
This is the at91 pll clock implementation using common clk framework.
The pll clock layout describe the PLLX register layout.
There's four pll clock layouts:
- at91rm9200
- at91sam9g20
- at91sam9g45
- sama5d3
PLL clocks are given characteristics:
- min/max clock source rate
- ranges of valid
This is the at91 utmi clock implementation using common clk framework.
This clock is a pll with a fixed factor (x40).
It is used as a source for usb clock.
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/Kconfig |7 +++
drivers/clk/at91/Makefile |1 +
(Resending with wider distribution list since my earlier email to
linux-wireless didn't get a response)
I updated the kernel on my fedora rawhide KVM guest, and noticed that
the ethernet interface wasn't coming up at all. While poking around, I
saw this stack trace pop up:
Jul 12 07:29:25
Hello Stephen, (actually a greeting this time!)
On Wed, Jul 17, 2013 at 01:41:24PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
>
> fs/aio.c: In function 'aio_migratepage':
> fs/aio.c:196:2: error:
This is the at91 system clock implementation using common clk framework.
Some peripheral needs to enable a "system" clock in order to work properly.
Each system clock is given an id which is the bit offset used in SCER/SCDR
registers.
Signed-off-by: Boris BREZILLON
---
Arnd
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: 2013年7月15日 3:30
> To: Neil Zhang
> Cc: Jason Cooper; Matt Sealey; grant.lik...@linaro.org;
> haojian.zhu...@gmail.com; devicetree-disc...@lists.ozlabs.org;
> linux-kernel@vger.kernel.org;
On Wed, Jul 17, 2013 at 05:22:30PM +0800, Gu Zheng wrote:
> As the aio job will pin the ring pages, that will lead to mem migrated
> failed. In order to fix this problem we use an anon inode to manage the aio
> ring
> pages, and setup the migratepage callback in the anon inode's address space,
This is the at91 master clock implementation using common clk framework.
The pll clock layout describe the MCKR register layout.
There's four pll clock layouts:
- at91rm9200
- at91sam9x5
Master clocks are given characteristics:
- min/max clock output rate
These characteristics are checked
Hello,
On 7/17/2013 11:43 AM, Ricardo Ribalda Delgado wrote:
Hi Marek
alloc_pages_exact returns pages of order 0, every single page is
filled into buf->pages, that then is used by vb2_dma_sg_mmap(), that
also expects order 0 pages (its loops increments in PAGE_SIZE). The
code has been tested
Hello,
This patch series is a proposal to move at91 clock implementation
to common clk framework.
Most of the clock provided by the PMC (Power Management Controller) are
implemented :
- main clock (main oscillator)
- pll clocks
- master clock
- programmable clocks
- utmi clock
- peripheral
This is the at91 main oscillator clock implementation using common
clk framework.
If rate is not provided during clock registraction it is computed using
the slow clock (main clk parent in this case) rate and the MCFR register.
Signed-off-by: Boris BREZILLON
---
drivers/clk/at91/Makefile |
On Mon, 15 Jul 2013, Julien Grall wrote:
> Enable power management from the toolstack for ARM guest.
>
> Signed-off-by: Julien Grall
Considering that now we support both ARM and ARM64, could you please
add an ifneq ($(CONFIG_ARM64),y) too around cpu_hotplug.o, since you are
at it?
>
This patch moves at91_pmc.h header from machine specific directory
(arch/arm/mach-at91/include/mach/at91_pmc.h) to clk include directory
(include/linux/clk/at91.h).
We need this to avoid reference to machine specific headers in clk
drivers.
Signed-off-by: Boris BREZILLON
---
Andy Lutomirski wrote:
I'm rather confused here. In SMBUS, the "read word" operation returns
two bytes. Just to be confusing, the SMBUS spec calls the first byte
"Data Byte Low" and the second byte "Data Byte High". But they really
are the first and second bytes -- Read Word will return
On 13-07-16 01:33 PM, Jonathan Corbet wrote:
> On Mon, 15 Jul 2013 19:34:44 -0400
> Paul Gortmaker wrote:
>
>> The last mainline release of a v2.6.x kernel was back in May 2011.
>> Here we update references to be 3.x based, which also means updating
>> some dates and statistics.
>
> Ccing the
On 7/17/13 2:08 AM, Namhyung Kim wrote:
From: Namhyung Kim
If an user gives both of --symfs and --vmlinux option, the vmlinux
will be searched under the symfs directory. This is somewhat
confusing since vmlinux often lives in kernel build directory or
somewhere other than user space binaries.
On Wed, 2013-07-17 at 13:33 +0100, Nicolas Pitre wrote:
> If this is really miscelaneous code that really doesn't fit
> anywhere else, it should rather go into drivers/misc/ as a last resort.
Interestingly enough drivers/misc was my first choice for all the
vexpress stuff, but it wasn't received
From: Ruchika Kharwar
Ensure the Interrupt handling routine return IRQ_HANDLED vs
IRQ_NONE.
Signed-off-by: Ruchika Kharwar
Signed-off-by: Alexander Savchenko
---
drivers/tty/serial/omap-serial.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
On Mon, 15 Jul 2013, Konrad Rzeszutek Wilk wrote:
> On Mon, Jul 15, 2013 at 03:21:41PM +0100, Julien Grall wrote:
> > When linux is running as dom0, Xen doesn't show the physical cpu but a
> > virtual CPU.
> > On some ARM SOC (for instance the exynos 5250), linux registers callbacks
> > for
On Wed, Jul 17, 2013 at 09:04:54PM +0800, Rong Wang wrote:
> Hi Felipe,
>
> On Wed, Jul 17, 2013 at 3:57 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Mon, Jul 15, 2013 at 11:31:17PM -0700, Greg KH wrote:
> >> > The question is since we default GADGET, so the g_mass_storage.ko is
> >> > installed
On Mon, 15 Jul 2013, Julien Grall wrote:
> Even if uncompress debug is disabled, some board will continue to print
> information during uncompress step.
Are you talking about DEBUG_UNCOMPRESS?
Should I read the sentence as "even if DEBUG_UNCOMPRESS is not selected,
some board will continue to
On Wed, Jul 17, 2013 at 06:25:05PM +0530, Raghavendra K T wrote:
> On 07/17/2013 06:15 PM, Gleb Natapov wrote:
> >On Wed, Jul 17, 2013 at 03:35:37PM +0530, Raghavendra K T wrote:
> Instead of halt we started with a sleep hypercall in those
> versions. Changed to halt() once Avi suggested
This patch adds MOXA ART SoCs clock driver support.
Signed-off-by: Jonas Jensen
---
Notes:
Changes since v2:
1. add devicetree bindings document
Applies to next-20130716
.../bindings/clock/moxa,moxart-core-clock.txt | 19 +
drivers/clk/Makefile
On Wed, Jul 17, 2013 at 09:03:35AM -0400, Steven Rostedt wrote:
> On Wed, 2013-07-17 at 13:30 +0100, Ricardo Ferreira wrote:
> > Slashdot is just a cesspool of trolls, not a good comparison.
>
> Point taken.
>
> I posted this privately, and I think I'll repost it here. I need to
> modify it a
On 07/16/2013 10:17 PM, Matt Turner wrote:
> On Tue, Jul 16, 2013 at 10:34 AM, Richard Henderson wrote:
>> Use WTINT to wait for the next interrupt. Squash the WTINT call
>> if the PALcode doesn't support it (e.g. MILO). No attempt is yet
>> made to skip clock ticks during normal scheduling in
On Wednesday 17 July 2013 01:18:00 Paul Bolle wrote:
> On Wed, 2013-07-17 at 00:34 +0200, Martin Walch wrote:
> > As I am working on yet another project for analyzing LKC's input files, I
> > have some intermediate results from simple syntactical checks.
>
> Naive question: LKC?
Sorry, I thought
On Wed, Jul 17, 2013 at 1:20 PM, Niels de Vos wrote:
> I can confirm that your patch fixes the original panic/BUG() with both
> Brian's test-case and the GlusterFS regression tests.
>
> Feel free to add my Tested-by/Reviewed-by signoff for this patch.
Thanks for the review and testing, patches
Hi Felipe,
On Wed, Jul 17, 2013 at 3:57 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Jul 15, 2013 at 11:31:17PM -0700, Greg KH wrote:
>> > The question is since we default GADGET, so the g_mass_storage.ko is
>> > installed early but connecting to a host PC
>> > is randomly, But the udev has no idea
On Wed, 2013-07-17 at 13:30 +0100, Ricardo Ferreira wrote:
> Slashdot is just a cesspool of trolls, not a good comparison.
Point taken.
I posted this privately, and I think I'll repost it here. I need to
modify it a bit as it wasn't meant to be public.
When I started sending patches to LKML it
On 07/17/2013 07:13 AM, Neil Horman wrote:
Recently we added an early quirk to detect 5500/5520 chipsets with early
revisions that had problems with irq draining with interrupt remapping enabled:
commit 03bbcb2e7e292838bb0244f5a7816d194c911d62
Author: Neil Horman
Date: Tue Apr 16 16:38:32
On 07/16/2013 09:29 PM, Matt Turner wrote:
> I've got five patches in a for-linus branch on kernel.org that I was
> planning to send a pull request for soon. Would you like me to add
> these to that branch?
Yes, please.
r~
--
To unsubscribe from this list: send the line "unsubscribe
On 07/17/2013 06:15 PM, Gleb Natapov wrote:
On Wed, Jul 17, 2013 at 03:35:37PM +0530, Raghavendra K T wrote:
Instead of halt we started with a sleep hypercall in those
versions. Changed to halt() once Avi suggested to reuse existing sleep.
If we use older hypercall with few changes like
On 17 July 2013 17:01, Rafael J. Wysocki wrote:
> First off, I'm not sure how many applications actually use it and I think,
> if any, they should be able cope with the attribute not being present.
>
> Of course, if it turns out that yes, there are applications using it and no,
> they cannot cope
On Tue 16-07-13 16:25:33, Dave Jones wrote:
> I've seen this happen a few times this week..
Thanks for report! Was this when fuzzing or just normal desktop load?
What is inode with inode number 12 on your filesystem sdb1? What IO happens
to it? Apparently some delalloc accounting went wrong
Add SDHCI driver for MOXA ART SoCs.
Signed-off-by: Jonas Jensen
---
Notes:
Changes since v1:
1. remove IRQF_DISABLED
2. use devm_request_irq, remove free_irq
3. remove unnecessary dev_set_drvdata in moxart_remove
4. add devicetree bindings document
5. use BIT macro
On Wed, Jul 17, 2013 at 03:35:37PM +0530, Raghavendra K T wrote:
> >>Instead of halt we started with a sleep hypercall in those
> >> versions. Changed to halt() once Avi suggested to reuse existing sleep.
> >>
> >>If we use older hypercall with few changes like below:
> >>
>
On 27/06/13 04:32, Joel Fernandes wrote:
> From: Matt Porter
>
> Adds AM33XX MMC support for am335x-bone, am335x-evm, and am335x-evmsk.
> Also added is the DMA binding definitions based on the generic DMA
> request binding.
>
> The HWMOD data removal was breaking MMC so some new properties like
Hi
Here are some fixes and tweaks to perf tools (version 7).
Changes in V7:
perf: Update perf_event_type documentation
Proposed new patch from Peter Zijlstra
perf: make events stream always parsable
Adjustments due to patch above
perf
Quoting Eric W. Biederman (ebied...@xmission.com):
> "Serge E. Hallyn" writes:
>
> > I'm not "relying on LSM" to make these safe. I'm relying on the
> > uid mappings to make these safe.
> >
> > Nevertheless I at least have hope of working around the others (in a
> > distro-acceptable way), so
On Wed, Jul 17, 2013 at 10:38:55AM +0100, Stefano Stabellini wrote:
> There is a very fine line between cursing and what people might perceive
> as a personal attack.
I wanted to stay out of that thread, but that argument really goes over
the top. Look, ANYTHING might be perceived as a personal
Record pid on struct thread. The member is named 'pid_'
to avoid confusion with the 'tid' member which was previously
named 'pid'.
Signed-off-by: Adrian Hunter
---
tools/perf/util/machine.c | 16 +++-
tools/perf/util/thread.c | 3 ++-
tools/perf/util/thread.h | 3 ++-
3 files
It is useful to see the arguments to perf_event_open
and whether the perf events ring buffer was mmapped
per-cpu or per-thread. That information will now be
displayed when verbose is 2 i.e option -vv
Signed-off-by: Adrian Hunter
Acked-by: Jiri Olsa
---
tools/perf/util/evlist.c | 3 +++
The event stream is not always parsable because the format of a sample
is dependent on the sample_type of the selected event. When there
is more than one selected event and the sample_types are not the
same then parsing becomes problematic. A sample can be matched to its
selected event using the
Add a new parameter for 'pid' to machine__findnew_thread().
Change callers to pass 'pid' when it is known.
Signed-off-by: Adrian Hunter
---
tools/perf/builtin-inject.c | 2 +-
tools/perf/builtin-kmem.c | 3 ++-
tools/perf/builtin-kvm.c | 3 ++-
tools/perf/builtin-lock.c | 3
Now that the sample parsing correctly checks data sizes
there is no reason for it to be done again for callchains.
Signed-off-by: Adrian Hunter
---
tools/perf/util/callchain.c | 8
tools/perf/util/callchain.h | 5 -
tools/perf/util/session.c | 20
3 files
From: Peter Zijlstra
Due to a discussion with Adrian I had a good look at the perf_event_type record
layout and found the documentation to be somewhat unclear.
Cc: Adrian Hunter
Signed-off-by: Peter Zijlstra
---
include/uapi/linux/perf_event.h | 19 ++-
kernel/events/core.c
struct ip_event assumes fixed positions for ip, pid
and tid. That is no longer true with the addition of
PERF_SAMPLE_IDENTIFIER.
struct ip_event is no longer used except by hists_link.c.
Move it there.
Signed-off-by: Adrian Hunter
---
tools/perf/tests/hists_link.c | 23 +++
The size of data retrieved from a sample event must be
validated to ensure it does not go past the end of the
event. That was being done sporadically and without
considering integer overflows.
Signed-off-by: Adrian Hunter
---
tools/perf/util/evsel.c | 102
struct ip_event assumes fixeed positions for ip, pid
and tid. That is no longer true with the addition of
PERF_SAMPLE_IDENTIFIER. The information is anyway in
struct sample, so use that instead.
Signed-off-by: Adrian Hunter
---
tools/perf/builtin-inject.c | 4 ++--
Add a test that checks that sample parsing is correctly
implemented.
Signed-off-by: Adrian Hunter
---
tools/perf/Makefile | 1 +
tools/perf/tests/builtin-test.c | 4 +
tools/perf/tests/sample-parsing.c | 263 ++
tools/perf/tests/tests.h
Add perf_event__sample_event_size() which can be used when
synthesizing sample events to determine how big the resulting
event will be, and therefore how much memory to allocate.
Signed-off-by: Adrian Hunter
---
tools/perf/util/event.h | 2 ++
tools/perf/util/evsel.c | 81
On 16/07/13 18:09, Peter Zijlstra wrote:
> On Tue, Jul 16, 2013 at 09:49:31AM +0300, Adrian Hunter wrote:
>
>> If you want the ID at the first position in the ID sample, it is do-able.
>> It means perf tools will have to be changed to calculate the variable start
>> position of the ID sample, and
Expand perf_event__synthesize_sample() to handle all
sample format bits.
Signed-off-by: Adrian Hunter
---
tools/perf/builtin-inject.c | 3 +-
tools/perf/util/event.h | 1 +
tools/perf/util/evsel.c | 70 -
3 files changed, 72 insertions(+), 2
Sample types need not be identical to determine
the sample id from the event. Only the position
of the sample id needs to be the same.
Compatible sample types are ones in which the bits
defined by PERF_COMPAT_MASK are the same.
'perf_evlist__config()' forces sample types to be
compatible on that
Enable parsing of samples with sample format bit
PERF_SAMPLE_IDENTFIER. In addition, if the kernel supports
it, prefer it to selecting PERF_SAMPLE_ID thereby avoiding
the need to force compatible sample types.
Signed-off-by: Adrian Hunter
---
tools/perf/tests/mmap-basic.c | 2 +-
> -Original Message-
> From: K. Y. Srinivasan [mailto:k...@microsoft.com]
> Sent: Tuesday, July 02, 2013 1:32 PM
> To: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat.com
> Cc: KY Srinivasan
>
On Wed, 17 Jul 2013, Pawel Moll wrote:
> On Tue, 2013-07-16 at 17:05 +0100, Lorenzo Pieralisi wrote:
> > /drivers/mfd is probably not the right place for this code as it stands (but
> > probably will be when the entire driver, with DVFS and config interface, is
> > complete).
>
> Not that it
On 07/17/2013 02:57 PM, Roger Quadros wrote:
Hi Grygorii,
On 07/17/2013 02:41 PM, Grygorii Strashko wrote:
Hi Tony, Kevin
This patch series introduces dynamic pinctrl handling in OMAP device framework
in the same way as it was before switching to DT.
This allow OMAP devices driver's
Slashdot is just a cesspool of trolls, not a good comparison.
On 17 July 2013 13:21, Steven Rostedt wrote:
>
> On Wed, 2013-07-17 at 07:51 +0200, Willy Tarreau wrote:
>
> > I don't believe this is that much practiced on LKML. I know at least
> > one developer who does this, but he's probably
On Tue, Jul 16, 2013 at 08:23:33PM +0200, Ortwin Glück wrote:
> Without NetworkManager, no X, on console and with plain jane wpa_supplicant I
> do
> echo mem > /sys/power state
>
> After that, it still responds to keyboard events: I can switch VT
> and type on the consoles, but I can not login
drivers/net/ethernet/i825xx/sun3_82586.c: In function 'sun3_82586_timeout':
drivers/net/ethernet/i825xx/sun3_82586.c:993:89: warning: array subscript is
above array bounds [-Warray-bounds]
Using the default NUM_XMIT_BUFFS = 1, there's only one transmit buffer.
Hence accessing the second buffer
On Wed, 17 Jul 2013, Mark Brown wrote:
> From: Mark Brown
>
> The jack detection code holds runtime PM references when required so
> there is no need for suspend to do any checks.
>
> Signed-off-by: Mark Brown
> ---
> drivers/mfd/wm8994-core.c | 14 --
> 1 file changed, 14
On Wed, 2013-07-17 at 07:51 +0200, Willy Tarreau wrote:
> I don't believe this is that much practiced on LKML. I know at least
> one developer who does this, but he's probably the exception. I more
> often see counter proposals just as if two authors were fighting to
> get their patch merged.
Hi Prabhakar,
On Saturday 13 July 2013 14:20:26 Prabhakar Lad wrote:
> From: "Lad, Prabhakar"
>
> This patch series replaces existing resource handling in the
> driver with managed device resource.
Thank you for the patches. They greatly simplify the probe/remove functions, I
like that. For
On Wed, Jul 17, 2013 at 05:20:31AM +0100, Phillip Lougher wrote:
> On 15 July 2013 17:17, Dan Carpenter wrote:
> > We read the size of the name from the disk, but a larger name than
> > expected would cause memory corruption.
>
> Thanks for the patch, it's queued for the next merge window.
We read the size of the name from the disk, but a larger name than
expected would cause memory corruption.
Signed-off-by: Dan Carpenter
---
v2: style change
diff --git a/fs/squashfs/namei.c b/fs/squashfs/namei.c
index 7834a51..bc1334c 100644
--- a/fs/squashfs/namei.c
+++ b/fs/squashfs/namei.c
This series should fix the long standing reset storm
issue in mei suspend/resume failure
The issue was reported in few places:
https://lkml.org/lkml/2013/6/26/693
https://lkml.org/lkml/2013/7/14/69
Tomas Winkler (4):
mei: hbm: fix typo in error message
mei: me: fix reset state machine
From: Mark Brown
Since enabling VMID takes a runtime PM reference there is no need to
suppress suspend when doing a runtime suspend. Similarly the digital
inputs and outputs are DAPM widgets and therefore the ASoC core will
be holding a reference for them.
This used to be required when
From: Mark Brown
The jack detection code holds runtime PM references when required so
there is no need for suspend to do any checks.
Signed-off-by: Mark Brown
---
drivers/mfd/wm8994-core.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/drivers/mfd/wm8994-core.c
Hi,
On 07/17/2013 01:37 PM, Michal Simek wrote:
> Hi Ohad,
>
> I am working on another remoteproc driver.
> Currently less problematic than arm-arm.
> It is arm to microblaze on zynq.
>
> I have two problems:
> 1. I need to allocate carveout first because my firmware must be added to that
>
1. MEI_INTEROP_TIMEOUT is in seconds not in jiffies
so we use mei_secs_to_jiffies macro
While cold boot is fast this is relevant in resume
2. wait_event_interruptible_timeout can return with
-ERESTARTSYS so do not override it with -ETIMEDOUT
3.Adjust error message
Signed-off-by: Tomas Winkler
writet -> write
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/hbm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/mei/hbm.c b/drivers/misc/mei/hbm.c
index f9296ab..6127ab6 100644
--- a/drivers/misc/mei/hbm.c
+++ b/drivers/misc/mei/hbm.c
@@ -167,7 +167,7 @@
ME HW ready bit is down after hw reset was asserted or on error.
Only on error we need to enter the reset flow, additional reset
need to be prevented when reset was triggered during
initialization , power up/down or a reset is already in progress
Signed-off-by: Tomas Winkler
---
When powering up, we don't have to clean up the device state
nothing is connected.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/init.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/misc/mei/init.c b/drivers/misc/mei/init.c
index ed1d752..e6f16f8 100644
---
On Wed, Jul 17, 2013 at 12:52:49PM +0100, Lee Jones wrote:
> I don't see the duplicate?
It seems Samuel already applied this but git did the wrong thing during
rebase and discarded the subsequent commit which removed the
non-duplicate copy rather than the first commit which had been applied.
The
On 07/17/2013 10:14 AM, Jonas Jensen wrote:
> On 16 July 2013 17:01, Daniel Lezcano wrote:
>> 1. could you elaborate the patch log: as it is a new driver, a nice
>> description of the timer hardware would be valuable for people willing
>> to understand the code (eg. some specificities of the
On Wed, Jul 17, 2013 at 1:51 PM, Takashi Iwai wrote:
> Looks like CONFIG_SND_HDA_CODEC_ANALOG=y is missing.
That was it!!
At last I’ve got sound again!
Thank you very much for your help! Much appreciated.
Cheers!
--
Kiko
--
To unsubscribe from this list: send the line "unsubscribe
On Wed, 2013-07-17 at 13:38 +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 17, 2013 09:16:38 AM Igor Gnatenko wrote:
> > On Wed, 2013-07-17 at 00:01 +0200, Rafael J. Wysocki wrote:
> > > On Tuesday, July 16, 2013 05:08:16 PM Matthew Garrett wrote:
> > > > On Tue, 2013-07-16 at 17:32 +0400,
On Wed, 17 Jul 2013, Mark Brown wrote:
> From: Mark Brown
>
> The Kconfig prompt for WM8997 says "Support for..." while the other MFD
> Kconfigs (including the adjacent ones for other Arizona devices) just
> list the device name which sticks out like a sore thumb when doing
> configuration.
>
On Wed, 17 Jul 2013, Mark Brown wrote:
> From: Mark Brown
>
> Since enabling VMID takes a runtime PM reference there is no need to
> suppress suspend when doing a runtime suspend. Similarly the digital
> inputs and outputs are DAPM widgets and therefore the ASoC core will
> be holding a
Hi Grygorii,
On 07/17/2013 02:41 PM, Grygorii Strashko wrote:
> Hi Tony, Kevin
>
> This patch series introduces dynamic pinctrl handling in OMAP device framework
> in the same way as it was before switching to DT.
> This allow OMAP devices driver's developers to simply add dynamic pinctrl
>
On Wed, Jul 17, 2013 at 12:50 AM, Shawn Guo wrote:
> On Tue, Jul 16, 2013 at 09:56:12AM -0300, Otavio Salvador wrote:
>> The i.MX23EVK board provides a USB port so the USB PHY and controller
>> need to be enabled for it to be usable.
>>
>> Signed-off-by: Otavio Salvador
>
> There is a typo
On Wed, 17 Jul 2013, Mark Brown wrote:
> From: Mark Brown
>
> Probably the result of a mismerge or rebase failing to notice that the
> hunk had already been applied.
>
> Signed-off-by: Mark Brown
> ---
> drivers/mfd/wm8994-core.c | 14 --
> 1 file changed, 14 deletions(-)
>
>
Tim Chen wrote:
> Herbert, seems like modules.dep generator wants explicit
>
> - select CRYPTO_CRCT10DIF
> + depends on CRYPTO_CRCT10DIF
>
> But it seems to me like it should have known CRC_T10DIF needs
> CRYPTO_CRCT10DIF when we do
> select CRYPTO_CRCT10DIF
>
> Your thoughts?
Hi Tony,
On 07/16/2013 12:05 PM, Tony Lindgren wrote:
Hi all,
As discussed earlier, the pinctrl support for changing some of the
consumer device pins during runtime needs some improvment.
Here are the patches to do that, I'll also post a minimal sample
patch as a reply to this thread on how
At Wed, 17 Jul 2013 12:47:51 +0200,
Kiko Piris wrote:
>
> On 17/07/2013 at 12:31 +0200, Takashi Iwai wrote:
>
> > Could you give alsa-info.sh outputs on both working and non-working
> > kernels? This will give more detailed information.
> > Run alsa-info.sh with --no-upload option and attach
701 - 800 of 1924 matches
Mail list logo
