i.MX7ULP has TPM(Low Power Timer/Pulse Width Modulation Module)
inside, add TPM PWM driver support.
Signed-off-by: Anson Huang
---
Changes since V1:
- improve coding style, function name's prefix;
- improve Kconfig's help info;
- use .apply instead for
Add i.MX TPM(Low Power Timer/Pulse Width Modulation Module) PWM binding.
Signed-off-by: Anson Huang
---
Changes since V1:
- remove optional property which is no need now.
---
Documentation/devicetree/bindings/pwm/imx-tpm-pwm.txt | 19 +++
1 file changed, 19 insertions(+)
i.MX7ULP EVK board has MIPI-DSI display, its backlight is supplied
by TPM PWM module, this patch set enables i.MX7ULP TPM PWM driver
support and also add backlight support for MIPI-DSI display.
Anson Huang (5):
dt-bindings: pwm: Add i.MX TPM PWM binding
pwm: Add i.MX TPM PWM driver support
Hi Suravee,
Please see below..
On 03/11/2019 01:38 PM, Suthikulpanit, Suravee wrote:
Hi Oren,
Sorry for delay response.
On 3/5/19 1:15 AM, Oren Twaig wrote:
Hello Suravee,
According to AMD's SDM, the target-not-running incomplete
ipi exit is only received if any of the destination cpus had
Hi, Uwe
Best Regards!
Anson Huang
> -Original Message-
> From: Uwe Kleine-König [mailto:u.kleine-koe...@pengutronix.de]
> Sent: 2019年3月11日 17:27
> To: Anson Huang
> Cc: thierry.red...@gmail.com; robh...@kernel.org; mark.rutl...@arm.com;
> shawn...@kernel.org; s.ha...@pengutronix.de;
Hi, Ted,
On Wed, Jan 2, 2019 at 8:40 AM kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed a -38.0% regression of fsmark.files_per_sec due to commit:
>
>
> commit: fde872682e175743e0c3ef939c89e3c6008a1529 ("ext4: force inode writes
> when nfsd calls commit_metadata()")
>
On Tue, Mar 12, 2019 at 7:31 PM Marcelo Schmitt
wrote:
>
> On 03/11, Alexandru Ardelean wrote:
> > On Sun, Mar 10, 2019 at 7:47 PM Marcelo Schmitt
> > wrote:
> > >
> > > Add an ABI documentation for the ad5933 driver.
> >
> > There's already an ABI documentation for this driver.
> > See:
> >
Hi Greg,
I was wondering if you think the below ABI addition looks sane to you?
Or, should I ask someone else for a tag?
Cheers,
Peter
On 2019-02-28 12:43, Robert Shearman wrote:
> From: Robert Shearman
>
> The behaviour, by default, to not deselect after each transfer is
> unsafe when there
Add Device Tree for VF610 based Zodiac Seat Power Box.
Signed-off-by: Andrey Smirnov
Cc: Shawn Guo
Cc: Chris Healy
Cc: Andrew Lunn
Cc: Heiner Kallweit
Cc: Fabio Estevam
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-...@nxp.com
---
Changes since [v1]:
On 12.03.19 17:33, Greg KH wrote:
> On Tue, Mar 12, 2019 at 03:57:33PM +0100, Enrico Weigelt, metux IT consult
> wrote:
>> ---
>> drivers/tty/serial/8250/8250_bcm2835aux.c | 12
>> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> No changelog or signed-off-by, sorry, please fix
Hello,
I encountered a regression in current (post-5.0) mainline kernel which I
bisected to commit 1aec4211204d ("parport: daisy: use new parport device
model"). Running "modprobe parport_pc" hangs up:
tweed:~ # ps ax | grep modprobe
1206 pts/0D+ 0:00 modprobe parport_pc
1209 ?
On Tue, Mar 12, 2019 at 10:11 PM Tetsuo Handa
wrote:
>
> On 2019/03/13 2:15, Dmitry Vyukov wrote:
> >> Also, this bisection is finding multiple different crash patterns, which
> >> suggests that the crashed tests are not giving correct feedback to syzbot.
> >
> > Treating different crashes as
On Wed, Mar 13, 2019 at 8:26 AM Kees Cook wrote:
>
> On Mon, Mar 11, 2019 at 1:42 PM syzbot
> wrote:
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ee410b20
> > [...]
> > [ cut here ]
> > Bad or missing usercopy whitelist? Kernel memory exposure
Hi Matthias,
On 2019-03-12 22:29, Matthias Kaehlcke wrote:
+DT folks
Please add them in future versions (script/scripts/get_maintainer.pl
should have listed them)
[Harish] -- Will add them in new version of patches.
On Tue, Mar 12, 2019 at 05:52:59PM +0530, Harish Bandi wrote:
This
On Mon, Mar 11, 2019 at 1:42 PM syzbot
wrote:
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ee410b20
> [...]
> [ cut here ]
> Bad or missing usercopy whitelist? Kernel memory exposure attempt detected
> from SLAB object 'fanotify_event' (offset 40, size
Hi Matthias,
On 2019-03-12 21:59, Matthias Kaehlcke wrote:
Hi Harish,
On Tue, Mar 12, 2019 at 05:52:58PM +0530, Harish Bandi wrote:
Added new compatible for wcn3998 and corresponding voltage
and current values to wcn3998 compatible.
Changed driver code to support wcn3998
Signed-off-by:
On 2019-03-12 12:47, MyungJoo Ham wrote:
From: Saravana Kannan
If the new governor fails to start, switch back to old governor so
that the
devfreq state is not left in some weird limbo.
[Mjungjoo: assume fatal on revert failure and set df->governor to
NULL]
Signed-off-by: Sibi Sankar
On Tue, Mar 12, 2019 at 12:59:34PM -0700, Mike Kravetz wrote:
> On 3/11/19 2:36 AM, Peter Xu wrote:
> >
> > The "kvm" entry is a bit special here only to make sure that existing
> > users like QEMU/KVM won't break by this newly introduced flag. What
> > we need to do is simply set the
801 - 818 of 818 matches
Mail list logo
