2018-01-31 17:22 GMT+08:00 Jiri Olsa :
> On Mon, Jan 29, 2018 at 11:48:09PM +0800, weiping zhang wrote:
>> if use -G with one cgroup and -e with multiple events, only the first
>> event has correct cgroup setting, all events from the second will track
>> system-wide events.
>>
>> if user want track
Hello,
Hans reported he sees a few warnings when compiling CEU driver with gcc7.3.0
I have silenced them, and the one reported in "probe" was actually a bug.
That's the diff from v10:
diff --git a/drivers/media/platform/renesas-ceu.c
b/drivers/media/platform/renesas-ceu.c
index 6624fba..cfabe
Add renesas-ceu header file.
Do not remove the existing sh_mobile_ceu.h one as long as the original
driver does not go away.
Signed-off-by: Jacopo Mondi
Reviewed-by: Laurent Pinchart
Acked-by: Hans Verkuil
---
include/media/drv-intf/renesas-ceu.h | 26 ++
1 file change
Remove soc_camera framework dependencies from ov772x sensor driver.
- Handle clock and gpios
- Register async subdevice
- Remove soc_camera specific g/s_mbus_config operations
- Change image format colorspace from JPEG to SRGB as the two use the
same colorspace information but JPEG makes assumpti
Add support to ov772x driver for frame intervals handling and enumeration.
Tested with 10MHz and 24MHz input clock at VGA and QVGA resolutions for
10, 15 and 30 frame per second rates.
Signed-off-by: Jacopo Mondi
Reviewed-by: Laurent Pinchart
Acked-by: Hans Verkuil
---
drivers/media/i2c/ov772x
Copy the soc_camera based driver in v4l2 sensor driver directory.
This commit just copies the original file without modifying it.
No modification to KConfig and Makefile as soc_camera framework
dependencies need to be removed first in next commit.
Signed-off-by: Jacopo Mondi
Acked-by: Laurent Pin
Hi Michal,
Please, let me know if any action is expected from my end.
Thank you for your support and sorry for the ifdef troubles.
Best regards,
Eugeniu.
On Thu, Feb 22, 2018 at 08:20:37AM +0100, Michal Hocko wrote:
> On Wed 21-02-18 15:58:41, Randy Dunlap wrote:
> > On 02/21/2018 02:48 PM, a...
Migo-R platform uses sh_mobile_ceu camera driver, which is now being
replaced by a proper V4L2 camera driver named 'renesas-ceu'.
Move Migo-R platform to use the v4l2 renesas-ceu camera driver
interface and get rid of soc_camera defined components used to register
sensor drivers and of platform sp
Add Capture Engine Unit (CEU) node to device tree.
Signed-off-by: Jacopo Mondi
Reviewed-by: Geert Uytterhoeven
Reviewed-by: Laurent Pinchart
Acked-by: Hans Verkuil
---
arch/arm/boot/dts/r7s72100.dtsi | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/arch/arm
Add driver for Renesas Capture Engine Unit (CEU).
The CEU interface supports capturing 'data' (YUV422) and 'images'
(NV[12|21|16|61]).
This driver aims to replace the soc_camera-based sh_mobile_ceu one.
Tested with ov7670 camera sensor, providing YUYV_2X8 data on Renesas RZ
platform GR-Peach.
T
Remove soc_camera framework dependencies from tw9910 sensor driver.
- Handle clock and gpios
- Register async subdevice
- Remove soc_camera specific g/s_mbus_config operations
- Add kernel doc to driver interface header file
- Adjust build system
This commit does not remove the original soc_camera
Hi Pankaj,
On 02/22/18 at 05:07am, Pankaj Gupta wrote:
>
> Hi Baoquan,
>
> >
> > In sparse_init(), two temporary pointer arrays, usemap_map and map_map
> > are allocated with the size of NR_MEM_SECTIONS. They are used to store
> > each memory section's usemap and mem map if marked as present. W
Copy the soc_camera based driver in v4l2 sensor driver directory.
This commit just copies the original file without modifying it.
No modification to KConfig and Makefile as soc_camera framework
dependencies need to be removed first in next commit.
Signed-off-by: Jacopo Mondi
Acked-by: Laurent Pin
Add bindings documentation for Renesas Capture Engine Unit (CEU).
Signed-off-by: Jacopo Mondi
Reviewed-by: Rob Herring
Reviewed-by: Laurent Pinchart
Acked-by: Hans Verkuil
---
.../devicetree/bindings/media/renesas,ceu.txt | 81 ++
1 file changed, 81 insertions(+)
cre
gcc-8 warns that we copy TRAMPOLINE_32BIT_CODE_SIZE bytes from the pointer
to the function into actual trampoline, when that pointer is only 8 bytes:
In file included from arch/x86/boot/compressed/pgtable_64.c:3:
arch/x86/boot/compressed/pgtable_64.c: In function 'paging_prepare':
arch/x86/boot/co
On 22 February 2018 at 09:48, James Hogan wrote:
> On Thu, Feb 22, 2018 at 10:26:54AM +0100, Peter Zijlstra wrote:
>> On Wed, Feb 21, 2018 at 11:38:12PM +, James Hogan wrote:
>> > So lets call it a day and drop the Meta architecture port from the
>> > kernel. RIP Meta.
>>
>> So long, and thank
On Thu, Feb 22, 2018 at 11:15:04AM +0100, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 02:58:47PM +0800, Boqun Feng wrote:
> > > And yes, if we go with a purely RCpc interpretation of acquire and
> > > release, then I don't believe the writes in the previous critical
> > > section would be order
>> On Fri 16-02-18 15:14:40, t.vi...@samsung.com wrote:
>> From: Vivek Trivedi
>>
>> If fanotify userspace response server thread is frozen first,
>> it may fail to send response from userspace to kernel space listener.
>> In this scenario, fanotify response listener will never get response
>> fr
Hi Radek
I've tested your change on stm32h743i-eval.dts board
and gpio-keys tests are not functional.
No interrupt occurs when we push or release button
(cat /proc/interrupt).
Board: stm32h743i-eval.dts
Test description: gpio-keys (gpioc 13 => exti 13), with gpio or
interrupt property.
commen
On Thu, Feb 15, 2018 at 11:31:45AM +0530, Keerthy wrote:
> Replace architecture specific guard with clocksource guard.
>
> Signed-off-by: Keerthy
> Replace architecture specific defines with clocksource
This looks like a bit unussual commit log. Also, what about merging
it with previous patch?
Hi Rui,
Thanks for the patchset.
Could you use "dt: bindings: " prefix in the subject?
On Thu, Feb 22, 2018 at 10:23:37AM +, Rui Miguel Silva wrote:
> Add device tree binding documentation for the OV5640 camera sensor.
>
> CC: devicet...@vger.kernel.org
> Signed-off-by: Rui Miguel Silva
>
Hi Ludovic,
I have tested on stm32f429-disco and it works without a problem.
handle_edge_irq is not used in current implementation because it is
substituted by handle_simple_irq in an alloc callback either way which
causes that irq_ack callback is not invoked as well (acking is done in
chained hand
On Wed, Feb 21, 2018 at 10:33:23PM -0800, Ashok Raj wrote:
> After updating microcode on one of the threads in the core, the
> thread sibling automatically gets the update since the microcode
> resources are shared. Check the ucode revision on the CPU before
> performing a ucode update.
>
> Signed
On 2/13/2018 10:28 PM, srinivas.kandaga...@linaro.org wrote:
From: Srinivas Kandagatla
This patch adds support to DB820c machine driver.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/Kconfig | 8 +++
sound/soc/qcom/apq8096.c | 173 +
Important details to share with you, kindly email me for info:
"peter.waddell...@gmail.com" Peter
On Thu, Feb 22, 2018 at 11:40:41AM +0100, Arnd Bergmann wrote:
> gcc-8 warns that we copy TRAMPOLINE_32BIT_CODE_SIZE bytes from the pointer
> to the function into actual trampoline, when that pointer is only 8 bytes:
>
> In file included from arch/x86/boot/compressed/pgtable_64.c:3:
> arch/x86/boo
> > Why? ePAPR says "okay", "disabled", "fail", or "fail-sss".
> >
> > Sorry for missing this in the previous round.
>
> That was per Wolfram's request, and because the existing code uses "ok". I'm
> personally fine with any.
I did? Well, today I don't have a strong preference. Any is fine wit
We will go on initial idev if failed to create debug_root, and it does
not matter to check the return value of this debugfs call, just remove it.
Signed-off-by: Yisheng Xie
---
drivers/staging/android/ion/ion.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/android/ion/ion
On Thu, Feb 22, 2018 at 10:33:50AM +0100, Yves-Alexis Perez wrote:
> On Thu, 2018-02-22 at 12:01 +1100, Michael Ellerman wrote:
> > So I guess this patch is OK for now, but we do need a full back port of
> > 222f20f to 4.9.
>
> Hi,
>
> in the light of this, do you know the full status of protecti
There's no need to check the return value of debug_file for it is just a
debugfs and we will go on the following process if we failed to create
debug_file. So just remove it.
Signed-off-by: Yisheng Xie
---
drivers/staging/android/ion/ion.c | 9 ++---
1 file changed, 2 insertions(+), 7 deleti
On Wed, Feb 21, 2018 at 05:59:34PM +0100, Arnd Bergmann wrote:
> On Wed, Feb 21, 2018 at 11:26 AM, Lorenzo Colitti wrote:
> > On Wed, Feb 14, 2018 at 5:54 PM, Greg KH wrote:
> >> > > IPSEC doesn't work with a 64bit kernel and 32bit userspace right now.
> >> > >
> >> > > Back in 2015 someone start
On 02/22/2018 11:25 AM, Javier Gonzalez wrote:
On 22 Feb 2018, at 10.39, Matias Bjørling wrote:
On 02/22/2018 08:47 AM, Javier Gonzalez wrote:
On 22 Feb 2018, at 08.28, Matias Bjørling wrote:
On 02/21/2018 10:26 AM, Javier González wrote:
Both 1.2 and 2.0 specs define a field for media a
> On 22 Feb 2018, at 12.10, Matias Bjørling wrote:
>
> On 02/22/2018 11:25 AM, Javier Gonzalez wrote:
>>> On 22 Feb 2018, at 10.39, Matias Bjørling wrote:
>>>
>>> On 02/22/2018 08:47 AM, Javier Gonzalez wrote:
> On 22 Feb 2018, at 08.28, Matias Bjørling wrote:
>
>> On 02/21/2018 1
Thanks for the review,
On 22/02/18 11:00, Rohit Kumar wrote:
+config SND_SOC_MSM8996
+tristate "SoC Machine driver for MSM8996 and APQ8096 boards"
+depends on QCOM_APR
+select SND_SOC_QDSP6V2
should be select SND_SOC_QDSP6, V2 is not defined
I will fix this in next version.
--sri
Thanks for your review Rohit,
On 21/02/18 11:14, Rohit Kumar wrote:
On 2/13/2018 10:28 PM, srinivas.kandaga...@linaro.org wrote:
From: Srinivas Kandagatla
This patch adds support to q6asm dai driver which configures Q6ASM
streams
to pass pcm data.
Signed-off-by: Srinivas Kandagatla
[..
On Thu, Feb 22, 2018 at 12:10 PM, Greg KH wrote:
> On Wed, Feb 21, 2018 at 05:59:34PM +0100, Arnd Bergmann wrote:
>> On Wed, Feb 21, 2018 at 11:26 AM, Lorenzo Colitti wrote:
>> > On Wed, Feb 14, 2018 at 5:54 PM, Greg KH
>> > wrote:
>> >> > > IPSEC doesn't work with a 64bit kernel and 32bit user
On arm64, no trampline code between old kernel and new kernel will be
required in kexec_file implementation. This patch introduces a new
configuration, ARCH_HAS_KEXEC_PURGATORY, and allows related code to be
compiled in only if necessary.
Signed-off-by: AKASHI Takahiro
Cc: Dave Young
Cc: Vivek G
This is the eighth round of implementing kexec_file_load() support
on arm64.[1]
Most of the code is based on kexec-tools (along with some kernel code
from x86, which also came from kexec-tools).
This patch series enables us to
* load the kernel by specifying its file descriptor, instead of user
This function, being a variant of walk_system_ram_res() introduced in
commit 8c86e70acead ("resource: provide new functions to walk through
resources"), walks through a list of all the resources of System RAM
in reversed order, i.e., from higher to lower.
It will be used in kexec_file implementati
exclude_mem_range() and prepare_elf64_headers() can be re-used on other
architectures, including arm64, as well. So let them factored out so as to
move them to generic side in the next patch.
fill_up_crash_elf_data() can potentially be commonalized for most
architectures who want to go through io
The initial user of this system call number is arm64.
Signed-off-by: AKASHI Takahiro
Acked-by: Arnd Bergmann
---
include/uapi/asm-generic/unistd.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/uapi/asm-generic/unistd.h
b/include/uapi/asm-generic/unistd.h
index
As arch_kexec_kernel_*_{probe,load}(), arch_kimage_file_post_load_cleanup()
and arch_kexec_kernel_verify_sg can be parameterized with a kexec_file_ops
array and now duplicated among some architectures, let's factor them out.
Signed-off-by: AKASHI Takahiro
Cc: Dave Young
Cc: Vivek Goyal
Cc: Baoq
In the previous patch, commonly-used routines were carved out. Now place
them in kexec common code.
Signed-off-by: AKASHI Takahiro
Cc: Dave Young
Cc: Vivek Goyal
Cc: Baoquan He
---
arch/x86/kernel/crash.c | 183
include/linux/kexec.h | 19 ++
To enable crash dump (kdump), we need to
* prepare the contents of ELF header of /proc/vmcore through
load_crashdump_segments(), and
* set up two device tree properties, "linux,usable-memory-range" and
"linux,elfcorehdr", which repsectively represent a memory range to be
used on crash dump ke
On arm64, purugatory would do almosty nothing. So just invoke the second
kernel by jumping into the entry code directly.
While, in this case, cpu_soft_restart() must be called in a specific way,
it still stays compatible with kexec as far as the fifth argument is null.
Signed-off-by: AKASHI Takah
This patch provides kexec_file_ops for "Image"-format kernel. Please note
that a binary is always loaded at an offset based on its text_offset field.
While this patch doesn't contains CONFIG_KEXEC_VERIFY_SIG support,
that is to be added in a later patch in this series, file-attribute-based
kernel
load_other_segments() sets up and adds all the memory segments necessary
other than kernel, including initrd and device-tree blob.
Most of the code was borrowed from kexec-tools' counterpart.
arch_kimage_kernel_post_load_cleanup() is meant to free arm64-specific data
allocated in load_other_segmen
Modify arm64/Kconfig to enable kexec_file_load support.
Signed-off-by: AKASHI Takahiro
Cc: Catalin Marinas
Cc: Will Deacon
---
arch/arm64/Kconfig | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 7381eeb7ef8e..79ee27b8d2a0 100644
---
With this patch, kernel verification can be done without IMA security
subsystem enabled. Turn on CONFIG_KEXEC_VERIFY_SIG instead.
On x86, a signature is embedded into a PE file (Microsoft's format) header
of binary. Since arm64's "Image" can also be seen as a PE file as far as
CONFIG_EFI is enable
message[] field won't be part of the definition of mz header.
This change is crucial for enabling kexec_file_load on arm64 because
arm64's "Image" binary, as in PE format, doesn't have any data for it and
accordingly the following check in pefile_parse_binary() will fail:
chkaddr(cursor,
From: Miles Chen
Marty reported a memory leakage introduced by commit 3aaabbf1c39e
("lib/dma-debug.c: fix incorrect pfn calculation"). Fix it
by checking the virtual address before allocating the entry.
This patch also use virt_addr_valid() instead of virt_to_page()
to check if a virtual address
Signed-off-by: Thomas Gleixner
---
kernel/irq/manage.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -855,10 +855,14 @@ irq_thread_check_affinity(struct irq_des
* This code is triggered unconditionally. Check th
When a irq vector is replaced, then the previous vector is normally
released when the first interrupt happens on the new vector. If the target
CPU of the previous vector is already offline when the new vector is
installed, then the previous vector is silently discarded, which leads to
accounting is
Yuriy reported suspend/resume issues related to the irq vector management.
They turned out to be an accounting issue related to CPU hot unplug where
vectors which are allocated on unplugged CPUs are dropped from the
accounting because not started interrupts are not force migrated.
The following p
At CPU hotunplug the corresponding per cpu matrix allocator is shut down and
the allocated interrupt bits are discarded under the assumption that all
allocated bits have been either migrated away or shut down through the
managed interrupts mechanism.
This is not true because interrupts which are n
On Thu, Feb 22, 2018 at 12:02 PM, Kirill A. Shutemov
wrote:
> On Thu, Feb 22, 2018 at 11:40:41AM +0100, Arnd Bergmann wrote:
>> gcc-8 warns that we copy TRAMPOLINE_32BIT_CODE_SIZE bytes from the pointer
>> to the function into actual trampoline, when that pointer is only 8 bytes:
>>
>> In file inc
gcc-8 warns that we copy TRAMPOLINE_32BIT_CODE_SIZE bytes from the pointer
to the function into actual trampoline, when that pointer is only 8 bytes:
In file included from arch/x86/boot/compressed/pgtable_64.c:3:
arch/x86/boot/compressed/pgtable_64.c: In function 'paging_prepare':
arch/x86/boot/co
Bah, scratch that. That's a different story and I missed to remove that
patch from the quilt series.
On Thu, 22 Feb 2018, Thomas Gleixner wrote:
> Signed-off-by: Thomas Gleixner
> ---
> kernel/irq/manage.c | 10 +++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> --- a/kerne
On Thu, Feb 22, 2018 at 7:23 AM, Rui Miguel Silva wrote:
> Add device tree binding documentation for the OV5640 camera sensor.
s/OV5640/OV2680
On Wed, Feb 21, 2018 at 06:32:46PM -0800, Saravana Kannan wrote:
> On 01/02/2018 03:25 AM, Suzuki K Poulose wrote:
> > +static int dsu_pmu_event_init(struct perf_event *event)
> > +{
> > + struct dsu_pmu *dsu_pmu = to_dsu_pmu(event->pmu);
> > +
> > + if (event->attr.type != event->pmu->type)
>
On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote:
[...]
> > In your case the platform code that adds the lookup may be identical to
> > the code that registers the struct reset_controller_dev, but that
> > doesn't have to be the case. I'm not sure how that is supposed to work
> > for the phy
On Wed, Feb 21, 2018 at 04:51:40PM +, Robin Murphy wrote:
> On 21/02/18 16:14, Shanker Donthineni wrote:
> [...]
> > > > @@ -1100,6 +1114,20 @@ static int cpu_copy_el2regs(void *__unused)
> > > > .enable = cpu_clear_disr,
> > > > },
> > > > #endif /* CONFIG_ARM64_RAS_E
On Wed, Feb 21, 2018 at 6:15 PM, Simon Horman wrote:
> On Tue, Feb 20, 2018 at 04:46:23PM +0100, Geert Uytterhoeven wrote:
>> On Tue, Feb 20, 2018 at 4:12 PM, Jacopo Mondi
>> wrote:
>> > Add basic support for R-Car Salvator-X M3-N (R8A77965) board.
>> >
>> > Based on original work from:
>> > Tak
On Wed, Feb 21, 2018 at 9:29 PM, Eric W. Biederman
wrote:
> Ensure the translation happens by failing to read or write
> posix acls when the filesystem has not indicated it supports
> posix acls.
For the first iteration this is fine, but we could convert the raw
xattrs as well, if we later want
Despite the efforts made to correctly read the NDA and CUBC registers,
the order in which the registers are read could sometimes lead to an
inconsistent state.
Re-using the timeline from the comments, this following timing of
registers reads could lead to reading NDA with value "@desc2" and
CUBC w
Hi,
On Wed, Feb 21, 2018 at 09:55:08PM +0100, Alexandre Belloni wrote:
> The RTC core is always calling rtc_valid_tm after the read_time callback.
> It is not necessary to call it just before returning from the callback.
>
> Signed-off-by: Alexandre Belloni
> ---
> drivers/rtc/rtc-cpcap.c | 2 +
On Thu, 22 Feb 2018 00:01:29 +0900
Masami Hiramatsu wrote:
> Add a testcase for symbol type with kprobe event.
> This tests good/bad syntax combinations and also
> the traced data.
> If the kernel doesn't support symbol type, it skips
> the test as UNSUPPORTED.
>
> Signed-off-by: Masami Hiramats
On Wed, Feb 21, 2018 at 10:33:25PM -0800, Ashok Raj wrote:
> Microcode updates during OS load always assumed the other hyper-thread
> was "quiet", but Linux never really did this. We've recently received
> several issues on this, where things did not go well at scale
> deployments, and the Intel mi
Declaring a static function in a header leads to a warning every
time that header gets included without the function being used:
In file included from drivers/net/dsa/mv88e6xxx/chip.c:42:
drivers/net/dsa/mv88e6xxx/ptp.h:92:13: error: 'mv88e6xxx_hwtstamp_work' defined
but not used [-Werror=unused-
The removal of the batched object freeing has caused the debug_objects_freed
to become read-only, and the reading is inside an ifdef, so gcc warns that it
is completely unused without CONFIG_DEBUG_FS:
lib/debugobjects.c:71:14: error: 'debug_objects_freed' defined but not used
[-Werror=unused-vari
On linux-next, I get a build failure in some configurations:
drivers/perf/arm_spe_pmu.c: In function 'arm_spe_pmu_setup_aux':
drivers/perf/arm_spe_pmu.c:857:14: error: implicit declaration of function
'vmap'; did you mean 'swap'? [-Werror=implicit-function-declaration]
buf->base = vmap(pglist,
On Tue, Feb 20, 2018 at 11:32:25AM +, Horia Geantă wrote:
>
> If final/finup is optional, how is the final hash supposed to be retrieved?
Sometimes the computation ends with a partial hash, that's what
export is for. Also it is completely legal to abandon the hash
state entirely.
> According
When comparing two variables with min()/max(), they should be the same type:
drivers/gpu/drm/drm_memory.c: In function 'drm_get_max_iomem':
include/linux/kernel.h:821:16: error: comparison of distinct pointer types
lacks a cast [-Werror]
(void) (&max1 == &max2);
This makes the local variable i
Since the 'commit d3deafaa8b5c ("lib/: make RUNTIME_TESTS a menuconfig
to ease disabling it all")', the make kselftest-merge cannot merge the
config dependencies of kselftest to the existing .config file.
These config dependencies of kselftest need to enable the
'CONFIG_RUNTIME_TESTING_MENU=y' at
I have information about your relative please write me back through (
geraldwalker...@gmail.com ) for more details.
On Thu, Feb 22, 2018 at 12:00:57PM +0100, Borislav Petkov wrote:
> >
> > Updates:
> > v2: Address Boris's to cleanup apply_microcode_intel
> > v3: Fixups per Ingo: Spell Checks
>
> That changelog...
>
> > ---
>
> ... comes under this line so that it can be ignored by tools.
Oops! using stg, an
ree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Enric-Balletbo-i-Serra/platform-chrome-cros_ec-debugfs-and-sysfs-updates/20180222-074242
> base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
> fo
On Thu, Feb 22, 2018 at 06:45:32PM +0800, Boqun Feng wrote:
> Maybe it's me who misunderstand Daniel's words. But my understanding is
> that riscv people are on a debate about whether their "RCpc" atomic
> instructions need to be more strict: release+acquire pair orders two
> writes. And I thought
On Thu, 2018-02-22 at 12:08 +0100, Greg Kroah-Hartman wrote:
> Did you look at /sys/devices/system/cpu/vulnerabilities/ to see what the
> files there say?
Unfortunately I don't have access to a powerpc box where I could run a new
kernel and try it on. I'll check with our ppc porters and see if I c
Hi all,
Please give feedback on these patches which extends the PWM framework in
order to support multiple PWM modes of operations. This series is a rework
of [1] and [2].
The current patch series add the following PWM modes:
- PWM mode normal
- PWM mode complementary
- PWM mode push-pull
Normal
Add basic PWM modes: normal and complementary. These modes should
differentiate the single output PWM channels from two outputs PWM
channels. These modes could be set as follow:
1. PWM channels with one output per channel:
- normal mode
2. PWM channels with two outputs per channel:
- normal mode
-
Add PWM mode to pwm_config() function. The drivers which uses pwm_config()
were adapted to this change.
Signed-off-by: Claudiu Beznea
---
arch/arm/mach-s3c24xx/mach-rx1950.c | 11 +--
drivers/bus/ts-nbus.c| 2 +-
drivers/clk/clk-pwm.c| 3 ++-
drivers/gp
Populate PWM mode in of_xlate function to avoid pwm_apply_state() failure.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-pxa.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/pwm/pwm-pxa.c b/drivers/pwm/pwm-pxa.c
index 4143a46684d2..7a035716e054 100644
--- a/drivers/pwm/pwm-p
Populate PWM mode in of_xlate function to avoid pwm_apply_state() failure.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-cros-ec.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/pwm/pwm-cros-ec.c b/drivers/pwm/pwm-cros-ec.c
index 9c13694eaa24..e54954c13323 100644
--- a/drive
Add PWM normal and complementary modes.
Signed-off-by: Claudiu Beznea
---
Documentation/devicetree/bindings/pwm/pwm.txt | 9 +++--
Documentation/pwm.txt | 26 +++---
include/dt-bindings/pwm/pwm.h | 1 +
3 files changed, 31 inserti
Add pwm capabilities for Atmel/Microchip PWM controllers.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-atmel.c | 80 -
1 file changed, 52 insertions(+), 28 deletions(-)
diff --git a/drivers/pwm/pwm-atmel.c b/drivers/pwm/pwm-atmel.c
index 530d
Add documentation for PWM push-pull mode.
Signed-off-by: Claudiu Beznea
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/pwm/pwm.txt | 2 ++
Documentation/pwm.txt | 16
include/dt-bindings/pwm/pwm.h | 1 +
3 files changed,
Add support for PWM push-pull mode. This is only supported by SAMA5D2 SoCs.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-atmel.c | 40
1 file changed, 36 insertions(+), 4 deletions(-)
diff --git a/drivers/pwm/pwm-atmel.c b/drivers/pwm/pwm-atmel.c
in
Hi Laurent,
On Wed, Feb 21, 2018 at 10:28:06PM +0200, Laurent Pinchart wrote:
> Hi Jacopo,
>
> On Tuesday, 20 February 2018 10:58:57 EET jacopo mondi wrote:
> > On Mon, Feb 19, 2018 at 09:19:32PM +0200, Laurent Pinchart wrote:
> > > On Monday, 19 February 2018 18:59:44 EET Jacopo Mondi wrote:
> >
Fix the following sparse warning by moving the prototype
of kvm_arch_mmu_notifier_invalidate_range() to linux/kvm_host.h .
CHECK arch/s390/kvm/../../../virt/kvm/kvm_main.c
arch/s390/kvm/../../../virt/kvm/kvm_main.c:138:13: warning: symbol
'kvm_arch_mmu_notifier_invalidate_range' was not decla
Move the kvm_arch_irq_routing_update() prototype outside of
ifdef CONFIG_HAVE_KVM_EVENTFD guards to fix the following sparse warning:
arch/s390/kvm/../../../virt/kvm/irqchip.c:171:28: warning: symbol
'kvm_arch_irq_routing_update' was not declared. Should it be static?
Signed-off-by: Sebastian Ot
Add push-pull mode support. In push-pull mode the channels' outputs have
same polarities and the edges are complementary delayed for one period.
Signed-off-by: Claudiu Beznea
---
include/linux/pwm.h | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/include/linux/pwm.h b
Populate PWM mode in of_xlate function to avoid pwm_apply_state() failure.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-clps711x.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/drivers/pwm/pwm-clps711x.c b/drivers/pwm/pwm-clps711x.c
index 26ec24e457b1..2a4
On Thu, Feb 22, 2018 at 12:47:05PM +0100, Arnd Bergmann wrote:
> On linux-next, I get a build failure in some configurations:
>
> drivers/perf/arm_spe_pmu.c: In function 'arm_spe_pmu_setup_aux':
> drivers/perf/arm_spe_pmu.c:857:14: error: implicit declaration of function
> 'vmap'; did you mean 's
Hi Jacopo,
On Thursday, 22 February 2018 14:04:12 EET jacopo mondi wrote:
> On Wed, Feb 21, 2018 at 10:28:06PM +0200, Laurent Pinchart wrote:
> > On Tuesday, 20 February 2018 10:58:57 EET jacopo mondi wrote:
> > > On Mon, Feb 19, 2018 at 09:19:32PM +0200, Laurent Pinchart wrote:
> > > > On Monday,
This patchset solves the same problem as my previous one[1] but follows
a rather different approach. Instead of implementing DISCONTIGMEM for
PowerPC32, I simply switched the "is this RAM" check in __ioremap_caller
to the existing page_is_ram function, and unified page_is_ram to search
memblock.mem
On Thu, Feb 22, 2018 at 03:55:54AM -0800, Raj, Ashok wrote:
> The current code wasn't trying to enforce checking the loaded microcode
> revision on a thread
> before attempting to load the microcode. While you comeback from resume, if
> C0T0 already
> is up, and we loaded the early microcode, the
To support accurate checking for different blocks of memory on PPC32,
use the same memblock-based approach that's already used on PPC64 also
on PPC32.
Signed-off-by: Jonathan Neuschäfer
---
arch/powerpc/mm/mem.c | 4
1 file changed, 4 deletions(-)
diff --git a/arch/powerpc/mm/mem.c b/arch/
Le 22/02/2018 à 05:17, Alastair D'Silva a écrit :
From: Alastair D'Silva
Some required information is not exposed to userspace currently (eg. the
PASID), pass this information back, along with other information which
is currently communicated via sysfs, which saves some parsing effort in
user
Signed-off-by: Jonathan Neuschäfer
---
arch/powerpc/platforms/embedded6xx/wii.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/arch/powerpc/platforms/embedded6xx/wii.c
b/arch/powerpc/platforms/embedded6xx/wii.c
index 4682327f76a9..fc00d82691e1 100644
--- a/arc
101 - 200 of 952 matches
Mail list logo
