Hi,
On Tue, Dec 18 2018, Andi Kleen wrote:
>> OK, I have read through it and with the caveats that I don't quite
>> understand what the failure is, that also believe attribute noclone
>> should not affect frame pointer generation, and that I don't quite get
>> how LTO comes into play, my comments
Vmalloc() is getting more and more used these days (kernel stacks,
bpf and percpu allocator are new top users), and the total %
of memory consumed by vmalloc() can be pretty significant
and changes dynamically.
/proc/meminfo is the best place to display this information:
its top goal is to show
alloc_vmap_area() is allocating memory for the vmap_area, and
performing the actual lookup of the vm area and vmap_area
initialization.
This prevents us from using a pre-allocated memory for the map_area
structure, which can be used in some cases to minimize the number
of required memory
__vunmap() calls find_vm_area() twice without an obvious reason:
first directly to get the area pointer, second indirectly by calling
remove_vm_area(), which is again searching for the area.
To remove this redundancy, let's split remove_vm_area() into
__remove_vm_area(struct vmap_area *), which
The patchset contains few changes to the vmalloc code, which are
leading to some performance gains and code simplification.
Also, it exports a number of pages, used by vmalloc(),
in /proc/meminfo.
Patch (1) removes some redundancy on __vunmap().
Patch (2) separates memory allocation and data
On 12/19/18 9:04 AM, Eugeniy Paltsev wrote:
> Just curious: isn't that enough to use GFP_NOWAIT instead
> of GFP_KERNEL when we allocate page in show_regs()?
>
> As I can see x86 use print_vma_addr() in their show_signal_msg()
> function which allocate page with __get_free_page(GFP_NOWAIT);
I'm
On 12/19, Daniel Vetter wrote:
> 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
Hi Jason,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net/master]
url:
https://github.com/0day-ci/linux/commits/Jason-Wang/Fix-various-issue-of-vhost/20181210-223236
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
Hi,
On Tue, Dec 18 2018, Josh Poimboeuf wrote:
> On Tue, Dec 18, 2018 at 01:15:40PM +0100, Martin Jambor wrote:
>> I'm afraid I cannot give an opinion what you should do in this case
>> without understanding the problem better. If you can isolate the case
>> where noclone behaves weirdly into a
On 12/19, Daniel Vetter wrote:
> 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
On Tue, Dec 04, 2018 at 03:03:40PM +, Vokáč Michal wrote:
> There was a bug in reset signal generation in ssd1307fb OLED driver.
> The display needs an active-low reset signal but the driver produced
> the correct sequence only if the GPIO used for reset was specified as
> GPIO_ACTIVE_HIGH.
>
On an OLPC XO 1.75 machine, the "security processor" handles the GPIO 71
and 72 interrupts. Don't reset the "route to SP" bit (4).
I'm just assuming the bit 4 is the "route to SP" bit -- it fixes the
SP-based keyboard for me and defines
ICU_INT_ROUTE_SP_IRQ to be 1 << 4. When asked for a data
On 12/18/18 9:56 PM, Yang Shi wrote:
>
>
> On 12/18/18 4:16 PM, Tim Chen wrote:
>> On 12/18/18 3:43 PM, Yang Shi wrote:
>>>
>>> On 12/18/18 11:29 AM, Tim Chen wrote:
On 12/17/18 10:52 PM, Yang Shi wrote:
> diff --git a/mm/swap_state.c b/mm/swap_state.c
> index fd2f21e..7cc3c29
On 19.12.18 14:46, Frieder Schrempf wrote:
> 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
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 anyone has any issues with these being applied, please
> let me
On Wed, Dec 19, 2018 at 05:48:17PM +0100, Wolfram Sang wrote:
> +static inline void i2c_mark_adapter_suspended(struct i2c_adapter *adap)
> +{
> + i2c_lock_bus(adap, I2C_LOCK_ROOT_ADAPTER);
> + set_bit(I2C_ALF_IS_SUSPENDED, >locked_flags);
> + i2c_unlock_bus(adap,
On Wed, Dec 19, 2018 at 05:58:53PM +0100, Jiri Kosina wrote:
> On Wed, 19 Dec 2018, Josh Poimboeuf wrote:
>
> > This option only makes sense for source-based patch generation, so isn't
> > it a bit premature to make this change without proper source-based patch
> > tooling?
>
> The reality is
Added documentation for audio formatter IP core DT bindings.
Signed-off-by: Maruthi Srinivas Bayyavarapu
---
.../bindings/sound/xlnx,audio-formatter.txt| 29 ++
1 file changed, 29 insertions(+)
create mode 100644
The audio formatter PL IP supports DMA of two streams -
mm2s and s2mm for playback and capture respectively. Apart from
DMA, IP also does conversions like PCM to AES and viceversa.
This patch adds DMA component driver for the IP.
Signed-off-by: Maruthi Srinivas Bayyavarapu
---
Enable audio formatter driver build.
Signed-off-by: Maruthi Srinivas Bayyavarapu
---
sound/soc/xilinx/Kconfig | 7 +++
sound/soc/xilinx/Makefile | 2 ++
2 files changed, 9 insertions(+)
diff --git a/sound/soc/xilinx/Kconfig b/sound/soc/xilinx/Kconfig
index 723a583..ac48d6a 100644
---
On Mon, Dec 03, 2018 at 12:47:48PM +0100, Lubomir Rintel wrote:
> A trivial one, but it's annoying that copy & paste of the link
> doesn't work.
>
> Signed-off-by: Lubomir Rintel
> ---
> Documentation/devicetree/bindings/clock/marvell,mmp2.txt | 2 +-
> 1 file changed, 1 insertion(+), 1
Audio formatter IP supports two streaming interfaces - MM2S for playback
and S2MM for capture. The driver enables DMA functionality for both the
interfaces.
Patchset includes devicetree bindings documentation, driver and build
enablement.
Maruthi Srinivas Bayyavarapu (3):
dt-bindings: ASoC:
* Mark Brown [181219 17:07]:
> On Wed, Dec 19, 2018 at 04:48:52PM +0100, David Lechner wrote:
> > On 12/19/18 4:43 PM, Roger Quadros wrote:
>
> > > Did I do something wrong or we just need to enhance regmap_debugfs.c?
>
> > Do you assign the name field in pru_regmap_config and
> >
On Mon, Dec 03, 2018 at 12:47:10PM +0100, Lubomir Rintel wrote:
> s/whold/whole/.
>
> Signed-off-by: Lubomir Rintel
> ---
> .../devicetree/bindings/interrupt-controller/mrvl,intc.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
Hi Linus,
Please pull dlm updates from tag:
git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-4.21
This set is entirely trivial fixes, mainly around correct cleanup
on error paths and improved error checks. One patch adds scheduling
in a potentially long recovery loop.
On Mon, Dec 03, 2018 at 03:45:45PM +0530, Jagan Teki wrote:
> GT5663 is capacitive touch controller with customized smart wakeup gestures,
> the existing goodix driver will work by phandle vcc-supply regulator.
>
> So, document compatible and example node for the same.
>
> Signed-off-by: Jagan
If palmas_smps_read() fails, we should not use the read data in "reg"
which may contain random value. The fix inserts a check for the return
value of palmas_smps_read(): If it fails, we return the error code
upstream and stop using "reg".
Signed-off-by: Kangjie Lu
---
On Wed, Dec 19, 2018 at 4:59 PM Matt Turner wrote:
> On Fri, Dec 14, 2018 at 10:18 AM Firoz Khan wrote:
> > On Tue, 13 Nov 2018 at 15:02, Firoz Khan wrote:
> >
> > Could someone review this patch series and queue it for 4.21
> > through alpha tree would be great.
>
> Thank you! I'll take a
On Wed, Dec 19, 2018 at 04:48:52PM +0100, David Lechner wrote:
> On 12/19/18 4:43 PM, Roger Quadros wrote:
> > Did I do something wrong or we just need to enhance regmap_debugfs.c?
> Do you assign the name field in pru_regmap_config and
> pru_debug_regmap_config?
Yeah, you'll at least need to
The mvpp2_phylink_validate() sets all modes that are supported by a
given PPv2 port. An mistake made the 1baseT_Full mode being
advertised in some cases when a port wasn't configured to perform at
10G. This patch fixes this.
Fixes: d97c9f4ab000 ("net: mvpp2: 1000baseX support")
Reported-by:
Hi Vineet,
Just curious: isn't that enough to use GFP_NOWAIT instead
of GFP_KERNEL when we allocate page in show_regs()?
As I can see x86 use print_vma_addr() in their show_signal_msg()
function which allocate page with __get_free_page(GFP_NOWAIT);
On Tue, 2018-12-18 at 10:53 -0800, Vineet
Hi Ard,
On 14/12/2018 16:40, Julien Thierry wrote:
>
>
> On 14/12/2018 15:49, Ard Biesheuvel wrote:
>> On Fri, 14 Dec 2018 at 16:23, Julien Thierry wrote:
>>>
>>> Hi,
>>>
>>> On 13/12/2018 15:03, Julien Thierry wrote:
Argh, not as simple as I had expected.
Turns out
FYI, I've picked this up for dma-mapping for-next now.
On Wed, 19 Dec 2018, Josh Poimboeuf wrote:
> This option only makes sense for source-based patch generation, so isn't
> it a bit premature to make this change without proper source-based patch
> tooling?
The reality is though that before the full-fledged patch tooling exists,
people are
On Thu, Dec 06, 2018 at 08:07:40PM +, Christophe Leroy wrote:
> checkpatch.pl reports the following:
>
> WARNING: struct kgdb_arch should normally be const
> #28: FILE: arch/mips/kernel/kgdb.c:397:
> +struct kgdb_arch arch_kgdb_ops = {
>
> This report makes sense, as all other ops
On Thu, Dec 06, 2018 at 08:07:38PM +, Christophe Leroy wrote:
> MIPS is the only architecture modifying arch_kgdb_ops during init.
> This patch makes the init static, so that it can be changed to
> const in following patch, as recommended by checkpatch.pl
>
> Suggested-by: Paul Burton
>
On Wed, Dec 19, 2018 at 12:35:40PM +0100, Jan Kara wrote:
> On Wed 19-12-18 21:28:25, Dave Chinner wrote:
> > On Tue, Dec 18, 2018 at 08:03:29PM -0700, Jason Gunthorpe wrote:
> > > On Wed, Dec 19, 2018 at 10:42:54AM +1100, Dave Chinner wrote:
> > >
> > > > Essentially, what we are talking about
On Tue, Dec 04, 2018 at 07:38:27PM -0800, Douglas Anderson wrote:
> If we're using the default implementation of kgdb_roundup_cpus() that
> uses smp_call_function_single_async() we can end up hanging
> kgdb_roundup_cpus() if we try to round up a CPU that failed to round
> up before.
>
>
On Tue, Dec 04, 2018 at 07:38:28PM -0800, Douglas Anderson wrote:
> If you have a CPU that fails to round up and then run 'btc' you'll end
> up crashing in kdb becaue we dereferenced NULL. Let's add a check.
> It's wise to also set the task to NULL when leaving the debugger so
> that if we fail
On Tue, Dec 04, 2018 at 07:38:26PM -0800, Douglas Anderson wrote:
> When I had lockdep turned on and dropped into kgdb I got a nice splat
> on my system. Specifically it hit:
> DEBUG_LOCKS_WARN_ON(current->hardirq_context)
>
> Specifically it looked like this:
> sysrq: SysRq : DEBUG
>
From: Peter Zijlstra
intel_pmu_cpu_prepare() allocated memory for ->shared_regs among other
members of struct cpu_hw_events. This memory is released in
intel_pmu_cpu_dying() which is wrong. The counterpart of the
intel_pmu_cpu_prepare() callback is x86_pmu_dead_cpu().
Otherwise if the CPU fails
On Tue, Dec 04, 2018 at 07:38:25PM -0800, Douglas Anderson wrote:
> The function kgdb_roundup_cpus() was passed a parameter that was
> documented as:
>
> > the flags that will be used when restoring the interrupts. There is
> > local_irq_save() call before kgdb_roundup_cpus().
>
> Nobody used
On Wed, Dec 19, 2018 at 03:17:44PM +0100, Miroslav Benes wrote:
> 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
On Mon, 2018-12-17 at 23:34 -0800, Doug Smythies wrote:
> This script is supposed to be allowed to run with regular user
> privileges
> if a previously captured trace is being post processed.
>
> Commit fbe313884d7ddd73ce457473cbdf3763f5b1d3da
> tools/power/x86/intel_pstate_tracer: Free the trace
On Wed, 19 Dec 2018 at 16:54, Valentin Schneider
wrote:
>
> On 19/12/2018 13:29, Vincent Guittot wrote:
> [...]
> >> My point is that AFAICT the LBF_ALL_PINNED flag would cover all the cases
> >> we care about, although the one you're mentioning is the only one I can
> >> think of. In that case
On Wed, 19 Dec 2018 at 17:36, Ulf Hansson wrote:
>
> On Wed, 19 Dec 2018 at 14:26, Vincent Guittot
> wrote:
> >
> > 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
From: Lenny Szubowicz
In __ghes_panic() clear the block status in the APEI generic
error status block for that generic hardware error source before
calling panic() to prevent a second panic() in the crash kernel
for exactly the same fatal error.
Otherwise ghes_probe(), running in the crash
Finally, here is the implementation Hans and I agreed on. Plus, all potential
users I could spot already converted. Renesas R-Car driver was added on top.
This series was tested on a Renesas Lager board (R-Car H2). I had to hack some
error cases into the code to verify the workings. Thanks for all
Rejecting transfers should be handled by the core.
Signed-off-by: Wolfram Sang
Reviewed-by: Kamal Dasu
---
drivers/i2c/busses/i2c-brcmstb.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/i2c/busses/i2c-brcmstb.c b/drivers/i2c/busses/i2c-brcmstb.c
Using the new 'is_suspended' flag, we now reject new transfers if the
adapter is already marked suspended.
Signed-off-by: Wolfram Sang
---
Documentation/i2c/fault-codes | 4
drivers/i2c/i2c-core-base.c | 2 ++
2 files changed, 6 insertions(+)
diff --git a/Documentation/i2c/fault-codes
Rejecting transfers should be handled by the core. Also, this will
ensure proper locking which was forgotten in this open coded version
and make sure resume mark is set after enabling clocks (not before).
Signed-off-by: Wolfram Sang
Acked-by: Shawn Guo
---
drivers/i2c/busses/i2c-zx2967.c | 8
Rejecting transfers should be handled by the core.
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-sprd.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/drivers/i2c/busses/i2c-sprd.c b/drivers/i2c/busses/i2c-sprd.c
index e266d8a713d9..961123529678
The pointer to a device is usually named 'dev'. These 'pdev' here look
much like copy errors. Fix them to avoid confusion.
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-sprd.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git
Hi Linus,
The following 3 patches fix a regression in the NFS/RPC TPC re-
connection code which can cause the RPC transmission to hang. The issue
was discovered by Dave Wysochanski last week.
With this pull, we still have one more regression to fix. MIPS is
seeing data corruption due to the fact
Rejecting transfers should be handled by the core. Also, this will
ensure proper locking which was forgotten in this open coded version.
Signed-off-by: Wolfram Sang
Tested-by: Marek Szyprowski
---
drivers/i2c/busses/i2c-s3c2410.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
A few drivers open code handling of suspended adapters. It could be
handled by the core, though, to ensure generic handling. This patch adds
the flag and accessor functions. The usage of these helpers is optional,
though. See the kerneldoc in this patch.
Signed-off-by: Wolfram Sang
---
Hi David,
On Wed, Dec 19, 2018 at 08:34:18AM -0800, David Miller wrote:
> From: Antoine Tenart
> Date: Wed, 19 Dec 2018 09:26:09 +0100
> >
> > The patch 2/2 ("net: mvpp2: fix the phylink mode validation") is still
> > relevant, in addition to the patch you applied. It was added in v3, and
> >
Because the adapter will be set up before every transaction anyhow, we
just need to mark it as suspended to the I2C core.
Signed-off-by: Hiromitsu Yamasaki
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-rcar.c | 25 +
1 file changed, 25 insertions(+)
diff --git
Rejecting transfers should be handled by the core. Also, this will
ensure proper locking which was forgotten in this open coded version.
Signed-off-by: Wolfram Sang
Tested-by: Marek Szyprowski
---
drivers/i2c/busses/i2c-exynos5.c | 11 ++-
1 file changed, 2 insertions(+), 9
This flag was defined and checked but never set a value. Remove it.
Signed-off-by: Wolfram Sang
Acked-by: Ard Biesheuvel
---
drivers/i2c/busses/i2c-synquacer.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/i2c/busses/i2c-synquacer.c
b/drivers/i2c/busses/i2c-synquacer.c
index
Hi Marek,
Marek Behún wrote on Wed, 19 Dec 2018 16:28:35
+0100:
> Hi,
>
> One thing for which I would like to be able to disable comphy is that
> each consumes about 100mW of power. On Turris Mox we configure the
> comphys to SGMII1, PCIe and USB3 modes. If there is no USB device
> plugged,
On Fri, Jul 20, 2018 at 11:50:16AM +0100, Daniel Thompson wrote:
> On Fri, Jul 20, 2018 at 11:23:37AM +0200, Nicholas Mc Guire wrote:
> > defcmd_in_progress is the state trace for command group processing
> > - within a command group or not - usable is an indicator if a command
> > set is
On 12/19/18 7:16 AM, Masahiro Yamada wrote:
> Could you pick this up to your arc tree?
Done, will push it in a day or so !
Thx,
-Vineet
[cc +kvm, +lkml]
Ditto list cc comment from 18/20, and doubly so on this with updates to
the vfio uapi. Also comment below...
On Wed, 19 Dec 2018 19:52:32 +1100
Alexey Kardashevskiy wrote:
> POWER9 Witherspoon machines come with 4 or 6 V100 GPUs which are not
> pluggable PCIe devices but
[cc +kvm, +lkml]
Sorry, just noticed these are only visible on ppc lists or for those
directly cc'd. vfio's official development list is the kvm list. I'll
let spapr specific changes get away without copying this list, but
changes like this really need to be visible to everyone. Thanks,
Alex
[cc +kvm, +lkml]
Ditto list cc comment from 18/20
On Wed, 19 Dec 2018 19:52:31 +1100
Alexey Kardashevskiy wrote:
> VFIO regions already support region capabilities with a limited set of
> fields. However the subdriver might have to report to the userspace
> additional bits.
>
> This adds an
Currently macvlan has single per-port queue for broadcast and multicast.
This disrupts order of packets when flows from different cpus are mixed.
This patch replaces this queue with single set of per-cpu queues.
Pointer to macvlan port is passed in skb control block.
Signed-off-by: Konstantin
On 12/19, Jani Nikula wrote:
> 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.
From: Kalle Valo
Date: Wed, 19 Dec 2018 16:34:02 +0200
> this a pull request to net tree for 4.20, more info below.
>
> Really sorry for sending a late request like this but I have been busy
> with other stuff and this just got delayed. These are pretty
> important fixes so I hope there's still
On Wed, 19 Dec 2018 12:32:41 +0100
Claudio wrote:
> >>
> >> I would imagine the core functionality is already available, since
> >> trace_pipe
> >> in the tracing directory already shows all events regardless of CPU, and so
> >> it would be a matter of doing the same for trace_pipe_raw.
> >
On Wed, 19 Dec 2018 at 14:26, Vincent Guittot
wrote:
>
> 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
From: Antoine Tenart
Date: Wed, 19 Dec 2018 09:26:09 +0100
> Hi David,
>
> On Tue, Dec 18, 2018 at 04:42:52PM -0800, David Miller wrote:
>> From: Antoine Tenart
>> Date: Mon, 17 Dec 2018 15:56:04 +0100
>>
>> > This small series introduces 2 fixes for the phylink validate function
>> > of the
On Wed, Dec 19, 2018 at 10:39:05AM +0100, Geert Uytterhoeven wrote:
> Hi Wolfram,
>
> On Wed, Dec 19, 2018 at 12:34 AM Wolfram Sang wrote:
> > > > + unsigned int is_suspended:1;/* owned by the I2C core */
> > >
> > > When more stuff is added to this bit field (which always happens at
> > >
From: Colin Ian King
Currently the cmd.read_write setting is not initialized so it contains
garbage from the stack. Fix this by setting it to 0 to indicate a
read is required.
Detected by CoverityScan, CID#1357925 ("Uninitialized scalar variable")
Fixes: c5c77ba18ea6 ("staging: wilc1000: Add
On Tue, Dec 18, 2018 at 02:20:10PM +0530, Anup Patel wrote:
> Actually these functions should not be inline because plic_toggle() uses
> raw_spin_lock() and plic_irq_toggle() uses for-loop.
So? It still inlines the all of two instances into each caller
for slightly different but related work.
> > Am 18.12.18 um 15:27 schrieb Jian-Hong Pan:
> > >> Sun, Dec 16, 2018 at 11:18:59AM CET, starni...@g.ncu.edu.tw wrote:
> > >>> LoRaWAN defined by LoRa Alliance(TM) is the MAC layer over LoRa
> > devices.
> > >>>
> > >>> This patch implements part of Class A end-devices SoftMAC defined in
> >
Introduce the bindings for the Texas Instruments LP5024 and the LP5018
RGB LED device driver. The LP5024/18 can control RGB LEDs individually
or as part of a control bank group. These devices have the ability
to adjust the mixing control for the RGB LEDs to obtain different colors
independent of
Hello
I am introducing the newest of the TI RGB parts the LP5024 and the LP5018.
Now I understand that there is a patchset in the works that changes the way
the LED labeling is created but I wanted to post these patches for comments and
let the maintainers decide whether to pull this in prior to
Introduce the LP5024 and LP5018 RGB LED driver.
The difference in these 2 parts are only in the number of
LED outputs where the LP5024 can control 24 LEDs the LP5018
can only control 18.
The device has the ability to group LED output into control banks
so that multiple LED banks can be controlled
On Wed, 19 Dec 2018 at 17:04, Paweł Chmiel
wrote:
>
> This commit adds node for Exynos Rorator device,
> so it can be used on all s5pv210 based devices.
>
> Signed-off-by: Paweł Chmiel
> ---
> arch/arm/boot/dts/s5pv210.dtsi | 9 +
> 1 file changed, 9 insertions(+)
Patch looks good but
Recent optimizations in MMU code broke nested SVM with NPT in L1
completely: when we do nested_svm_{,un}init_mmu_context() we want
to switch from TDP MMU to shadow MMU, both init_kvm_tdp_mmu() and
kvm_init_shadow_mmu() check if re-configuration is needed by looking
at cache source data. The data,
On Wed, Dec 19, 2018 at 07:17:04AM -0800, Christoph Hellwig wrote:
> On Wed, Dec 19, 2018 at 03:10:40PM +0530, Maruthi Srinivas Bayyavarapu wrote:
> > Changed License header from C to C++ style comment block.
> Why this completely pointless uglification that goes counter to
> the common style all
On Wed, 19 Dec 2018 at 17:04, Paweł Chmiel
wrote:
>
> This commit documents new compatible for s5pv210 soc,
> which will be also supported by this driver.
>
> Signed-off-by: Paweł Chmiel
> ---
> Documentation/devicetree/bindings/gpu/samsung-rotator.txt | 1 +
> 1 file changed, 1 insertion(+)
>
On Wed, Dec 19, 2018 at 9:28 PM Aruna Hewapathirane
wrote:
>
>
>>
>> I think, on my test machine, by default, there are many modules which
>> get added during boot up, which with vanilla kernel is not happening.
>> Thanks for your input.
>>
>> Regards,
>>
>> ~Praveen.
>>
>
> What does lsmod show
In setup_arch_memory we reserve the memory area wherein the kernel
is located. Current implementation may reserve more memory than
it actually required in case of CONFIG_LINUX_LINK_BASE is not
equal to CONFIG_LINUX_RAM_BASE. This happens because we calculate
start of the reserved region relatively
Den 19.12.2018 09.18, skrev Oleksandr Andrushchenko:
On 12/18/18 9:20 PM, Noralf Trønnes wrote:
Den 27.11.2018 11.32, skrev Oleksandr Andrushchenko:
From: Oleksandr Andrushchenko
When GEM backing storage is allocated with drm_gem_get_pages
the backing pages may be cached, thus making it
Hi Gustavo,
On 19/12/2018 15:11, Gustavo A. R. Silva wrote:
> Hi Marc,
>
> This is wrong: commit 6022fcc0e87a0eb5e9a72b15ed70dd29ebcb7343
>
> The above is not my original patch and it should not be tagged for stable,
> as it introduces the same kind of bug I intended to fix:
>
>
On Tue, Dec 18, 2018 at 10:55:31AM +0100, Vlastimil Babka wrote:
> On 12/15/18 12:03 AM, Mel Gorman wrote:
> > release_pages() is a simpler version of free_unref_page_list() but it
> > tracks the highest PFN for caching the restart point of the compaction
> > free scanner. This patch optionally
Hello Linus,
Here is the MTD PR for 4.21 coming a bit earlier than usual (hope this
is not a problem).
Regards,
Boris
The following changes since commit 2595646791c319cadfdbf271563aac97d0843dc7:
Linux 4.20-rc5 (2018-12-02 15:07:55 -0800)
are available in the Git repository at:
This commit adds node for Exynos Rorator device,
so it can be used on all s5pv210 based devices.
Signed-off-by: Paweł Chmiel
---
arch/arm/boot/dts/s5pv210.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/s5pv210.dtsi b/arch/arm/boot/dts/s5pv210.dtsi
index
This commit documents new compatible for s5pv210 soc,
which will be also supported by this driver.
Signed-off-by: Paweł Chmiel
---
Documentation/devicetree/bindings/gpu/samsung-rotator.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
This patchset adds support for s5pv210 soc, into
Samsung DRM Rotator driver. Currently only NV12 and XRGB formats
are supported.
It was tested by using simple tool from
https://www.spinics.net/lists/linux-samsung-soc/msg60498.html
Paweł Chmiel (3):
drm/exynos: rotator: Add support for
This commit adds support for s5pv210.
Currently only NV12 and XRGB formats are supported.
It was tested by using tool from
https://www.spinics.net/lists/linux-samsung-soc/msg60498.html
Signed-off-by: Paweł Chmiel
---
drivers/gpu/drm/exynos/exynos_drm_rotator.c | 23 +
1
On Wed, 19 Dec 2018, Paul Elder wrote:
> A usb gadget function driver may or may not want to delay the status
> stage of a control OUT request. An instance it might want to is to
-^
Typo: missing "where"
> asynchronously validate the data of a
On Mon, Dec 03, 2018 at 06:11:35PM +0800, Chen-Yu Tsai wrote:
> On Mon, Dec 3, 2018 at 6:08 PM Jagan Teki wrote:
> >
> > Most of the Allwinner A64 CSI controllers are supply with
> > VCC-PE pin. which need to supply for some of the boards to
> > trigger the power.
> >
> > So, document the supply
On Fri, Dec 14, 2018 at 10:18 AM Firoz Khan wrote:
>
> Hi Folks,
>
> On Tue, 13 Nov 2018 at 15:02, Firoz Khan wrote:
> >
> > The purpose of this patch series is, we can easily
> > add/modify/delete system call table support by cha-
> > nging entry in syscall.tbl file instead of manually
> >
On Thu, Dec 06, 2018 at 04:43:33PM +0530, Jagan Teki wrote:
> On Mon, Dec 3, 2018 at 3:55 PM Chen-Yu Tsai wrote:
> >
> > On Mon, Dec 3, 2018 at 6:08 PM Jagan Teki
> > wrote:
> > >
> > > Amarula A64-Relic board by default bound with OV5640 camera,
> > > so add support for it with below pin
From: Luo Jiaxing
This patch create debugfs file for port register and add file operations.
Signed-off-by: Luo Jiaxing
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_main.c | 43 ++
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 55
Checkpatch highlights some style issues which need to be addressed.
Signed-off-by: Ben Whitten
---
drivers/net/lora/sx125x.c | 20 +--
drivers/net/lora/sx1301.c | 52 ++-
drivers/net/lora/sx1301.h | 7 +++---
3 files changed, 45 insertions(+), 34
From: Luo Jiaxing
This patch take snapshot for global regs, port regs, CQ, DQ, IOST, ITCT.
Then, Add code for snapshot trig and generate dump directory.
Signed-off-by: Luo Jiaxing
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas.h | 15 +++-
401 - 500 of 949 matches
Mail list logo
