On Thu, Jul 20, 2017 at 02:31:09PM +0530, Arvind Yadav wrote:
> > "Constify attribute_group structs because they don't change at runtime."
> I can add this as subject. But we should avoid lengthy subject.
Are you actually reading what I'm writing to you? I said this should be
the commit message, n
Commit-ID: d689c64d189e43d782fec5649fb0afe303c5b3f9
Gitweb: http://git.kernel.org/tip/d689c64d189e43d782fec5649fb0afe303c5b3f9
Author: Arnd Bergmann
AuthorDate: Wed, 19 Jul 2017 14:53:05 +0200
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 10:46:24 +0200
x86/platform: Add PCI depe
Commit-ID: 693bf0aa01b7f9a1b24b2b932d555c6667f17a1a
Gitweb: http://git.kernel.org/tip/693bf0aa01b7f9a1b24b2b932d555c6667f17a1a
Author: Ingo Molnar
AuthorDate: Thu, 20 Jul 2017 11:23:07 +0200
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 11:37:58 +0200
x86/boot: Fix memremap() rel
Commit-ID: 7206f9bf108eb9513d170c73f151367a1bdf3dbf
Gitweb: http://git.kernel.org/tip/7206f9bf108eb9513d170c73f151367a1bdf3dbf
Author: Arnd Bergmann
AuthorDate: Wed, 19 Jul 2017 14:53:02 +0200
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 10:46:24 +0200
x86/io: Add "memory" clobb
On Tue, 2017-07-18 at 12:57 -0700, Mark Salyzyn wrote:
> On 07/18/2017 10:50 AM, Joe Perches wrote:
> > On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote:
> > > Recently I have noticed too many users of struct rtc_time that
> > > printing
> > > its content field by field.
> > >
> > > In thi
Hit the kmemleak when executing instance_rmdir, it forgot releasing
mem of tracing_cpumask. With this fix, the warn does not appear any
more.
unreferenced object 0x93a8dfaa7c18 (size 8):
comm "mkdir", pid 1436, jiffies 4294763622 (age 9134.308s)
hex dump (first 8 bytes):
ff ff ff ff ff
On 20/07/17 09:06, Pavel Machek wrote:
Hi!
--- a/drivers/video/backlight/pwm_bl.c
+++ b/drivers/video/backlight/pwm_bl.c
@@ -10,6 +10,7 @@
* published by the Free Software Foundation.
*/
+#include
#include
#include
#include
@@ -35,6 +36,7 @@ struct pwm_bl_data {
struct g
On Thu, Jul 20, 2017 at 11:53:39AM +0200, Maxime Ripard wrote:
> Hi Daniel,
>
> On Tue, Jul 18, 2017 at 09:35:03AM +0200, Daniel Vetter wrote:
> > On Tue, Jul 18, 2017 at 9:07 AM, Maxime Ripard
> > wrote:
> > > On Mon, Jul 17, 2017 at 02:57:19PM +0800, Chen-Yu Tsai wrote:
> > >> On Mon, Jul 17, 2
On Thu, Jul 20, 2017 at 10:17 AM, gregkh wrote:
> On Thu, Jul 20, 2017 at 09:24:21AM +0200, Arnd Bergmann wrote:
>> On Wed, Jul 19, 2017 at 11:50 PM, wrote:
>> > --
>> > From: Arnd Bergmann
>> > Subject: kbuild: disable -Wformat-truncation war
On Thu, 20 Jul 2017 12:02:10 +0200,
Masaki Ota wrote:
>
> Hi,
>
> Some user reported that this issue happened from kernel 4.10.7.
> Because the below patch was applied on it.
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=0186e6a4e501d39f5f90dd7e5887bc668aef
Hugh Dickins wrote:
> You probably won't welcome getting into alternatives at this late stage;
> but after hacking around it one way or another because of its pointless
> lockups, I lost patience with that too_many_isolated() loop a few months
> back (on realizing the enormous number of pages that
Remove unbalanced RPM put at driver unbind which resulted in a negative
usage count.
Fixes: 19891b20e7c2 ("pwm: pwm-tiehrpwm: PWM driver support for EHRPWM")
Signed-off-by: Johan Hovold
---
drivers/pwm/pwm-tiehrpwm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/pwm/pwm-tiehrpwm.c b
Make sure to unprepare the clock before returning on late probe errors.
Fixes: b388f15fd14c ("pwm: pwm-tiehrpwm: Use clk_enable/disable instead
clk_prepare/unprepare.")
Signed-off-by: Johan Hovold
---
drivers/pwm/pwm-tiehrpwm.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff -
Quoting Tvrtko Ursulin (2017-07-20 11:09:53)
>
> On 19/07/2017 23:35, Christophe JAILLET wrote:
> > Goto the right label in case of error, otherwise there is a leak.
> > This has been introduced by c5cf9a9147ff. In this patch a goto has not been
> > updated.
> >
> > Fixes: c5cf9a9147ff ("drm/i915
Currently we are calling usb_submit_urb directly to submit deferred tx
urbs after unanchor them.
So the usb_giveback_urb_bh would failed to unref it in usb_unanchor_urb
and cause memory leak:
unreferenced object 0xffc0ce0fa400 (size 256):
...
backtrace:
[] __save_stack_trace+0x48/0x6c
Joe Perches writes:
> On Wed, 2017-07-19 at 21:24 -0700, Linus Torvalds wrote:
>> On Wed, Jul 19, 2017 at 6:05 PM, Joe Perches wrote:
>> >
>> > Just for ease of manipulation and not breaking the script much,
>> > I'd suggest just having a MAINTAINERS directory and stuffing
>> > each of the sect
On 07/20/2017 05:02 AM, Sean Wang wrote:
Hi, Matthias
just a gentle ping on this
pushed now to v4.13-next/dts64
Thanks!
Sean
On Sat, 2017-06-17 at 01:06 +0800, sean.w...@mediatek.com wrote:
From: Sean Wang
Changes since v4:
- redefine the two dummy clocks with the correct fr
Hi Oliver,
On 07/20/2017 05:11 PM, Oliver Neukum wrote:
>+ if (err < 0) {
>+ if (err != -EPERM && err != -ENODEV)
>+ BT_ERR("%s urb %p submission failed (%d)",
>+ data->hdev->name, urb, -err);
>+
Fix mishaps in error format strings.
Signed-off-by: Bogdan Purcareata
---
drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
b/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
index
Once a Tx frame descriptor is enqueued, an interrupt might be triggered
to process the Tx confirmation and free the skb, hitting a memory use
after free when updating the tx_bytes statistic based on skb->len.
Use the frame descriptor length instead.
Signed-off-by: Bogdan Purcareata
---
drivers/
Declare rf69_set_dc_cut_off_frequency_intern as static since it
is used internaly only
Fixes: 874bcba65f9a ("staging: pi433: New driver")
Signed-off-by: Marcus Wolf
diff --git a/drivers/staging/pi433/rf69.c b/drivers/staging/pi433/rf69.c
--- a/drivers/staging/pi433/rf69.c
+++ b/drivers/staging/p
On 07/20/2017 05:07 AM, Sean Wang wrote:
Hi, Matthias
just a gentle ping on this
Pushed now to v4.13-next/dts32
Thanks!
Sean
On Wed, 2017-06-21 at 15:49 +0800, sean.w...@mediatek.com wrote:
From: Sean Wang
Fixed binding violation and also updated related binding documentatio
Hi,
On Thursday 20 July 2017 04:01 PM, Borislav Petkov wrote:
On Thu, Jul 20, 2017 at 02:31:09PM +0530, Arvind Yadav wrote:
"Constify attribute_group structs because they don't change at runtime."
I can add this as subject. But we should avoid lengthy subject.
Are you actually reading what I
Reviewed-by: Marcus Wolf
Tested-by: Marcus Wolf
Am Di, 18.07.2017, 15:04 schrieb Colin King:
> From: Colin Ian King
>
> The check for thread_run failure is incorrect, use IS_ERR instead.
>
> Cleans up sparse error message:
> "error: incompatible types for operation (<)"
>
> Fixes: 874bcba65f9a
On (07/20/17 12:28), H??kon Bugge wrote:
> cp->cp_send_gen is treated as a normal variable, although it may be
> used by different threads.
I'm confused by that assertion. If you look at the comments right
above the change in your patch, there is a note that
acquire_in_xmit/release_in_xmit are th
Reviewed-by: Marcus Wolf
Am Di, 18.07.2017, 15:03 schrieb Colin King:
> From: Colin Ian King
>
> The functions pi433_receive and pi433_tx_thread are local to the source
> and do not need to be in global scope, so make them static
>
> Cleans up sparse warnings:
> symbol 'pi433_receive' was not de
Hi,
While booting v4.13-rc1 on an arm64 system, I noticed some messages
that clutter the boot log without providing any useful
information. This series trims some of the obvious offenders.
The patches are spread across a few sub-systems - arm64/mm, mailbox,
APEI and xen, and can be independently
Reviewed-by: Marcus Wolf
Am Di, 18.07.2017, 15:03 schrieb Colin King:
> From: Colin Ian King
>
> The function rf69_set_bandwidth_intern is local to the source
> and do not need to be in global scope, so make it static. Also
> break overly wide line.
>
> Cleans up sparse warning:
> symbol 'update
When booting linux on a system without CONFIG_NUMA enabled, the
following messages are printed during boot -
NUMA: Faking a node at [mem 0x-0x0083]
NUMA: Adding memblock [0x80 - 0x8000e7] on node 0
NUMA: Adding memblock [0x8000e8 - 0x83f65c] on node
Reviewed-by: Marcus Wolf
Am So, 16.07.2017, 16:48 schrieb Joseph Wright:
> Declare functions static to fix sparse warnings:
>
> warning: symbol 'pi433_receive' was not declared. Should it be static?
> warning: symbol 'pi433_tx_thread' was not declared. Should it be static?
>
> Signed-off-by: Jose
When booting an ACPI enabled system that does not provide the hardware
error source table (HEST), the ghes driver prints the following message
in the kernel log -
[3.460067] GHES: HEST is not enabled!
which is not helpful.
The message is also output when HEST is explicitly disabled using ker
When booting on an ACPI enabled system that does not provide the
Platform Communications Channel Table (PCCT), the pcc mailbox driver
prints -
[0.484261] PCCT header not found.
during probe before returning -ENODEV.
This message clutters the bootlog and doesn't provide any useful
information
Reviewed-by: Marcus Wolf
Tested-by: Marcus Wolf
Am So, 16.07.2017, 16:48 schrieb Joseph Wright:
> Error should be checked with IS_ERR after calling kthread_run()
> instead of comparing the returned pointer to an int.
>
> Found by sparse warning:
>
> incompatible types for operation (<)
> lef
On Thu 2017-07-20 11:37:17, Daniel Thompson wrote:
> On 20/07/17 09:06, Pavel Machek wrote:
> >Hi!
> >
> >>>--- a/drivers/video/backlight/pwm_bl.c
> >>>+++ b/drivers/video/backlight/pwm_bl.c
> >>>@@ -10,6 +10,7 @@
> >>> * published by the Free Software Foundation.
> >>> */
> >>>+#include
> >>>
On systems that are not booted as a Xen domain, the xenfs driver prints
the following message during boot.
[3.460595] xenfs: not registering filesystem on non-xen platform
As the user chose not to boot a Xen domain, this message does not
provide useful information. Drop this message.
Signed-
When enabling lockdep debugging on Juno platform with HDLCD and TDA998x
I get the following warning from the system:
[ 25.990733] ==
[ 25.998637] WARNING: possible circular locking dependency detected
[ 26.006531] 4.13.0-rc1-00284-g28c0a682
Reviewed-by: Marcus Wolf
Am Do, 20.07.2017, 01:58 schrieb Randy Dunlap:
> From: Randy Dunlap
>
> The pi433 driver uses SPI interfaces so it should depend on SPI.
> Also, the "default n" can be removed since that is already the
> default.
>
> Fixes these build errors when SPI is not enabled:
>
>
On Thu, Jul 20, 2017 at 2:40 PM, Will Deacon wrote:
> On Thu, Jul 20, 2017 at 09:32:00AM +0530, Anup Patel wrote:
>> On Wed, Jul 19, 2017 at 5:23 PM, Will Deacon wrote:
>> > There are two things here:
>> >
>> > 1. iommu_present() is pretty useless, because it applies to a "bus" which
>> >
Reviewed-by: Marcus Wolf
> Colin King hat am 18. Juli 2017 um 07:40
> geschrieben:
>
>
> From: Colin Ian King
>
> Trivial fix to spelling mistakes in dev_dbg debug messages
>
> "wiat" -> "wait"
> "fonud" -> "found"
>
> Signed-off-by: Colin Ian King
> ---
> drivers/staging/pi433/pi433_if.c | 4
Logan Gunthorpe writes:
> On 18/07/17 11:57 PM, Michael Ellerman wrote:
>> Seems fair enough, have you tested it at all?
>
> It's only been compile tested and the kbuild robot has beat up on it a bit.
OK. I don't think I see any way it can break anything, so feel free to
merge it, it'll get boot
Em Wed, 19 Jul 2017 11:02:01 -0500
Rob Herring escreveu:
> On Wed, Jul 19, 2017 at 4:41 AM, Sylwester Nawrocki
> wrote:
> > On 07/18/2017 11:43 PM, Rob Herring wrote:
> >> Now that we have a custom printf format specifier, convert users of
> >> full_name to use %pOF instead. This is preparatio
On Thu, Jul 20, 2017 at 04:38:09PM +0530, Anup Patel wrote:
> On Thu, Jul 20, 2017 at 2:40 PM, Will Deacon wrote:
> > On Thu, Jul 20, 2017 at 09:32:00AM +0530, Anup Patel wrote:
> >> On Wed, Jul 19, 2017 at 5:23 PM, Will Deacon wrote:
> >> > There are two things here:
> >> >
> >> > 1. iommu_pre
On 20/07/17 10:10, Will Deacon wrote:
> On Thu, Jul 20, 2017 at 09:32:00AM +0530, Anup Patel wrote:
>> On Wed, Jul 19, 2017 at 5:23 PM, Will Deacon wrote:
>>> There are two things here:
>>>
>>> 1. iommu_present() is pretty useless, because it applies to a "bus" which
>>> doesn't actually te
This patchset primarily adds Broadcom FlexRM reset module for
VFIO platform driver.
The patches are based on Linux-4.13-rc1 and can also be
found at flexrm-vfio-v3 branch of
https://github.com/Broadcom/arm64-linux.git
Changes since v2:
- Remove PATCH1 because fixing VFIO no-IOMMU mode is
a se
This patch adds Broadcom FlexRM low-level reset for
VFIO platform.
It will do the following:
1. Disable/Deactivate each FlexRM ring
2. Flush each FlexRM ring
The cleanup sequence for FlexRM rings is adapted from
Broadcom FlexRM mailbox driver.
Signed-off-by: Anup Patel
Reviewed-by: Oza Oza
Rev
On Thu, Jul 20, 2017 at 10:58:37AM +, Bogdan Purcareata wrote:
> Once a Tx frame descriptor is enqueued, an interrupt might be triggered
> to process the Tx confirmation and free the skb, hitting a memory use
> after free when updating the tx_bytes statistic based on skb->len.
>
> Use the fram
On Thu, Jul 20, 2017 at 12:04:01PM +0100, Punit Agrawal wrote:
> When booting an ACPI enabled system that does not provide the hardware
> error source table (HEST), the ghes driver prints the following message
> in the kernel log -
>
> [3.460067] GHES: HEST is not enabled!
>
> which is not he
On Thu, Jul 20, 2017 at 04:47:31PM +0800, Jisheng Zhang wrote:
> I notice there's one regulator driver for NCP6335D in android-msm repo:
> https://android.googlesource.com/kernel/msm/+log/android-msm-dory-3.10-kitkat-wear/drivers/regulator/onsemi-ncp6335d.c
> Is there anyone want to make it main
On Tue, Jul 18, 2017 at 10:43 PM, Rob Herring wrote:
> Now that we have a custom printf format specifier, convert users of
> full_name to use %pOF instead. This is preparation to remove storing
> of the full path string for each node.
>
> Signed-off-by: Rob Herring
> Cc: Kyungmin Park
> Cc: Andr
Hi Greg,
below you can see the report with the error on m68k. It was sent to me from a
test robot of intel.
According to my research, this problem occured, because there is no hardware
support for floating point on the m68k (or it was configured not to use it).
Therefore gcc uses an internal func
> On 20 Jul 2017, at 13:02, Sowmini Varadhan
> wrote:
>
> On (07/20/17 12:28), H??kon Bugge wrote:
>> cp->cp_send_gen is treated as a normal variable, although it may be
>> used by different threads.
>
> I'm confused by that assertion. If you look at the comments right
> above the change in yo
On Mon, Feb 02, 2015 at 11:13:44AM -0800, Linus Torvalds wrote:
> On Mon, Feb 2, 2015 at 11:00 AM, Linus Torvalds
> wrote:
> >
> > (I'm also not entirely sure what uses int_sqrt() that ends up being so
> > performance-critical, so it would be good to document that too, since
> > that probably also
On 19/07/17 13:51, Stanimir Varbanov wrote:
> In venus_boot(), we pass a pointer to a phys_addr_t
> into dmam_alloc_coherent, which the compiler warns about:
>
> platform/qcom/venus/firmware.c: In function 'venus_boot':
> platform/qcom/venus/firmware.c:63:49: error: passing argument 3 of
> 'dmam_
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by and 'uncore.h'
work with const attribute_group. So mark the non-const structs as const.
Arvind Yadav (7):
[PATCH v2 1/7] perf: x86: intel: uncore: constify attribute_group structures.
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by 'uncore.h' work with const
attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
change in v2:
Remove before/after size comparison from com
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
change in v2:
Remove before/after size comparison from commit messag
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
change in v2:
Remove before/after size comparison from commit messag
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
change in v2:
Remove before/after size comparison from commit messag
On Thu, Jul 20, 2017 at 01:23:05PM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> below you can see the report with the error on m68k. It was sent to me from a
> test robot of intel.
>
> According to my research, this problem occured, because there is no hardware
> support for floating point on the m68
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by 'uncore.h' work with const
attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
change in v2:
Remove before/after size comparison from com
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by 'uncore.h' work with const
attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
change in v2:
Remove before/after size comparison from com
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by 'uncore.h' work with const
attribute_group. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
change in v2:
Remove before/after size comparison from com
Push the request_irq function to the end of probe so as
to ensure all the required fields are populated in the event
of an ISR getting executed right after requesting the irq.
Currently while loading the crash kernel a crash was seen as
soon as devm_request_threaded_irq was called. This was due to
On Thu, Jul 20, 2017 at 01:23:05PM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> below you can see the report with the error on m68k. It was sent to me from a
> test robot of intel.
>
> According to my research, this problem occured, because there is no hardware
> support for floating point on the m
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Thursday, July 20, 2017 2:18 PM
> To: Bogdan Purcareata
> Cc: Ruxandra Ioana Radulescu ;
> gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@driverdev.osuosl.org
> Subject: Re: [PATCH 1/2]
On Thu, Jul 20, 2017 at 12:04:50PM +0100, Liviu Dudau wrote:
> When enabling lockdep debugging on Juno platform with HDLCD and TDA998x
> I get the following warning from the system:
>
> [ 25.990733] ==
> [ 25.998637] WARNING: possible circula
On 20.07.2017 08:40, shuw...@redhat.com wrote:
From: Shu Wang
Found this issue by kmemleak.
xhci_run() did not check return val and free command for
xhci_queue_vendor_command()
unreferenced object 0x88011c0be500 (size 64):
comm "kworker/0:1", pid 58, jiffies 4294670908 (age 50.420s)
Ah. Good. My mistake.
regards,
dan carpenter
On Thu, Jul 20, 2017 at 12:38:53PM +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 20, 2017 at 12:04:50PM +0100, Liviu Dudau wrote:
> > When enabling lockdep debugging on Juno platform with HDLCD and TDA998x
> > I get the following warning from the system:
> >
> > [ 25.990733] =
Commit-ID: 325cdacd03c12629aa5f9ee2ace49b1f3dc184a8
Gitweb: http://git.kernel.org/tip/325cdacd03c12629aa5f9ee2ace49b1f3dc184a8
Author: Josh Poimboeuf
AuthorDate: Sat, 15 Jul 2017 00:10:58 -0500
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 12:31:04 +0200
debug: Fix WARN_ON_ONCE()
On Thu, Jul 20, 2017 at 1:26 PM, Hans Verkuil wrote:
> On 19/07/17 13:51, Stanimir Varbanov wrote:
>> In venus_boot(), we pass a pointer to a phys_addr_t
>> into dmam_alloc_coherent, which the compiler warns about:
>>
>> platform/qcom/venus/firmware.c: In function 'venus_boot':
>> platform/qcom/ve
* Andrew Banman wrote:
> The BAU confers no benefit to a UV system running with only one hub/socket.
> Permanently disable the BAU driver if there are less than two hubs online
> to avoid BAU overhead. We have observed failed boots on single-socket UV4
> systems caused by BAU that are avoided wi
Hi Gabriel,
On 07/20/2017 11:31 AM, Gabriel FERNANDEZ wrote:
> Hi Vladimir,
>
>
> On 07/19/2017 11:20 PM, Vladimir Zapolskiy wrote:
>> Hello Gabriel,
>>
>> On 07/19/2017 05:25 PM, gabriel.fernan...@st.com wrote:
>>> From: Gabriel Fernandez
>>>
>>> This patch enables clocks for STM32H743 boards.
On Thu, 2017-07-20 at 13:24 +0200, Peter Zijlstra wrote:
[]
> + m = 1UL << ((fls(x) + 1) & ~1UL);
maybe
#if BITS_PER_LONG == 64
m = 1UL << ((fls64(x) + 1) & ~1UL);
#else
m = 1UL << ((fls(x) + 1) & ~1UL);
#endif
Krzysztof Kozlowski writes:
> Remove old, dead Kconfig option USB_LED. It is gone since
> commit a335aaf3125c ("usb: misc: remove outdated USB LED driver").
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> arch/powerpc/configs/c2k_defconfig| 1 -
> arch/powerpc/configs/ppc6xx_defconfig | 1 -
Constify dw_mipi_dsi_stm_phy_ops as these ops are not supposed
to change at runtime.
Signed-off-by: Philippe CORNU
Reviewed-by: Benjamin Gaignard
---
drivers/gpu/drm/stm/dw_mipi_dsi-stm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/stm/dw_mipi_dsi-stm.c
Use devm_reset_control_get_exclusive to avoid resource leakage (based
on patch "Convert drivers to explicit reset API" from Philipp Zabel).
Also use platform_get_resource, which is more usual and
consistent with platform_get_irq called later.
Signed-off-by: Fabien Dessenne
Signed-off-by: Philipp
Rename the returned value from "res" to "ret" as it is more "readable".
Signed-off-by: Philippe CORNU
Reviewed-by: Benjamin Gaignard
---
drivers/gpu/drm/stm/ltdc.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/gpu/drm/stm/ltd
From: Qiuyang Sun
This patch implements Direct Access (DAX) in F2FS, including:
- a mount option to choose whether to enable DAX or not
- read/write and mmap of regular files in the DAX way
- zero-out of unaligned partial blocks in the DAX way
- garbage collection of DAX files, by mapping bot
Constify drm funcs structures.
Signed-off-by: Philippe CORNU
Reviewed-by: Benjamin Gaignard
---
drivers/gpu/drm/stm/ltdc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/gpu/drm/stm/ltdc.c
index 628825b..92e58ba 100644
--- a/driver
Rename the platform driver name from "stm" to "stm32-display"
for a better readability in /sys/bus/platform/drivers entries.
Note: We keep "stm" as drm_driver.name because it is better
when using "modetest -M stm ..." (even if recent modetest patch
avoids using -M).
Signed-off-by: Philippe CORNU
The GCR_PCPOL/DEPOL/VSPOL/HSPOL defines are sufficient to
describe the HS, VS, DE & PC signal polarities.
Signed-off-by: Philippe CORNU
Reviewed-by: Benjamin Gaignard
---
drivers/gpu/drm/stm/ltdc.c | 28 ++--
1 file changed, 10 insertions(+), 18 deletions(-)
diff --git
Version 2:
- Add devm_reset_control_get_exclusive to follow explicit reset API
- Add missing commit messages & reviewed-by.
Version 1:
- Initial commit
The purpose of this set of patches is to clean up the drm stm driver.
Philippe CORNU (7):
drm/stm: drv: Rename platform driver name
drm/stm:
Lindent then checkpatch --strict cleanups
Signed-off-by: Philippe CORNU
Reviewed-by: Benjamin Gaignard
---
drivers/gpu/drm/stm/ltdc.c | 172 ++---
1 file changed, 85 insertions(+), 87 deletions(-)
diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/gpu/drm
Warnings:
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dtb: Warning
(unit_address_format): Node
/amba/spi@ff04/spi0_flash0@0/spi0_flash0@ unit name should
not have leading 0s
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dtb: Warning
(unit_address_format): Node
/amba/spi@ff05/spi1_flash0@0/spi
Nodes without reg properties shouldn't be placed in amba node.
Move them out.
Warnings:
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dtb: Warning (simple_bus_reg):
Node /amba/misc_clk missing or empty reg/ranges property
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dtb: Warning (simple_bus_reg):
Node /amba/
Hi Todor,
On Mon, Jul 17, 2017 at 01:33:33PM +0300, Todor Tomov wrote:
> These files control the CSIPHY modules which are responsible for the physical
> layer of the CSI2 receivers.
>
> Signed-off-by: Todor Tomov
> ---
> .../media/platform/qcom/camss-8x16/camss-csiphy.c | 816
> ++
Hi Icenowy,
icen...@aosc.io píše v Čt 20. 07. 2017 v 16:21 +0800:
> 在 2017-07-20 06:59，Ondřej Jirman 写道：
> > Hi,
> >
> > Icenowy Zheng píše v Út 04. 04. 2017 v 17:50 +0800:
> > > From: Icenowy Zheng
> > >
> > > Now we have driver for the PRCM CCU, switch to use it instead of
> > > old-style clo
On 19 July 2017 at 19:28, Andy Shevchenko
wrote:
> There are new types and helpers that are supposed to be used in new code.
>
> As a preparation to get rid of legacy types and API functions do
> the conversion here.
>
> Cc: Matt Fleming
> Cc: Ard Biesheuvel
> Signed-off-by: Andy Shevchenko
Ac
Constify dw_mipi_dsi_bridge_funcs as these functions are not supposed
to change at runtime.
Signed-off-by: Philippe CORNU
Reviewed-by: Laurent Pinchart
---
drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bridge/sy
Version 2:
- Put back Synopsys mipi dsi unused registers.
- Add devm_reset_control_get_exclusive to follow explicit reset API.
- Add a missing commit message & reviewed-by.
Version 1:
- Initial commit
The purpose of this set of patches is to clean up the mipi dsi dw
Synopsys drm bridge.
Philippe
Hi,
I have cherry-picked all patches from xilinx soc vendor tree which are
ready for submission.
This patchset targets only zynqmp.dtsi which is shared with all zynqmp
families.
Thanks,
Michal
Bharat Kumar Gogada (1):
arm64: zynqmp: Adding prefetchable memory space to pcie node
Edgar E. Igle
Add missing references to all cpu nodes.
Signed-off-by: Michal Simek
---
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
index 1a3f5e928bb9..4f7d99
From: Shubhrajyoti Datta
Adding operating-points-v2 for zynqmp.
Signed-off-by: Shubhrajyoti Datta
Signed-off-by: Michal Simek
---
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 29 +
1 file changed, 29 insertions(+)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
The following commits:
c815fde wlcore: spi: Populate config firmware data
d776fc8 wlcore: sdio: Populate config firmware data
Populated the nvs entry for wilink6 and wilink7 only while it is
still needed for wilink8 as well.
This broke user space backward compatibility when upgrading from older
From: Bharat Kumar Gogada
Adding prefetchable memory space to pcie device tree node.
Shifting configuration space to 64-bit address space.
Removing pcie device tree node from amba as it requires size-cells=<2>
in order to access 64-bit address space.
Signed-off-by: Bharat Kumar Gogada
Signed-of
Add CCI-400 node to DTSI.
Signed-off-by: Michal Simek
---
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
index 3657fdbdb552..f3968737e613 100644
---
Add support for RTC.
Signed-off-by: Michal Simek
---
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
index e7d1815c114b..1272fa6d4f99 100644
--- a/arch/arm64/b
> The following commits:
> c815fde wlcore: spi: Populate config firmware data
> d776fc8 wlcore: sdio: Populate config firmware data
>
> Populated the nvs entry for wilink6 and wilink7 only while it is
> still needed for wilink8 as well.
> This broke user space backward compatibility when upgrading
On Thu, Jul 13, 2017 at 07:02:37PM -0700, Saravana Kannan wrote:
> In all Qualcomm chipsets (well, at least the ones that have been used in
> Android devices so far), we can switch the frequency of any CPU from any
> other CPU. If we can do that even without fast switching, why wouldn't any
> theor
301 - 400 of 969 matches
Mail list logo
