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] =
Ah. Good. My mistake.
regards,
dan carpenter
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)
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
> -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 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
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
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
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 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
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 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.
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_
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 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
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 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
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 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 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
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
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
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
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
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
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
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
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
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:
>
>
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
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-
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
> >>>
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
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 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 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
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 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
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
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
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
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
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/
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
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);
>+
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
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
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
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
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 -
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
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
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, 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 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
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 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
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
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: 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
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: d460131dd50599e0e9405d5f4ae02c27d529a44a
Gitweb: http://git.kernel.org/tip/d460131dd50599e0e9405d5f4ae02c27d529a44a
Author: Arnd Bergmann
AuthorDate: Wed, 19 Jul 2017 14:53:03 +0200
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 10:46:24 +0200
x86/build: Silence the bui
On Thu, 2017-06-08 at 23:45 +0200, Arnd Bergmann wrote:
> On Thu, Jun 8, 2017 at 11:25 PM, Andy Shevchenko
> wrote:
> > On Thu, Jun 8, 2017 at 11:42 PM, Rasmus Villemoes
> > wrote:
> > > On Thu, Jun 08 2017, Andy Shevchenko
> > > wrote:
> > > > On Thu, Jun 8, 2017 at 9:41 PM, Alexandre Belloni
>
From: Colin Ian King
The function v4l2_fwnode_endpoint_parse_csi1_bus does not need to be
in global scope, so make it static. Also reformat the function arguments
as adding the static keyword made one of the source lines more than 80
chars wide and checkpatch does not like that.
Cleans up spars
Commit-ID: 0bc73048d7baecf94117d1a948853a627e6ba5c8
Gitweb: http://git.kernel.org/tip/0bc73048d7baecf94117d1a948853a627e6ba5c8
Author: Arnd Bergmann
AuthorDate: Wed, 19 Jul 2017 14:53:06 +0200
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 10:46:25 +0200
x86/platform/intel-mid: Fi
From: Steffen Trumtrar
Add a devicetree entry for the Random Number Generator Version C (RNGC).
Signed-off-by: Steffen Trumtrar
Signed-off-by: Martin Kaiser
---
Changes in v4:
none
Changes in v3:
- remove clock-names from dtsi
Changes in v2:
- remove interrupt-names from dtsi
arch/ar
cp->cp_send_gen is treated as a normal variable, although it may be
used by different threads.
This is fixed by using {READ,WRITE}_ONCE when it is incremented and
READ_ONCE when it is read outside the {acquire,release}_in_xmit
protection.
Normative reference from the Linux-Kernel Memory Model:
From: Steffen Trumtrar
The driver is ported from Freescales Linux git and can be
found in the
vendor/freescale/imx_2.6.35_maintain
branch.
According to that code, the RNGC is found on Freescales i.MX3/5 SoCs.
The i.MX2x actually has an RNGB, which has no driver implementation
in Freesc
The physical size of the panel is 105.5 (W) x 67.2 (H) x 4.05 (D) mm
but the active display area is 95.04 (W) x 53.856 (H) mm.
The width and height should be set to the active display area.
Signed-off-by: Jonathan Liu
---
drivers/gpu/drm/panel/panel-simple.c | 4 ++--
1 file changed, 2 insertio
From: Steffen Trumtrar
Add binding documentation for the Freescale RNGC found on
some i.MX2/3 SoCs.
Signed-off-by: Steffen Trumtrar
Signed-off-by: Martin Kaiser
---
Changes in v4:
none
Changes in v3:
- add compatible string for imx35
- remove imx5 from the commit message,
I couldn't
Commit-ID: 75e2f0a6b16141cb347f442033ec907380d4d66e
Gitweb: http://git.kernel.org/tip/75e2f0a6b16141cb347f442033ec907380d4d66e
Author: Arnd Bergmann
AuthorDate: Wed, 19 Jul 2017 14:53:00 +0200
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 10:46:24 +0200
x86/fpu/math-emu: Fix poss
Commit-ID: 5623452a0eaec1d44cc9f0770444a48847c9953f
Gitweb: http://git.kernel.org/tip/5623452a0eaec1d44cc9f0770444a48847c9953f
Author: Arnd Bergmann
AuthorDate: Wed, 19 Jul 2017 14:53:01 +0200
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 10:46:24 +0200
x86/fpu/math-emu: Avoid bo
Commit-ID: 11d8b05855f3749bcb6c57e2c4052921b9605c77
Gitweb: http://git.kernel.org/tip/11d8b05855f3749bcb6c57e2c4052921b9605c77
Author: Arnd Bergmann
AuthorDate: Wed, 19 Jul 2017 14:52:59 +0200
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 10:46:23 +0200
perf/x86: Shut up false-po
On 7/19/2017 7:04 PM, Logan Gunthorpe wrote:
>
>
> 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.
>
Looks like the patch set does not compile on PPC (.config generated
On Wed 19-07-17 10:26:45, Ross Zwisler wrote:
> On Wed, Jul 19, 2017 at 05:33:14PM +0200, Jan Kara wrote:
> > On Wed 28-06-17 16:01:50, Ross Zwisler wrote:
> > > Another major change is that we remove dax_pfn_mkwrite() from our fault
> > > flow, and instead rely on the page fault itself to make the
Replace the obsolete compatible string for Coresight programmable
replicator with the new one.
Cc: Andy Gross
Cc: David Brown
Cc: linux-arm-...@vger.kernel.org
Cc: Mathieu Poirier
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 2 +-
1
On 07/19/2017 06:02 PM, Rob Herring wrote:
diff --git a/drivers/media/v4l2-core/v4l2-async.c
b/drivers/media/v4l2-core/v4l2-async.c
index 851f128eba22..0a385d1ff28c 100644
--- a/drivers/media/v4l2-core/v4l2-async.c
+++ b/drivers/media/v4l2-core/v4l2-async.c
@@ -47,9 +47,7 @@ static bool match_fw
From: Matthias Brugger
This patch adds the binding for the MT6797 SoC.
Signed-off-by: Matthias Brugger
---
Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/watchdog/mtk-wdt.txt
b/Documentation/devicetr
After adding the clock subsystem to the SOC, the dummy
clock clk32k is not longer needed. Delete it.
Signed-off-by: Matthias Brugger
---
arch/arm64/boot/dts/mediatek/mt6797.dtsi | 7 ---
1 file changed, 7 deletions(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt6797.dtsi
b/arch/arm64/boot/
From: Matthias Brugger
This patch cleans up the binding documentation stating explicitly
the binding and it's fallback for every SoC.
Signed-off-by: Matthias Brugger
---
Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --gi
On Thu, 2017-06-08 at 22:59 +0200, Rasmus Villemoes wrote:
> On Thu, Jun 08 2017, Andy Shevchenko m> wrote:
> > The pointer can't be NULL since it's first what has been done in the
> > pointer().
> > - if (ZERO_OR_NULL_PTR(addr))
> > - return string(buf, end, NULL, spec);/* NULL
From: Matthias Brugger
This patch adds the watchdog driver to the MT6796 SoC.
Signed-off-by: Matthias Brugger
---
arch/arm64/boot/dts/mediatek/mt6797.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt6797.dtsi
b/arch/arm64/boot/dts/mediatek/mt6797.dt
As per coresight standards, PIDR2 register has the following format :
[2-0] - JEP106_bits6to4
[3]- JEDEC, designer ID is specified by JEDEC.
However some of the drivers only use mask of 0x3 for the PIDR2 leaving
bits [3-2] unchecked, which could potentially match the component for
a differ
Replace the obsolete compatible string for Coresight programmable
replicator with the new one.
Cc: Andy Gross
Cc: David Brown
Cc: linux-arm-...@vger.kernel.org
Cc: Mathieu Poirier
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 2 +-
1 f
Use the new compatible for ATB programmable replicator in Juno.
Cc: Sudeep Holla
Cc: Mike Leach
Cc: Mathieu Poirier
Cc: Liviu Dudau
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
arch/arm64/boot/dts/arm/juno-base.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Use the new helpers for exposing coresight component registers,
choosing the 64bit variants for appropriate registers.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-etb10.c | 22
.../hwtracing/coresight/coresight-etm3x-sysfs.
Expose DBALO,DBAHI and AXICTL registers
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-tmc.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/hwtracing/coresight/coresight-tmc.c
b/drivers/hwtracing/coresight/coresight-tmc.c
index aa
The Linux coresight drivers define the programmable ATB replicator as
Qualcomm replicator, while this is designed by ARM. This can cause
confusion to a user selecting the driver. Cleanup all references to
make it explicitly clear. This patch :
1) Replace the compatible string for the replicator :
Christoph noticed [1] that default DMA pool in current form overload
the DMA coherent infrastructure. In reply, Robin suggested [2] to
split the per-device vs. global pool interfaces, so allocation/release
from default DMA pool is driven by dma ops implementation.
This patch implements Robin's ide
Hi,
This is follow-up for Christoph complain [1] of overloading the current
dma coherent infrastructure with the global pool. To address that I
implemented Robin's idea of the new interface to the global pool and
wire up it with (only existent user) ARM NOMMU. Since I have not
heard from Vitaly a
* Linus Torvalds wrote:
> On Tue, Jul 18, 2017 at 2:21 PM, Dave Airlie wrote:
> >
> > Oh and just FYI, the machine I've tested this on has an mgag200 server
> > graphics card backing the framebuffer, but with just efifb loaded.
>
> Yeah, it looks like it needs special hardware - and particular
Add support for reading a lower and upper 32bits of a register
as a single 64bit register. Also add simplified macros for
direct register accesses.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-priv.h | 29 +++-
1 file chan
601 - 700 of 969 matches
Mail list logo
