On Thu, Dec 13, 2018 at 1:45 AM Alexander Duyck
wrote:
>
> Add an additional bit flag to the device struct named "dead".
>
> This additional flag provides a guarantee that when a device_del is
> executed on a given interface an async worker will not attempt to attach
> the driver following the ear
Hi Naga,
+ Martin
Naga Sureshkumar Relli wrote on Tue, 18 Dec 2018
05:33:53 +:
> Hi Miquel,
>
> > -Original Message-
> > From: Miquel Raynal [mailto:miquel.ray...@bootlin.com]
> > Sent: Monday, December 17, 2018 10:11 PM
> > To: Naga Sureshkumar Relli
> > Cc: Boris Brezillon ; r..
On Mon, Dec 17, 2018 at 11:51:13PM +0100, Oscar Salvador wrote:
>v1 -> v2:
> - Fix the logic for skipping pages by Michal
>
>---
>>From e346b151037d3c37feb10a981a4d2a25018acf81 Mon Sep 17 00:00:00 2001
>From: Oscar Salvador
>Date: Mon, 17 Dec 2018 14:53:35 +0100
>Subject: [PATCH] mm, page_al
The following changes since commit 6531e115b7ab84f563fcd7f0d2d05ccf971aaaf9:
Merge branch 'akpm' (patches from Andrew) (2018-12-14 15:35:30 -0800)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-4.20-4
for you to fetch changes up to
On Wed, Dec 19, 2018 at 1:39 PM Daniel Vetter wrote:
>
> This is the much more correct fix for my earlier attempt at:
>
> https://lkml.org/lkml/2018/12/10/118
>
> Short recap:
>
> - There's not actually a locking issue, it's just lockdep being a bit
> too eager to complain about a possible deadl
On Mon, 3 Dec 2018 14:13:23 +0800, Xingyu Chen wrote:
> 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-control
On Mon, Dec 03, 2018 at 11:45:06AM +0800, Yu Chen wrote:
> This patch adds binding documentation to support usb hub and usb
> data role switch of Hisilicon HiKey&HiKey960 Board.
>
> Cc: Sergei Shtylyov
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: John Stultz
> Cc: Binghui Wang
> Signed-off-by:
Hi Daniel,
On Wed, Dec 19, 2018 at 11:32 AM Daniel Baluta wrote:
>
> On Wed, Dec 19, 2018 at 3:17 PM Daniel Baluta wrote:
> >
> >
> > On Wed, 2018-12-19 at 12:42 +, Marcel Ziswiler wrote:
> > > Hi there
> > >
> > > I noticed that at least today's and yesterdays -next won't build with
> > > t
Dear Sir,
My name is Nancy.M Michael of the International Monetary and Financial
Committee (IMFC) of the IMF. The IMF through an electronic random pick
has chosen your name for compensation/payment. At the meeting of heads
of international financial institutions held recently in Geneva
Switzerl
GCC 9 introduces a new option, -flive-patching. It disables certain
optimizations which could make a compilation unsafe for later live
patching of the running kernel.
The option is used only if CONFIG_LIVEPATCH is enabled and $(CC)
supports it.
Signed-off-by: Miroslav Benes
---
Makefile | 4 +++
On Mon, Dec 03, 2018 at 11:45:05AM +0800, Yu Chen wrote:
> This patch adds binding documentation for supporting the hi3660 usb
> phy on boards like the HiKey960.
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: John Stultz
> Cc: Binghui Wang
> Signed-off-by: Yu Chen
> --
> v1: Fix some format err
[+cc Sven, Trent, et al from related report:
https://lore.kernel.org/linux-pci/20181218210444.5950-1-thesve...@googlemail.com]
On Fri, Dec 14, 2018 at 06:44:15AM +, Richard Zhu wrote:
> Assertion of the MSI Enable bit of RC's MSI CAP is mandatory required to
> trigger MSI on i.MX6 PCIe.
> This
Hello, Gerd!
On 12/18/18 9:33 AM, Gerd Hoffmann wrote:
Check first two header bytes before trying to read the edid blob,
to avoid the log being spammed in case qemu has no edid support (old
qemu or edid turned off).
Fixes: 01f23459cf drm/bochs: add edid support.
Signed-off-by: Gerd Hoffmann
--
Hi,
> > Sure this actually helps? It's below 4G in guest physical address
> > space, so it can be backed by pages which are actually above 4G in host
> > physical address space ...
>
> Yes, you are right here. This is why I wrote about the IOMMU
> and other conditions. E.g. you can have a devi
On Mon, Dec 03, 2018 at 05:28:56PM +0800, Chen Yu wrote:
> Hi,
>
> On 2018/12/3 16:59, Sergei Shtylyov wrote:
> > On 03.12.2018 11:51, Chen Yu wrote:
> >
> This patch adds binding descriptions to support the dwc3 controller
> on HiSilicon SoCs and boards like the HiKey960.
>
>
Hi John,
On 12/18/2018 6:35 PM, John Keeping wrote:
> Hi Minas,
>
> On Fri, 14 Dec 2018 09:00:08 +
> Minas Harutyunyan wrote:
>> First of all, sorry for delayed answer.
>> Looks like similar issue seen by Andrzej Pietrasiewicz
>> : "dwc2 isochronous transfers issues". Same
>> feedback provid
On Mon, Dec 03, 2018 at 12:23:14AM +0300, Mesih Kilinc wrote:
> Add compatible string for Allwinner suniv F1C100s audio codec.
Typo in the subject. Otherwise,
Reviewed-by: Rob Herring
>
> Signed-off-by: Mesih Kilinc
> ---
> Documentation/devicetree/bindings/sound/sun4i-codec.txt | 5 +
>
On Mon, 3 Dec 2018 00:23:10 +0300, Mesih Kilinc wrote:
> Add compatible string for Allwinner suniv F1C100s DMA.
>
> Signed-off-by: Mesih Kilinc
> ---
> Documentation/devicetree/bindings/dma/sun4i-dma.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring
Commit c1cae12e6b4a ("vfs: Add a sample program for the new mount API")
introduced a build error (regression) when building an allmodconfig
kernel. Before that SAMPLE_STATX had a "depends on BROKEN", and it got
removed in the patch.
When building an allmodconfig kernel, option SAMPLE_VFS gets enab
On Wed, Dec 19, 2018 at 6:33 AM james qian wang (Arm Technology China)
wrote:
>
> Add DT bindings documentation for the ARM display processor D71 and later
> IPs.
>
> Signed-off-by: James (Qian) Wang
> ---
> .../bindings/display/arm/arm,komeda.txt | 87 +++
> 1 file changed
On Tue, 18 Dec 2018 18:59:39 +0100,
sh...@kernel.org wrote:
>
> From: Shuah Khan
>
> Media Device Allocator API to allows multiple drivers share a media device.
> This API solves a very common use-case for media devices where one physical
> device (an USB stick) provides both audio and video. Wh
Hi Sebastian,
On 19.12.18 12:36, Sebastian Andrzej Siewior wrote:
> On 2018-12-19 07:50:17 [+], Schrempf Frieder wrote:
>> + linux-rt-users
>>
>> On 17.12.18 11:42, Frieder Schrempf wrote:
>>> Hi,
>>>
>>> I have tried to boot a 4.14-Kernel with the RT-patches and
>>> PREEMPT_RT_FULL on an i.MX
On Thu, Dec 13, 2018 at 04:48:07AM +, Yoshihiro Shimoda wrote:
Hi,
From: Sasha Levin, Sent: Thursday, December 13, 2018 1:28 PM
From: Yoshihiro Shimoda
[ Upstream commit ef1b5bf506b1f0ee3edc98533e1f3ecb105eb46a ]
This upstream commit is also reverted on mainline
as I mentioned other em
On Thu, Dec 13, 2018 at 04:44:41AM +, Yoshihiro Shimoda wrote:
Hi,
From: Sasha Levin , Sent: Thursday, December 13, 2018 1:28 PM
From: Yoshihiro Shimoda
[ Upstream commit 8c85f4b81296a530b8af2796c110fa482ac42d4f ]
Since this upstream commit are reverted by the following commit,
we shou
On Thu, Dec 13, 2018 at 09:31:06AM +0530, Ramalingam C wrote:
> If all the components associated to a component master is not added
> to the component framework due to the HW capability or Kconfig
> selection, component_match will be NULL at
> component_master_add_with_match().
>
> To avoid this,
On Wed, 19 Dec 2018 at 12:58, Valentin Schneider
wrote:
>
> On 19/12/2018 08:32, Vincent Guittot wrote:
> [...]
> > This is another UC, asym packing is used at SMT level for now and we
> > don't face this kind of problem, it has been also tested and DynamiQ
> > configuration which is similar to SM
On Tue, 18 Dec 2018 18:52:16 +0100,
Gustavo A. R. Silva wrote:
>
> ipcm->substream is indirectly controlled by user-space, hence leading to
> a potential exploitation of the Spectre variant 1 vulnerability.
>
> This issue was detected with the help of Smatch:
>
> sound/pci/emu10k1/emufx.c:1031
On Tue, 18 Dec 2018 18:18:34 +0100,
Gustavo A. R. Silva wrote:
>
> info->channel is indirectly controlled by user-space, hence leading to
> a potential exploitation of the Spectre variant 1 vulnerability.
>
> This issue was detected with the help of Smatch:
>
> sound/pci/rme9652/hdsp.c:4100 sn
Commit fc560a26acce ("cpuset: replace cpuset->stack_list with
cpuset_for_each_descendant_pre()") removed the local list (q)
that was used to perform a top-down scan of all cpusets;
however, comments mentioning it were not updated.
Update comments to reflect current implementation.
Signed-off-by:
Holding hotplug lock is not a requirement anymore for callers of sched_
init_domains after commit 6acce3ef8452 ("sched: Remove get_online_cpus()
usage").
Update the relative comment preceding init_sched_domains().
Signed-off-by: Juri Lelli
---
kernel/sched/topology.c | 5 ++---
1 file changed,
> > Has anybody seen that as well and knows what is going on?
>
> Hmm, works for me.
>
> Using linux-next, master branch. HEAD commit:
>
> commit 02fc169594e96f7c51c4f23114e12b7a18e85a0a (HEAD -> master, tag:
> next-20181219, origin/master, origin/HEAD)
> Author: S
On Wed, 19 Dec 2018 at 12:16, Valentin Schneider
wrote:
>
> On 19/12/2018 08:27, Vincent Guittot wrote:
> [...]
> >> Wouldn't LBF_ALL_PINNED cover all relevant cases? It's set at the very top
> >> of the 'if (busiest->nr_running > 1)' block and cleared whenever we find
> >> at least one task we co
On 2018-12-18 10:31, Thomas Gleixner wrote:
On Wed, 12 Dec 2018, Peter Zijlstra wrote:
On Mon, Dec 10, 2018 at 06:43:51PM +0100, Thomas Gleixner wrote:
@@ -806,6 +806,8 @@ void __noreturn do_exit(long code)
* task into the wait for ever nirwana as well.
*/
On Wed, Dec 19, 2018 at 02:18:25PM +0100, Daniel Vetter wrote:
> On Wed, Dec 19, 2018 at 01:49:30PM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Dec 19, 2018 at 01:39:09PM +0100, Daniel Vetter wrote:
> > > --- a/include/linux/device.h
> > > +++ b/include/linux/device.h
> > > @@ -327,6 +327,7 @@ str
On Wed, 19 Dec 2018 at 11:43, Ulf Hansson wrote:
>
> On Wed, 19 Dec 2018 at 11:34, Vincent Guittot
> wrote:
> >
> > On Wed, 19 Dec 2018 at 11:21, Ulf Hansson wrote:
> > >
> > > > > >
> > > > > > diff --git a/drivers/base/power/runtime.c
> > > > > > b/drivers/base/power/runtime.c
> > > > > > in
On Wed 19-12-18 10:42:54, Dave Chinner wrote:
> On Tue, Dec 18, 2018 at 11:33:06AM +0100, Jan Kara wrote:
> > On Mon 17-12-18 08:58:19, Dave Chinner wrote:
> > > On Fri, Dec 14, 2018 at 04:43:21PM +0100, Jan Kara wrote:
> > > > Yes, for filesystem it is too late. But the plan we figured back in
>
On 12/19/18 3:23 AM, Alexander Potapenko wrote:
> On Thu, Sep 13, 2018 at 11:23 AM Alexander Potapenko
> wrote:
>>
>> On Thu, Sep 13, 2018 at 11:18 AM syzbot
>> wrote:
>>>
>>> Hello,
>>>
>>> syzbot found the following crash on:
>>>
>>> HEAD commit:123906095e30 kmsan: introduce kmsan_interrup
Hi All,
Compiled the vanila kernel 4.20.0-rc6 build, and was trying to get
module information, but /proc/modules is not showing any output ( both
on arm64 and x86_64 )
root@ubuntu:~# uname -a
Linux ubuntu 4.20.0-rc6-00082-g65e08c5e8631 #7 SMP PREEMPT Fri Dec 14
15:54:30 IST 2018 aarch64 aarch64 a
On 12/19/18 3:14 PM, Gerd Hoffmann wrote:
Hi,
+ mapping = xen_obj->base.filp->f_mapping;
+ mapping_set_gfp_mask(mapping, GFP_USER | __GFP_DMA32);
Let's see if I understand what you're doing:
Here you say that the pages should be DMA accessible for devices that can
only see 4GB.
Yes,
On Fri, 30 Nov 2018, Yangtao Li wrote:
> Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
>
> Signed-off-by: Yangtao Li
> ---
> drivers/hid/hid-debug.c | 12 +---
> 1 file changed, 1 insertion(+), 11 deletions(-)
>
> diff --git a/drivers/hid/hid-debug.c b/drivers/hid/hid-debug.c
>
The xenstore 'ring-page-order' is used globally for each blkback queue and
therefore should be read from xenstore only once. However, it is obtained
in read_per_ring_refs() which might be called multiple times during the
initialization of each blkback queue.
If the blkfront is malicious and the 'r
On Tue, Dec 18, 2018 at 04:52:24PM -0500, Lyude Paul wrote:
> On Fri, 2018-12-14 at 10:32 +0100, Daniel Vetter wrote:
> > On Thu, Dec 13, 2018 at 08:25:35PM -0500, Lyude Paul wrote:
> > > So that the ports stay around until we've destroyed the connectors, in
> > > order to ensure that we don't pass
On Tue, Dec 18, 2018 at 01:26:00PM -0700, shuah wrote:
> On 12/18/18 9:39 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.19.11 release.
> > There are 44 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with
On Tue, Dec 18, 2018 at 03:10:25PM -0600, Dan Rue wrote:
> On Tue, Dec 18, 2018 at 05:39:12PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.19.11 release.
> > There are 44 patches in this series, all will be posted as a response
> > to this one. If any
On Sat, Dec 1, 2018 at 6:40 PM Sabyasachi Gupta
wrote:
>
> On Wed, Nov 21, 2018 at 7:18 PM Sabyasachi Gupta
> wrote:
> >
> > Replace dma_alloc_coherent + memset with dma_zalloc_coherent
> >
> > Signed-off-by: Sabyasachi Gupta
>
> Any comment on this patch?
Any comment on this patch?
>
> > ---
On Wed, Dec 19, 2018 at 01:49:30PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Dec 19, 2018 at 01:39:09PM +0100, Daniel Vetter wrote:
> > --- a/include/linux/device.h
> > +++ b/include/linux/device.h
> > @@ -327,6 +327,7 @@ struct driver_attribute {
> > #define DRIVER_ATTR_WO(_name) \
> > struc
me.
Using linux-next, master branch. HEAD commit:
commit 02fc169594e96f7c51c4f23114e12b7a18e85a0a (HEAD -> master, tag:
next-20181219, origin/master, origin/HEAD)
Author: Stephen Rothwell
Date: Wed Dec 19 18:42:46 2018 +1100
Add linux-next specific files for 20181219
Signed-off-by: Stephen Rothwell
Using gcc version 7.3.0 (GCC).
On Tue, Dec 18, 2018 at 11:38:36AM -0200, Shayenne Moura wrote:
> This patch finalizes the KMS cleanup task dependency from drm_display_mode
> It removes the use of drm_mode_object from drm_display_mode struct
> and it removes the use of base.id and base.type.
>
> Signed-off-by: Shayenne Moura
I
Hi,
> > > + mapping = xen_obj->base.filp->f_mapping;
> > > + mapping_set_gfp_mask(mapping, GFP_USER | __GFP_DMA32);
> > Let's see if I understand what you're doing:
> >
> > Here you say that the pages should be DMA accessible for devices that can
> > only see 4GB.
>
> Yes, your understa
On Tue, Dec 18, 2018 at 11:38:30AM -0200, Shayenne Moura wrote:
> This patch removes base.id prints from drm_display_mode
>
> objects in meson files. It removes dependency from drm_mode_object.
>
> Signed-off-by: Shayenne Moura
> ---
> drivers/gpu/drm/meson/meson_dw_hdm
On Tue, Dec 18, 2018 at 11:38:25AM -0200, Shayenne Moura wrote:
> This patch removes base.id prints from drm_display_mode
>
> objects in sti files. It removes dependency from drm_mode_object.
>
> Signed-off-by: Shayenne Moura
Reviewed-by: Daniel Vetter
> ---
> driver
On Tue, Dec 18, 2018 at 11:38:21AM -0200, Shayenne Moura wrote:
> This patch removes base.id prints from drm_display_mode
>
> objects in i915 files. It removes dependency from drm_mode_object.
>
> Signed-off-by: Shayenne Moura
Again I think better to switch to DRM_MODE_
From: Peter Rosin
Hi!
I'm not sure if I should have added the texas chips to the lvds_encoder_match
list in the driver, right next to the thine,thc63lvdm83d entry, but ended
up not doing that. That can always be added later, it needed...
Changes since v1:
- fork out the bindings for the texas c
On Tue, Dec 18, 2018 at 11:38:10AM -0200, Shayenne Moura wrote:
> This patch removes the drm_mode_object prints, evaluation and use from
> drm_display_mode objects used in drm files. It removes dependency from
> drm_mode_object.
>
> Signed-off-by: Shayenne Moura
Reviewed-by: Daniel Vetter
> --
On Sat, Dec 1, 2018 at 6:45 PM Sabyasachi Gupta
wrote:
>
> On Sat, Nov 17, 2018 at 6:17 PM Sabyasachi Gupta
> wrote:
> >
> > Replaced dma_alloc_coherent + memset with dma_zalloc_coherent
> >
> > Signed-off-by: Sabyasachi Gupta
>
> Any comment on this patch?
Any comment on this patch?
>
> > ---
From: Peter Rosin
Optionally power down the LVDS-encoder when it is not in use.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/bridge/lvds-encoder.c | 34 ++
1 file changed, 34 insertions(+)
diff --git a/drivers/gpu/drm/bridge/lvds-encoder.c
b/drivers/gpu/drm/
On Tue, Dec 18, 2018 at 11:38:15AM -0200, Shayenne Moura wrote:
> This patch removes base.id prints from drm_display_mode
>
> objects in omapdrm files. It removes dependency from drm_mode_object.
>
> Signed-off-by: Shayenne Moura
Same comment as for msm, I think better
From: Peter Rosin
Drop #address-cells and #size-cells from the root node in the
example, they are unused.
Signed-off-by: Peter Rosin
---
Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt | 2 --
1 file changed, 2 deletions(-)
diff --git
a/Documentation/devicetree/bindings
From: Peter Rosin
DS90C185 has a shutdown pin which does not fit in the lvds-transmitter
binding, which is meant to be generic.
The sister chip DS90C187 is similar to DS90C185, describe it here as well.
Signed-off-by: Peter Rosin
---
.../bindings/display/bridge/lvds-transmitter.txt | 8 +--
Em Wed, Dec 19, 2018 at 06:15:00PM +0900, Namhyung Kim escreveu:
> On Tue, Dec 18, 2018 at 07:07:27PM -0300, Arnaldo Carvalho de Melo wrote:
> > Helps with comparing 'strace' and 'perf trace' output, for mutual
> > regression testing.
> > +++ b/tools/perf/trace/beauty/mmap.c
> > @@ -17,8 +17,8 @
On Tue, Dec 18, 2018 at 11:38:03AM -0200, Shayenne Moura wrote:
> This patch removes base.id prints from drm_display_mode
> objects in msm files. It removes dependency from drm_mode_object.
>
> Signed-off-by: Shayenne Moura
I think switching these over to the DRM_MODE_FMT and DRM_MODE_ARG like
d
On Tue, 18 Dec 2018, Shayenne Moura wrote:
> This patch removes base.id prints from drm_display_mode
>
> objects in i915 files. It removes dependency from drm_mode_object.
As said, this could expand on the *why*. With that fixed,
Reviewed-by: Jani Nikula
as well as ac
On Fri, 14 Dec 2018, Kai-Heng Feng wrote:
> While using Elan touchpads, the message floods:
> [ 136.138487] i2c_hid i2c-DELL08D6:00: i2c_hid_get_input: incomplete report
> (14/65535)
>
> Though the message flood is annoying, the device it self works without
> any issue. I suspect that the devic
On Tue, 18 Dec 2018, Shayenne Moura wrote:
> This patch serie removes drm_mode_object dependency from
> drm_display_mode struct. This is part of KMS cleanup.
For future reference:
Please use git-send-email or fix the mail threading otherwise. Patches
1-7 should be in reply to the cover letter
On Wed, Dec 19, 2018 at 4:23 PM Thomas Gleixner wrote:
>
> On Tue, 4 Dec 2018, Dou Liyang wrote:
>
> > Now, Spreading the interrupt affinity info by a cpumask pointer is not
> > enough, meets a problem[1] and hard to expand in the future.
> >
> > Fix it by:
> >
> > +-
On Wed, 19 Dec 2018 at 13:11, Daniel Lezcano wrote:
>
> On 29/11/2018 18:46, Ulf Hansson wrote:
> > From: Lina Iyer
> >
> > Currently CPU's idle states are represented in a flattened model, via the
> > "cpu-idle-states" binding from within the CPU's device nodes.
> >
> > Support the hierarchical
On 2018-12-19 12:38, Laurent Pinchart wrote:
> Hello,
>
> On Wednesday, 19 December 2018 11:57:32 EET Peter Rosin wrote:
>> On 2018-12-19 10:12, Andrzej Hajda wrote:
>>> On 19.12.2018 00:19, Peter Rosin wrote:
Add optional property to specify a power-down GPIO.
The pwdn-gpios name is alr
On Tue, Dec 18, 2018 at 05:59:38PM +, Catalin Marinas wrote:
> On Tue, Dec 18, 2018 at 04:03:38PM +0100, Andrey Konovalov wrote:
> > On Wed, Dec 12, 2018 at 4:02 PM Catalin Marinas
> > wrote:
> > > The summary of our internal discussions (mostly between kernel
> > > developers) is that we can
ks_pcie_get_irq_controller_info() was used to configure both MSI and
legacy interrupt. This will prevent MSI or legacy interrupt specific
intializations. Add separate functions to configure MSI and legacy
interrupts.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/controller/dwc/pci-keysto
Em Wed, Dec 19, 2018 at 05:40:24PM +0900, Namhyung Kim escreveu:
> On Tue, Dec 18, 2018 at 07:07:05PM -0300, Arnaldo Carvalho de Melo wrote:
> > + if (!strcmp(var, "trace.add_events")) {
> > + struct trace *trace = arg;
> > + struct option o = OPT_CALLBACK('e', "event", &trace
On Wed, Dec 19, 2018 at 01:39:09PM +0100, Daniel Vetter wrote:
> --- a/include/linux/device.h
> +++ b/include/linux/device.h
> @@ -327,6 +327,7 @@ struct driver_attribute {
> #define DRIVER_ATTR_WO(_name) \
> struct driver_attribute driver_attr_##_name = __ATTR_WO(_name)
>
> +
> extern in
On Tue, Dec 18, 2018 at 04:27:58PM -0500, Lyude Paul wrote:
> On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote:
> > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote:
> > > The current way of handling refcounting in the DP MST helpers is really
> > > confusing and probably just plain
On 12/19/18 5:20 AM, Michal Hocko wrote:
> On Tue 18-12-18 20:57:32, Qian Cai wrote:
> [...]
>> diff --git a/include/linux/mm.h b/include/linux/mm.h
>> index 5411de93a363..f083f366ea90 100644
>> --- a/include/linux/mm.h
>> +++ b/include/linux/mm.h
>> @@ -985,9 +985,7 @@ extern int page_to_nid(const
Hi Pawel,
> This patch adds the device ID for the BCM 4329 combo module used
> in the Samsung Aries based phones (Galaxy S and it's variants).
>
> ```
> [ 11.508980] Bluetooth: hci0: BCM: chip id 41
> [ 11.518975] Bluetooth: hci0: BCM: features 0x04
> [ 11.550132] Bluetooth: hci0: BCM4329B1
Hi Pawel,
> The Broadcom controller on aries S5PV210 boards sends out a couple of
> unknown packets after the firmware is loaded. This will cause
> logging of errors such as:
> Bluetooth: hci0: Frame reassembly failed (-84)
>
> This is probably also the case with other boards, as there are
On Wed, Dec 19, 2018 at 06:03:45PM +0800, Rong Chen wrote:
> On 12/18/2018 08:17 PM, Matthew Wilcox wrote:
> > On Tue, Dec 18, 2018 at 08:20:28AM +0800, kernel test robot wrote:
> > > Greetings,
> > >
> > > 0day kernel testing robot got the below dmesg and the first bad commit is
> > >
> > > http
Use Keystone specific msi_irq_chip to configure the MSI controller
logic in the PCIe keystone wrapper instead of using the default
Designware msi_irq chip (dw_pci_msi_bottom_irq_chip) with
callback functions for configuring the Keystone MSI controller.
This will help to remove Keystone specific cal
On 19/12/2018 14:29, Joe Perches wrote:
On Wed, 2018-12-19 at 11:59 +, Andy Whitcroft wrote:
On Wed, Dec 19, 2018 at 02:44:36AM -0800, Joe Perches wrote:
To cover both cases perhaps:
"please ensure that this config symbols is described fully (less than
$min_conf_desc_
Both ks_pcie_msi_irq_handler() and ks_pcie_legacy_irq_handler() invokes
ks_pcie_handle_msi_irq() and ks_pcie_handle_legacy_irq() respectively
for handling the interrupts.
Having two functions for handling the interrupt was used when keystone
PCIe driver was implemented using two files. But with
co
Hi,
On 19/12/18 3:41 PM, Yogesh Narayan Gaur wrote:
> Add support for octal mode IO data transfer.
> Micron flash, mt35xu512aba, supports octal mode data transfer and
> NXP FlexSPI controller supports 8 data lines for data transfer (Rx/Tx).
>
> Patch series
> * Add support for octal mode flags an
The legacy interrupt handler directly checks the IRQ_STATUS register
corresponding to a interrupt line inorder to invoke generic_handle_irq.
While this is okay for K2G platform which has separate interrupt line for
each of the 4 legacy interrupts, AM654 which uses the same PCIe wrapper
has a singl
No functional change. Change both MSI interrupt and legacy interrupt
related macros to take an additional argument in order to return the
correct register offset.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/controller/dwc/pci-keystone.c | 26 +++
1 file changed, 13
Platforms using Designware IP uses dw_pci_msi_bottom_irq_chip for
configuring the MSI controller logic within the Designware IP. However
certain platforms like Keystone (K2G) which uses Desingware IP has
it's own MSI controller logic. For handling such platforms,
the irqchip ops uses msi_irq_ack, m
Now that Keystone started using it's own msi_irq_chip, remove
Keystone specific callback function defined in dw_pcie_host_ops.
Signed-off-by: Kishon Vijay Abraham I
---
.../pci/controller/dwc/pcie-designware-host.c | 45 ++-
drivers/pci/controller/dwc/pcie-designware.h | 5 ---
ks_pcie_msi_irq_handler() uses 'virq' to get the IRQ number offset.
This offset is used to get the correct MSI_IRQ_STATUS register
corresponding to the IRQ line that raised the interrupt.
There is no guarantee that 'virq' assigned for consecutive hardware
IRQ will be contiguous. And this might get
Platforms which populate msi_host_init, has it's own MSI controller
logic. Writing to MSI control registers on platforms which doesn't use
Designware's MSI controller logic might have side effects. To
be safe, do not write to MSI control registers if the platform uses
it's own MSI controller logic
Instead of creating a new irqchip with empty callback functions, use
dummy_irq_chip. Since there is nothing to do in the irqchip callback
functions, use handle_simple_irq instead of handle_level_irq.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/controller/dwc/pci-keystone.c | 24 ++-
This series tries to address the comments discussed in [1] w.r.t
removing Keystone specific callbacks defined in dw_pcie_host_ops.
This series also tries to cleanup the Keystone interrupt handling
part.
This series is created on top of
git://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.
Hi there
I noticed that at least today's and yesterdays -next won't build with
the imx_v6_v7_defconfig giving the following error:
LD arch/arm/boot/compressed/vmlinux
arch/arm/boot/compressed/head.o: In function `restart':
(.text+0xa8): undefined reference to `__hyp_stub_vectors'
(.text+0x
"Grumbach, Emmanuel" writes:
>>
>> Stephen Rothwell writes:
>>
>> > On Fri, 30 Nov 2018 12:05:55 +1100 Stephen Rothwell
>> wrote:
>> >>
>> >> After merging the wireless-drivers-next tree, today's linux-next
>> >> build
>> >> (x86_64 allmodconfig) produced these warnings:
>> >>
>> >> drivers/n
From: Patrice Chotard
The pen_release implementation was created for Versatile platforms to
work around boot loaders that did not differentiate between the
various different secondary CPUs on this ARM development platform.
This should not be true of modern platforms where we send IPIs to
specific
This is the much more correct fix for my earlier attempt at:
https://lkml.org/lkml/2018/12/10/118
Short recap:
- There's not actually a locking issue, it's just lockdep being a bit
too eager to complain about a possible deadlock.
- Contrary to what I claimed the real problem is recursion on
On Tue, Dec 18, 2018 at 05:51:12PM +0200, Roger Quadros wrote:
> We could combine control and debug into one iomap and use
> 2 regmap ranges. But this is really working around the
> regmap_mmio limitation of not being able to use more than one ioremaps.
> Mark, any suggestions?
If they're separa
On Wed, Dec 19, 2018 at 05:34:32PM +0530, Buland Singh wrote:
> On 12/19/18 3:16 PM, Greg KH wrote:
> > On Wed, Dec 19, 2018 at 02:55:02PM +0530, Buland Singh wrote:
> > > The kernel command parameter 'hpet_mmap' never takes effect due to missing
> > > '=' character in the __setup() code of hpet_mm
The objcopy only emits loadable sections when creating flat kernel
Image. To have minimal possible size of flat kernel Image, we should
have all non-loadable sections after loadable sections.
Currently, execption table section (loadable section) is after BSS
section (non-loadable section) in the R
v2: Adjusted the position of KOMEDA by alphabetical order
Signed-off-by: James (Qian) Wang
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 254b7b267731..e48c2e5fd29f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1124,6 +1124,15 @@ S:
v2: Some editing changes according to Randy Dunlap's comments
Signed-off-by: James (Qian) Wang
---
Documentation/gpu/drivers.rst| 1 +
Documentation/gpu/komeda-kms.rst | 488 +++
2 files changed, 489 insertions(+)
create mode 100644 Documentation/gpu/komeda-kms
komeda_framebuffer is for extending drm_framebuffer to add komeda own
attributes and komeda specific fb handling.
Signed-off-by: James (Qian) Wang
---
drivers/gpu/drm/arm/display/komeda/Makefile | 3 +-
.../arm/display/komeda/komeda_framebuffer.c | 165 ++
.../arm/display/k
Add komeda_kms abstracton to attach komeda_dev to DRM-KMS
CRTC: according to the komeda_pipeline
PLANE: according to komeda_layer (layer input pipeline)
PRIVATE_OBJS: komeda_pipeline/component all will be treat as private_objs
komeda_kms is for connecting DRM-KMS and komeda_dev, like reporti
On Wed, Dec 19, 2018 at 01:45:17PM +0200, Alexander Shishkin wrote:
> Greg Kroah-Hartman writes:
>
> > On Fri, Dec 14, 2018 at 05:53:45PM +0200, Alexander Shishkin wrote:
> >> Commit ccddbbf4ef27 ("stm class: Introduce framing protocol drivers")
> >
> > I don't see that commit id in Linus's tree,
601 - 700 of 949 matches
Mail list logo