Hello Andy
> Btw, is the statement in above email still actual? "...I can fix
> required things."
Yes i will fix your hints tomorrow and send a v6 of my patchset.
Thank you for your hints and time
It would be nice if you could fix ACPI problemmatik.
I would like to see the ACPI dump for
Hello Andy
> Btw, is the statement in above email still actual? "...I can fix
> required things."
Yes i will fix your hints tomorrow and send a v6 of my patchset.
Thank you for your hints and time
It would be nice if you could fix ACPI problemmatik.
I would like to see the ACPI dump for
On Mon, Dec 3, 2018 at 1:13 AM Darren Hart wrote:
> On Fri, Nov 16, 2018 at 05:23:52PM +0100, Lubomir Rintel wrote:
> > It's based off the driver from the OLPC kernel sources. Somewhat
> > modernized and cleaned up, for better or worse.
> >
> > Modified to plug into the olpc-ec driver
On Mon, Dec 3, 2018 at 1:13 AM Darren Hart wrote:
> On Fri, Nov 16, 2018 at 05:23:52PM +0100, Lubomir Rintel wrote:
> > It's based off the driver from the OLPC kernel sources. Somewhat
> > modernized and cleaned up, for better or worse.
> >
> > Modified to plug into the olpc-ec driver
This Makefile is wrong in multiple ways.
The first issue is the breakage of 'linux.bin.ub' target since commit
ece97f3a5fb5 ("microblaze: Fix simpleImage format generation")
because the addition of UIMAGE_{IN,OUT} obviously affected it.
make ARCH=microblaze CROSS_COMPILE=microblaze-linux-
This Makefile is wrong in multiple ways.
The first issue is the breakage of 'linux.bin.ub' target since commit
ece97f3a5fb5 ("microblaze: Fix simpleImage format generation")
because the addition of UIMAGE_{IN,OUT} obviously affected it.
make ARCH=microblaze CROSS_COMPILE=microblaze-linux-
The simpleImage. target generates the following files:
arch/microblaze/boot/simpleImage.
arch/microblaze/boot/simpleImage..ub
arch/microblaze/boot/simpleImage..strip
arch/microblaze/boot/simpleImage..unstrip
However, "make ARCH=microblaze clean" only cleans up the unstrip
image. Fix the
On Fri, 2018-10-19 at 08:30:20 UTC, Daniel Santos wrote:
> jffs2_sync_fs makes the assumption that if CONFIG_JFFS2_FS_WRITEBUFFER
> is defined then a write buffer is available and has been initialized.
> However, this does is not the case when the mtd device has no
> out-of-band buffer:
>
> int
I fixed a race condition in the parallel building of ARM in commit
3939f3345050 ("ARM: 8418/1: add boot image dependencies to not
generate invalid images").
I see the same problem for MicroBlaze too.
"make -j ARCH=microblaze all linux.bin.ub" results in a broken build
since two threads descend
I guess
|| (rm -f $@ && echo false)
... should be
|| (rm -f $@ && false)
since printing the string "false" on the console has no point.
Moreover, no Makefile needs to delete a target on error explicitly
since commit 9c2af1c7377a ("kbuild: add .DELETE_ON_ERROR special
target").
Reuse
To prepare for more fixes, move this to arch/microblaze/Makefile.
Otherwise, the same "... is ready" would be printed multiple times.
(Another solution would be, to remove these messages entirely unless
people persist with them.)
Signed-off-by: Masahiro Yamada
---
arch/microblaze/Makefile
On Sun, 2018-11-18 at 16:36:56 UTC, Colin King wrote:
> From: Colin Ian King
>
> The hunk of code is indented too much by one level, fix this by
> removing the extraneous tabs. Also terminate block comment using
> the recommended coding style to clean up checkpatch warning.
>
> Signed-off-by:
linux.bin, linux.bin.gz, and linux.bin.ub are phony targets to
generate a corresponding image under arch/microblaze/boot/.
simpleImage.% also works like a PHONY target, but a pattern that
contains '%' cannot be a PHONY target. I renamed it to equivalent
simpleImage.$(DTB).
Signed-off-by:
The simpleImage. target generates the following files:
arch/microblaze/boot/simpleImage.
arch/microblaze/boot/simpleImage..ub
arch/microblaze/boot/simpleImage..strip
arch/microblaze/boot/simpleImage..unstrip
However, "make ARCH=microblaze clean" only cleans up the unstrip
image. Fix the
On Fri, 2018-10-19 at 08:30:20 UTC, Daniel Santos wrote:
> jffs2_sync_fs makes the assumption that if CONFIG_JFFS2_FS_WRITEBUFFER
> is defined then a write buffer is available and has been initialized.
> However, this does is not the case when the mtd device has no
> out-of-band buffer:
>
> int
I fixed a race condition in the parallel building of ARM in commit
3939f3345050 ("ARM: 8418/1: add boot image dependencies to not
generate invalid images").
I see the same problem for MicroBlaze too.
"make -j ARCH=microblaze all linux.bin.ub" results in a broken build
since two threads descend
I guess
|| (rm -f $@ && echo false)
... should be
|| (rm -f $@ && false)
since printing the string "false" on the console has no point.
Moreover, no Makefile needs to delete a target on error explicitly
since commit 9c2af1c7377a ("kbuild: add .DELETE_ON_ERROR special
target").
Reuse
To prepare for more fixes, move this to arch/microblaze/Makefile.
Otherwise, the same "... is ready" would be printed multiple times.
(Another solution would be, to remove these messages entirely unless
people persist with them.)
Signed-off-by: Masahiro Yamada
---
arch/microblaze/Makefile
On Sun, 2018-11-18 at 16:36:56 UTC, Colin King wrote:
> From: Colin Ian King
>
> The hunk of code is indented too much by one level, fix this by
> removing the extraneous tabs. Also terminate block comment using
> the recommended coding style to clean up checkpatch warning.
>
> Signed-off-by:
linux.bin, linux.bin.gz, and linux.bin.ub are phony targets to
generate a corresponding image under arch/microblaze/boot/.
simpleImage.% also works like a PHONY target, but a pattern that
contains '%' cannot be a PHONY target. I renamed it to equivalent
simpleImage.$(DTB).
Signed-off-by:
On Thu, 2018-11-29 at 04:19:51 UTC, Huijin Park wrote:
> From: "huijin.park"
>
> Callers of erase_write() always pass an unsigned int.
> So this patch avoids a cast to an int.
>
> Signed-off-by: huijin.park
> Reviewed-by: Miquel Raynal
Applied to http://git.infradead.org/linux-mtd.git
On Wed, 2018-11-28 at 08:02:14 UTC, Huijin Park wrote:
> From: "huijin.park"
>
> The "params->size" is defined as "u64".
> And "info->sector_size" and "info->n_sectors" are defined as
> unsigned int and u16.
> Thus, u64 data might have strange data(loss data) if the result
> overflows an
This patch set fixes various issues in microblaze Makefiles.
BTW, "simpleImage." works like a phony target to generate the
following four images, where the first three are just aliases.
- arch/microblaze/boot/simpleImage.:
identical to arch/microblaze/boot/linux.bin
-
"make ARCH=microblaze help" mentions simpleImage..unstrip,
but it never works because Makefile assumes "system.unstrip" is
the name of DT.
$ make ARCH=microblaze CROSS_COMPILE=microblaze-linux-
simpleImage.system.unstrip
[ snip ]
make[1]: *** No rule to make target
On Sun, 2018-12-02 at 08:33:58 UTC, Yangtao Li wrote:
> DEFINE_SHOW_ATTRIBUTE macro can help us simplify the code,so change
> to it.And change the DEBUGFS_RO_ATTR macro defined in some file to a
> standard macro.
>
> Signed-off-by: Yangtao Li
Applied to http://git.infradead.org/linux-mtd.git
On Thu, 2018-11-29 at 04:19:51 UTC, Huijin Park wrote:
> From: "huijin.park"
>
> Callers of erase_write() always pass an unsigned int.
> So this patch avoids a cast to an int.
>
> Signed-off-by: huijin.park
> Reviewed-by: Miquel Raynal
Applied to http://git.infradead.org/linux-mtd.git
On Wed, 2018-11-28 at 08:02:14 UTC, Huijin Park wrote:
> From: "huijin.park"
>
> The "params->size" is defined as "u64".
> And "info->sector_size" and "info->n_sectors" are defined as
> unsigned int and u16.
> Thus, u64 data might have strange data(loss data) if the result
> overflows an
This patch set fixes various issues in microblaze Makefiles.
BTW, "simpleImage." works like a phony target to generate the
following four images, where the first three are just aliases.
- arch/microblaze/boot/simpleImage.:
identical to arch/microblaze/boot/linux.bin
-
"make ARCH=microblaze help" mentions simpleImage..unstrip,
but it never works because Makefile assumes "system.unstrip" is
the name of DT.
$ make ARCH=microblaze CROSS_COMPILE=microblaze-linux-
simpleImage.system.unstrip
[ snip ]
make[1]: *** No rule to make target
On Sun, 2018-12-02 at 08:33:58 UTC, Yangtao Li wrote:
> DEFINE_SHOW_ATTRIBUTE macro can help us simplify the code,so change
> to it.And change the DEBUGFS_RO_ATTR macro defined in some file to a
> standard macro.
>
> Signed-off-by: Yangtao Li
Applied to http://git.infradead.org/linux-mtd.git
* Linus Torvalds wrote:
> The patch stats this week look a little bit more normal than last tim,
> probably simply because it's also a normal-sized rc4 rather than the
> unusually small rc3.
So there's a new regression in v4.20-rc4, my desktop produces this
lockdep splat:
[ 1772.588771]
* Linus Torvalds wrote:
> The patch stats this week look a little bit more normal than last tim,
> probably simply because it's also a normal-sized rc4 rather than the
> unusually small rc3.
So there's a new regression in v4.20-rc4, my desktop produces this
lockdep splat:
[ 1772.588771]
Thanks, we have run the test for the whole weekend and not reproduce the issue,
so we confirm the CONFIG_RCU_BOOST can fix the issue.
We have enabled the rcupdate.rcu_cpu_stall_timeout=7 and also set panic on rcu
stall and will see if we can see the panic, will keep you posed with the test
Thanks, we have run the test for the whole weekend and not reproduce the issue,
so we confirm the CONFIG_RCU_BOOST can fix the issue.
We have enabled the rcupdate.rcu_cpu_stall_timeout=7 and also set panic on rcu
stall and will see if we can see the panic, will keep you posed with the test
Hi,
On 2018/11/30 17:16, Stephen Boyd wrote:
Quoting Sugaya, Taichi (2018-11-29 04:24:51)
On 2018/11/28 11:01, Stephen Boyd wrote:
Quoting Sugaya Taichi (2018-11-18 17:01:07)
create mode 100644
Documentation/devicetree/bindings/soc/socionext/socionext,m10v.txt
diff --git
Hi,
On 2018/11/30 17:16, Stephen Boyd wrote:
Quoting Sugaya, Taichi (2018-11-29 04:24:51)
On 2018/11/28 11:01, Stephen Boyd wrote:
Quoting Sugaya Taichi (2018-11-18 17:01:07)
create mode 100644
Documentation/devicetree/bindings/soc/socionext/socionext,m10v.txt
diff --git
Hi Dmitry,
On Mon, Dec 3, 2018 at 1:24 AM Dmitry V. Levin wrote:
> On Sun, Dec 02, 2018 at 11:29:10AM +0100, Geert Uytterhoeven wrote:
> > On Tue, Nov 20, 2018 at 1:15 AM Dmitry V. Levin wrote:
> > > syscall_get_arch() is required to be implemented on all architectures
> > > in order to extend
Hi Dmitry,
On Mon, Dec 3, 2018 at 1:24 AM Dmitry V. Levin wrote:
> On Sun, Dec 02, 2018 at 11:29:10AM +0100, Geert Uytterhoeven wrote:
> > On Tue, Nov 20, 2018 at 1:15 AM Dmitry V. Levin wrote:
> > > syscall_get_arch() is required to be implemented on all architectures
> > > in order to extend
Hi all,
Changes since 20181130:
The arm-soc tree gained a conflict against the kbuild tree.
The reset tree gained a conflict against the arm-soc tree.
The clk tree lost its build failure.
The vfs tree gained a conflict against the fscrypt tree.
The net-next tree gained conflicts against the
Hi all,
Changes since 20181130:
The arm-soc tree gained a conflict against the kbuild tree.
The reset tree gained a conflict against the arm-soc tree.
The clk tree lost its build failure.
The vfs tree gained a conflict against the fscrypt tree.
The net-next tree gained conflicts against the
On Mon, Dec 03, 2018 at 12:35:35AM +0100, Vitaly Kuznetsov wrote:
> Nadav Amit writes:
>
> [skip]
>
> >
> > Having said that, something else is sort of strange in the TLFS definitions,
> > I think (I really know little about this whole protocol). Look at the
> > following definitions from
On Mon, Dec 03, 2018 at 12:35:35AM +0100, Vitaly Kuznetsov wrote:
> Nadav Amit writes:
>
> [skip]
>
> >
> > Having said that, something else is sort of strange in the TLFS definitions,
> > I think (I really know little about this whole protocol). Look at the
> > following definitions from
On Mon, Dec 3, 2018 at 1:23 AM Dave Chinner wrote:
>
> On Sat, Dec 01, 2018 at 02:49:09AM -0500, Sasha Levin wrote:
> > On Sat, Dec 01, 2018 at 08:50:05AM +1100, Dave Chinner wrote:
> > >On Fri, Nov 30, 2018 at 05:14:41AM -0500, Sasha Levin wrote:
> > >>On Fri, Nov 30, 2018 at 09:22:03AM +0100,
On Mon, Dec 3, 2018 at 1:23 AM Dave Chinner wrote:
>
> On Sat, Dec 01, 2018 at 02:49:09AM -0500, Sasha Levin wrote:
> > On Sat, Dec 01, 2018 at 08:50:05AM +1100, Dave Chinner wrote:
> > >On Fri, Nov 30, 2018 at 05:14:41AM -0500, Sasha Levin wrote:
> > >>On Fri, Nov 30, 2018 at 09:22:03AM +0100,
On Fri, 30 Nov 2018, Pascal PAILLET-LME wrote:
> The goal of this patch-set is to propose a driver for the STPMIC1 PMIC from
> STMicroelectronics.
> The STPMIC1 regulators supply power to an application processor as well as
> to external system peripherals such as DDR, Flash memories and
On Fri, 30 Nov 2018, Pascal PAILLET-LME wrote:
> The goal of this patch-set is to propose a driver for the STPMIC1 PMIC from
> STMicroelectronics.
> The STPMIC1 regulators supply power to an application processor as well as
> to external system peripherals such as DDR, Flash memories and
Good Day Dear,
I'm Ms Amelia and am new here looking for a serious relationship with someone i
can spend the rest of my life with, someone who is loving, caring, honest and
faithful to spend the rest of my life with, i came across your profile and its
very interesting to me and i would like
Good Day Dear,
I'm Ms Amelia and am new here looking for a serious relationship with someone i
can spend the rest of my life with, someone who is loving, caring, honest and
faithful to spend the rest of my life with, i came across your profile and its
very interesting to me and i would like
On Sat, 01 Dec 2018, Jonathan Cameron wrote:
> On Wed, 28 Nov 2018 09:14:32 +
> Lee Jones wrote:
>
> > On Mon, 19 Nov 2018, Vignesh R wrote:
> >
> > > When performing single ended measurements with TSCADC, its recommended
> > > to set negative input (SEL_INM_SWC_3_0) of ADC step to ADC's
On Sat, 01 Dec 2018, Jonathan Cameron wrote:
> On Wed, 28 Nov 2018 09:14:32 +
> Lee Jones wrote:
>
> > On Mon, 19 Nov 2018, Vignesh R wrote:
> >
> > > When performing single ended measurements with TSCADC, its recommended
> > > to set negative input (SEL_INM_SWC_3_0) of ADC step to ADC's
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc_le perf)
failed like this:
bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory
#include
^~
Caused by patches
"mm: replace all open encodings for NUMA_NO_NODE"
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc_le perf)
failed like this:
bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory
#include
^~
Caused by patches
"mm: replace all open encodings for NUMA_NO_NODE"
On 30-11-18, 09:53, Ulf Hansson wrote:
> On Mon, 26 Nov 2018 at 09:10, Viresh Kumar wrote:
> >
> > We will need these going forward in hotpath, i.e. from within
> > dev_pm_genpd_set_performance_state().
>
> Well, as for patch2, please try to be a bit more descriptive of why
> and what this patch
On 30-11-18, 09:53, Ulf Hansson wrote:
> On Mon, 26 Nov 2018 at 09:10, Viresh Kumar wrote:
> >
> > We will need these going forward in hotpath, i.e. from within
> > dev_pm_genpd_set_performance_state().
>
> Well, as for patch2, please try to be a bit more descriptive of why
> and what this patch
On Sun, Dec 02, 2018 at 08:21:30PM +, Tigran Aivazian wrote:
> On Sun, 2 Dec 2018 at 20:13, Greg KH wrote:
> > What is the git commit id of this patch in Linus's tree?
>
> In linux-next the commit id is
> d2e6681167c634cfc3558991b59a6f614a31d226 , but it is not in Linus'
> tree (i.e. at
On Sun, Dec 02, 2018 at 08:21:30PM +, Tigran Aivazian wrote:
> On Sun, 2 Dec 2018 at 20:13, Greg KH wrote:
> > What is the git commit id of this patch in Linus's tree?
>
> In linux-next the commit id is
> d2e6681167c634cfc3558991b59a6f614a31d226 , but it is not in Linus'
> tree (i.e. at
Add missing definition for HID_DG_WHITEBOARD then replace the hid
usage hex with macros for better readibility.
Signed-off-by: Chris Chiu
---
include/linux/hid.h | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/include/linux/hid.h b/include/linux/hid.h
index
The ASUS laptops start to support the airplane mode radio management
to replace the original mechanism of airplane mode toggle hotkey.
On the ASUS P5440FF, it presents as a HID device connecting via
I2C, named i2c-AMPD0001. When pressing it, the Embedded Controller
send hid report via I2C and
Add missing definition for HID_DG_WHITEBOARD then replace the hid
usage hex with macros for better readibility.
Signed-off-by: Chris Chiu
---
include/linux/hid.h | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/include/linux/hid.h b/include/linux/hid.h
index
The ASUS laptops start to support the airplane mode radio management
to replace the original mechanism of airplane mode toggle hotkey.
On the ASUS P5440FF, it presents as a HID device connecting via
I2C, named i2c-AMPD0001. When pressing it, the Embedded Controller
send hid report via I2C and
On Wed, Nov 28, 2018 at 1:36 PM Wen Yang wrote:
>
> dma_pool_destroy(NULL) is safe, so removes NULL check before freeing
> the mem. This patch also fix the ifnullfree.cocci warnings.
>
> Signed-off-by: Wen Yang
Acked-by: Sumit Saxena
> CC: Julia Lawall
> CC: Kashyap Desai
> CC: Sumit Saxena
On Wed, Nov 28, 2018 at 1:36 PM Wen Yang wrote:
>
> dma_pool_destroy(NULL) is safe, so removes NULL check before freeing
> the mem. This patch also fix the ifnullfree.cocci warnings.
>
> Signed-off-by: Wen Yang
Acked-by: Sumit Saxena
> CC: Julia Lawall
> CC: Kashyap Desai
> CC: Sumit Saxena
On 30-11-18, 09:45, Ulf Hansson wrote:
> On Mon, 26 Nov 2018 at 09:10, Viresh Kumar wrote:
> >
> > Introduce a new helper dev_pm_opp_xlate_performance_state() which will
> > be used to translate from pstate of a device to another one.
>
> I don't get this, could you please elaborate?
>
> >
> >
On 30-11-18, 09:45, Ulf Hansson wrote:
> On Mon, 26 Nov 2018 at 09:10, Viresh Kumar wrote:
> >
> > Introduce a new helper dev_pm_opp_xlate_performance_state() which will
> > be used to translate from pstate of a device to another one.
>
> I don't get this, could you please elaborate?
>
> >
> >
On 2018-11-30 07:10, Prateek Sood wrote:
In a scenario where cpu_hotplug_lock percpu_rw_semaphore is already
acquired for read operation by P1 using percpu_down_read().
Now we have P1 in the path of releaseing the cpu_hotplug_lock and P2
is in the process of acquiring cpu_hotplug_lock.
P1
On 2018-11-30 07:10, Prateek Sood wrote:
In a scenario where cpu_hotplug_lock percpu_rw_semaphore is already
acquired for read operation by P1 using percpu_down_read().
Now we have P1 in the path of releaseing the cpu_hotplug_lock and P2
is in the process of acquiring cpu_hotplug_lock.
P1
Current mailbox driver of Hi3660 release the mailbox directly
before sending a new message which may cause last message lost
and next message sending doesn't take effect actually.
This patch fixes this issue by following the right process below,
each time before sending a message, mailbox driver
Current mailbox driver of Hi3660 release the mailbox directly
before sending a new message which may cause last message lost
and next message sending doesn't take effect actually.
This patch fixes this issue by following the right process below,
each time before sending a message, mailbox driver
A missing of_node_put() and a small cleanup.
Please pull, thanks!
The following changes since commit 2595646791c319cadfdbf271563aac97d0843dc7:
Linux 4.20-rc5 (2018-12-02 15:07:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide.git
A missing of_node_put() and a small cleanup.
Please pull, thanks!
The following changes since commit 2595646791c319cadfdbf271563aac97d0843dc7:
Linux 4.20-rc5 (2018-12-02 15:07:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide.git
On Mon, Dec 03, 2018 at 09:51:45AM +0530, Souptick Joarder wrote:
> Hi Mike,
>
> On Sun, Dec 2, 2018 at 4:43 PM Mike Rapoport wrote:
> >
> > On Sun, Dec 02, 2018 at 11:49:44AM +0530, Souptick Joarder wrote:
> > > Previouly drivers have their own way of mapping range of
> > > kernel pages/memory
On Mon, Dec 03, 2018 at 09:51:45AM +0530, Souptick Joarder wrote:
> Hi Mike,
>
> On Sun, Dec 2, 2018 at 4:43 PM Mike Rapoport wrote:
> >
> > On Sun, Dec 02, 2018 at 11:49:44AM +0530, Souptick Joarder wrote:
> > > Previouly drivers have their own way of mapping range of
> > > kernel pages/memory
Hi Steve,
Please pull this patch.
Thanks.
On 11/15/18 6:13 PM, Oleg Nesterov wrote:
> On 11/15, Ravi Bangoria wrote:
>>
>> There could be a race between task exit and probe unregister:
>>
>> exit_mm()
>> mmput()
>> __mmput() uprobe_unregister()
>>
This patch fixes a possible null pointer dereference in
dlfb_usb_probe, detected by the semantic patch deref_null.cocci,
with the following warning:
drivers/video/fbdev/udlfb.c:1704:11-15: ERROR: dlfb is NULL but dereferenced.
The following code has potential null pointer references:
1597
Hi Steve,
Please pull this patch.
Thanks.
On 11/15/18 6:13 PM, Oleg Nesterov wrote:
> On 11/15, Ravi Bangoria wrote:
>>
>> There could be a race between task exit and probe unregister:
>>
>> exit_mm()
>> mmput()
>> __mmput() uprobe_unregister()
>>
This patch fixes a possible null pointer dereference in
dlfb_usb_probe, detected by the semantic patch deref_null.cocci,
with the following warning:
drivers/video/fbdev/udlfb.c:1704:11-15: ERROR: dlfb is NULL but dereferenced.
The following code has potential null pointer references:
1597
On Fri, Nov 30, 2018 at 03:47:45PM -0800, Roman Gushchin wrote:
> Describe cgroup v2 freezer interface in the cgroup v2 admin guide.
>
> Signed-off-by: Roman Gushchin
> Cc: Tejun Heo
> Cc: linux-...@vger.kernel.org
> Cc: kernel-t...@fb.com
Reviewed-by: Mike Rapoport
> ---
>
On Fri, Nov 30, 2018 at 03:47:45PM -0800, Roman Gushchin wrote:
> Describe cgroup v2 freezer interface in the cgroup v2 admin guide.
>
> Signed-off-by: Roman Gushchin
> Cc: Tejun Heo
> Cc: linux-...@vger.kernel.org
> Cc: kernel-t...@fb.com
Reviewed-by: Mike Rapoport
> ---
>
Update the dt-binding document to support new compatible string for the
GPIO interrupt controller which found in Amlogic's Meson-G12A SoC.
Signed-off-by: Xingyu Chen
Signed-off-by: Jianxin Pan
---
.../bindings/interrupt-controller/amlogic,meson-gpio-intc.txt| 1 +
1 file changed, 1
The Meson-G12A SoC uses the same GPIO interrupt controller IP block as the
other Meson SoCs, A totle of 100 pins can be spied on, which is the sum of:
- 223:100 undefined (no interrupt)
- 99:97 3 pins on bank GPIOE
- 96:77 20 pins on bank GPIOX
- 76:61 16 pins on bank GPIOA
- 60:53 8 pins
Update the dt-binding document to support new compatible string for the
GPIO interrupt controller which found in Amlogic's Meson-G12A SoC.
Signed-off-by: Xingyu Chen
Signed-off-by: Jianxin Pan
---
.../bindings/interrupt-controller/amlogic,meson-gpio-intc.txt| 1 +
1 file changed, 1
The Meson-G12A SoC uses the same GPIO interrupt controller IP block as the
other Meson SoCs, A totle of 100 pins can be spied on, which is the sum of:
- 223:100 undefined (no interrupt)
- 99:97 3 pins on bank GPIOE
- 96:77 20 pins on bank GPIOX
- 76:61 16 pins on bank GPIOA
- 60:53 8 pins
This series try to add GPIO interrupt controller support for Meson-G12A SoCs.
Although the total number of pins is the same as the Meson-AXG SoC, the gpio
banks and irq numbers are different. To avoid confusion on use, i think the
new compatible string is needed.
Xingyu Chen (2):
dt-bindings:
This series try to add GPIO interrupt controller support for Meson-G12A SoCs.
Although the total number of pins is the same as the Meson-AXG SoC, the gpio
banks and irq numbers are different. To avoid confusion on use, i think the
new compatible string is needed.
Xingyu Chen (2):
dt-bindings:
On (12/03/18 15:02), Sergey Senozhatsky wrote:
> Seems like I misread writeback_limit_store() a bit.
>
> So, if I want to, say, let only 10M of writteback pages, I need to
> do
>
> echo 0 > writeback_limit
> echo 10M > writeback_limit_store// memparse format is for
>
On (12/03/18 15:02), Sergey Senozhatsky wrote:
> Seems like I misread writeback_limit_store() a bit.
>
> So, if I want to, say, let only 10M of writteback pages, I need to
> do
>
> echo 0 > writeback_limit
> echo 10M > writeback_limit_store// memparse format is for
>
From: Joris Gutjahr
Date: Sun, 28 Oct 2018 17:45:46 +0100
> I fixed this coding style error I got after running
> checkpatch --file on this file.
> The problem was that the whole case block was on one line.
>
> Signed-off-by: Joris Gutjahr
Frankly I think the existing code is more compact and
From: Joris Gutjahr
Date: Sun, 28 Oct 2018 17:45:46 +0100
> I fixed this coding style error I got after running
> checkpatch --file on this file.
> The problem was that the whole case block was on one line.
>
> Signed-off-by: Joris Gutjahr
Frankly I think the existing code is more compact and
On (12/03/18 14:50), Sergey Senozhatsky wrote:
> On (12/03/18 11:40), Minchan Kim wrote:
> [..]
> > + down_read(>init_lock);
> > + atomic64_set(>stats.bd_wb_limit, val);
> > + if (val == 0)
> > + zram->stop_writeback = false;
> > + up_read(>init_lock);
>
> [..]
>
> > +
On (12/03/18 14:50), Sergey Senozhatsky wrote:
> On (12/03/18 11:40), Minchan Kim wrote:
> [..]
> > + down_read(>init_lock);
> > + atomic64_set(>stats.bd_wb_limit, val);
> > + if (val == 0)
> > + zram->stop_writeback = false;
> > + up_read(>init_lock);
>
> [..]
>
> > +
> -Original Message-
> From: Thomas Meyer
> Sent: Monday, December 3, 2018 2:22 AM
> To: Dept-Eng QLogic Storage Upstream upstr...@cavium.com>; j...@linux.vnet.ibm.com;
> martin.peter...@oracle.com; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: [PATCH] scsi:
> -Original Message-
> From: Thomas Meyer
> Sent: Monday, December 3, 2018 2:22 AM
> To: Dept-Eng QLogic Storage Upstream upstr...@cavium.com>; j...@linux.vnet.ibm.com;
> martin.peter...@oracle.com; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: [PATCH] scsi:
Convert warnings to info as not all platforms may
have all the thresholds and sensors enabled.
Signed-off-by: Wei Ni
---
drivers/thermal/tegra/soctherm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/thermal/tegra/soctherm.c b/drivers/thermal/tegra/soctherm.c
I210 ethernet card doesn't wakeup when a cable gets plugged. It's
because its PME is not set.
Since commit 42eca2302146 ("PCI: Don't touch card regs after runtime
suspend D3"), if the PCI state is saved, pci_pm_runtime_suspend() stops
calling pci_finish_runtime_suspend(), which enables the PCI
Since different platforms may not support all 4
sensors, so the sensor registration may be failed.
Add codes to parse dt to find sensor id which
need to be registered. So that the registration
can be successful on all platform.
Signed-off-by: Wei Ni
---
drivers/thermal/tegra/soctherm.c | 45
Fix memory allocation to store the pointers to
thermal_zone_device.
Signed-off-by: Wei Ni
Acked-by: Thierry Reding
---
drivers/thermal/tegra/soctherm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/tegra/soctherm.c b/drivers/thermal/tegra/soctherm.c
index
This series fixed some issues for Tegra soctherm
Main changes from v4:
1. fixed for the parsing sensor id.
2. keep warning for missing critical trips.
Main changes from v3:
1. updated codes for parsing sensor id, per Thierry's comments
Main changes from v2:
1. add codes to parse sensor id to
Convert warnings to info as not all platforms may
have all the thresholds and sensors enabled.
Signed-off-by: Wei Ni
---
drivers/thermal/tegra/soctherm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/thermal/tegra/soctherm.c b/drivers/thermal/tegra/soctherm.c
I210 ethernet card doesn't wakeup when a cable gets plugged. It's
because its PME is not set.
Since commit 42eca2302146 ("PCI: Don't touch card regs after runtime
suspend D3"), if the PCI state is saved, pci_pm_runtime_suspend() stops
calling pci_finish_runtime_suspend(), which enables the PCI
Since different platforms may not support all 4
sensors, so the sensor registration may be failed.
Add codes to parse dt to find sensor id which
need to be registered. So that the registration
can be successful on all platform.
Signed-off-by: Wei Ni
---
drivers/thermal/tegra/soctherm.c | 45
1 - 100 of 614 matches
Mail list logo
