On Fri, 18 Jan 2019 at 20:12, Vijay Khemka wrote:
>
> Hi Andrew,
> Thanks for this review, I will have a follow up patch for this return values.
Did you send a follow up patch to fix the return values?
Greg, is there any reason why you did not merge this one? 5.2 will
have device trees that
Return value directly without saving it in a variable and remove that
variable.
Issue suggested by Coccinelle.
Signed-off-by: Vatsala Narang
---
Changes in v2:
-Change subject line and log message
-Remove respective unused variable
drivers/staging/vc04_services/bcm2835-camera/bcm2835-camera.c
On 30-04-19 02:17, Stephen Boyd wrote:
> Quoting Mike Looijmans (2019-04-27 02:42:56)
>> On 27-04-19 02:44, Stephen Boyd wrote:
>>> Quoting Mike Looijmans (2019-04-25 23:51:15)
On 26-04-19 01:04, Stephen Boyd wrote:
>> +
>> +Optional properties:
>> +- silabs,pll-m-num,
On Tue, Apr 30, 2019 at 09:44:09AM -0700, Andy Lutomirski wrote:
> On Sat, Apr 27, 2019 at 10:47 PM Mike Rapoport wrote:
> >
> > On Fri, Apr 26, 2019 at 09:42:23AM +0200, Peter Zijlstra wrote:
> > > On Fri, Apr 26, 2019 at 12:45:52AM +0300, Mike Rapoport wrote:
> > > > If a system call runs in
--
Greetings
I wonder why you continue neglecting my emails. Please, acknowledge the
receipt of this message in reference to the subject above as I intend
to send to you the details of the project.
Sometimes, try to check your spam box because most of these
correspondences
fall out
If ',' is not found, kmem_cache_flags() calls strlen() to find the end
of line. We can do it in a single pass using strchrnul().
Signed-off-by: Yury Norov
---
mm/slub.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
index 4922a0394757..85f90370a293
On Thu, Apr 18, 2019 at 11:02:27AM +0200, Michal Hocko wrote:
On Wed 17-04-19 13:43:44, Yang Shi wrote:
[...]
And, I'm wondering whether this optimization is also suitable to general
NUMA balancing or not.
If there are convincing numbers then this should be a preferable way to
deal with it.
to v5.1-rc7]
[if your patch is applied to the wrong git tree, please drop us a note
to help improve the system]
url:
https://github.com/0day-ci/linux/commits/Matthias-Kaehlcke/Bluetooth-btqca-inject-command-complete-event-during-fw-download/20190430-125407
base:
https://git.kernel.org/pub
On Tue, Apr 30, 2019 at 4:39 PM Will Deacon wrote:
>
> On Tue, Apr 30, 2019 at 04:05:04PM +0530, Arun KS wrote:
> > __early_cpu_boot_status is of type long. Use quad
> > assembler directive to allocate proper size.
> >
> > Signed-off-by: Arun KS
> > ---
> > arch/arm64/kernel/head.S | 2 +-
> >
The Always On Subsystem (AOSS) Qualcomm Messaging Protocol (QMP) driver
is used to communicate with the AOSS for certain side-channel requests,
that are not available through the RPMh interface.
The communication is a very simple synchronous mechanism of messages
being written in message RAM and
Introduce a driver implementing Qualcomm Messaging Protocol (QMP) to
communicate with the Always On Subsystem (AOSS) and expose the low-power
states for the remoteprocs as a set of power-domains and the QDSS clock
as a clock.
Changes since v6:
- First couple of patches merged for v5.2
- Squashed
From: Sibi Sankar
This patch adds Q6V5 MSS remoteproc node for SDM845 SoCs.
Reviewed-by: Douglas Anderson
Signed-off-by: Sibi Sankar
Signed-off-by: Bjorn Andersson
---
Changes since v6:
- None
arch/arm64/boot/dts/qcom/sdm845.dtsi | 58
1 file changed, 58
The AOSS QMP provides a number of power domains, used for QDSS and
PIL, add the node for this.
Tested-by: Sibi Sankar
Reviewed-by: Sibi Sankar
Signed-off-by: Bjorn Andersson
---
Changes since v6:
- Added #clock-cells
arch/arm64/boot/dts/qcom/sdm845.dtsi | 10 ++
1 file changed, 10
Add binding for the QMP based side-channel communication mechanism to
the AOSS, which is used to control resources not exposed through the
RPMh interface.
Signed-off-by: Bjorn Andersson
---
Changes since v6:
- Added #clock-cells
.../bindings/soc/qcom/qcom,aoss-qmp.txt | 81
Introduce a driver implementing Qualcomm Messaging Protocol (QMP) to
communicate with the Always On Subsystem (AOSS) and expose the low-power states
for the remoteprocs as a set of power-domains and the QDSS clock as a clock.
Bjorn Andersson (3):
dt-bindings: soc: qcom: Add AOSS QMP binding
From: Len Brown
Syntax only, no functional or semantic change.
This routine matches packages, not die, so name it thus.
Signed-off-by: Len Brown
---
arch/x86/kernel/smpboot.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/smpboot.c
From: Zhang Rui
Syntax only, no functional or semantic change.
Simplify how the code to discover a package is called.
Rename find_package_by_id() to rapl_find_package_domain()
Signed-off-by: Zhang Rui
Signed-off-by: Len Brown
Acked-by: Rafael J. Wysocki
Cc: linux...@vger.kernel.org
---
From: Len Brown
topology_die_id(cpu) is a simple macro for use inside the kernel
to get the die_id associated with the given cpu.
Signed-off-by: Len Brown
---
arch/x86/include/asm/topology.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/include/asm/topology.h
From: Len Brown
topology_max_packages() is available to size resources to
cover all packages in the system.
But now we have multi-die/package systems, and some
resources are per-die.
Create topology_max_die_per_package(), for detecting
multi-die/package systems, and sizing any per-die
From: Zhang Rui
The RAPL domain "name" attribute contains "Package-N",
which is ambiguous on multi-die per-package systems.
Update the name to "package-X-die-Y" on those systems.
No change on systems without multi-die/package.
Update driver debug messages.
Signed-off-by: Zhang Rui
From: Kan Liang
RAPL becomes die-scope on Xeon Cascade Lake-AP. Perf RAPL driver needs
to support die-scope RAPL domain.
Use topology_logical_die_id() to replace topology_logical_package_id().
For previous platforms which doesn't have multi-die,
topology_logical_die_id() is identical as
From: Zhang Rui
Package temperature sensors are actually implemented in hardware per-die.
Update coretemp to be "die-aware", so it can expose mulitple sensors
per package, instead of just one. No change to single-die/package
systems.
Signed-off-by: Zhang Rui
Signed-off-by: Len Brown
From: Len Brown
Create CPU topology sysfs attributes: "core_cpus" and "core_cpus_list"
These attributes represent all of the logical CPUs that share the
same core.
These attriutes is synonymous with the existing "thread_siblings" and
"thread_siblings_list" attribute, which will be deprecated.
From: Len Brown
Define topology_logical_die_id() ala
existing topology_logical_package_id()
Tested-by: Zhang Rui
Signed-off-by: Len Brown
---
arch/x86/include/asm/processor.h | 1 +
arch/x86/include/asm/topology.h | 5
arch/x86/kernel/cpu/common.c | 1 +
From: Kan Liang
Uncore becomes die-scope on Xeon Cascade Lake-AP. Uncore driver needs to
support die-scope uncore units.
Use topology_logical_die_id() to replace topology_logical_package_id().
For previous platforms which doesn't have multi-die,
topology_logical_die_id() is identical as
From: Zhang Rui
RAPL "package" domains are actually implemented in hardware per-die.
Thus, the new multi-die/package systems have mulitple domains
within each physical package.
Update the intel_rapl driver to be "die aware" -- exporting multiple
domains within a single package, when present.
No
From: Zhang Rui
Package temperature sensors are actually implemented in hardware per-die.
Thus, the new multi-die/package systems sport mulitple package thermal
zones for each package.
Update the x86_pkg_temp_thermal to be "multi-die-aware", so it can
expose multiple zones per package, instead
From: Kan Liang
Some cstate counters becomes die-scope on Xeon Cascade Lake-AP. Perf
cstate driver needs to support die-scope cstate counters.
Use topology_die_cpumask() to replace topology_core_cpumask().
For previous platforms which doesn't have multi-die,
topology_die_cpumask() is identical
This patch series does 4 things.
1. Parse the new CPUID.1F leaf to discover multi-die/package topology
2. Export multi-die topology inside the kernel
3. Update 4 places (coretemp, pkgtemp, rapl, perf) that that need to know
the difference between die and package-scope MSR.
4. Export
From: Len Brown
Syntax only, no functional or semantic change.
reflect actual cpuinfo_x86 field name:
s/logical_id/logical_proc_id/
Signed-off-by: Len Brown
Cc: linux-...@vger.kernel.org
---
Documentation/x86/topology.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Len Brown
Some new systems have multiple software-visible die within each package.
Update Linux parsing of the Intel CPUID "Extended Topology Leaf"
to handle either CPUID.B, or the new CPUID.1F.
Add cpuinfo_x86.die_id and cpuinfo_x86.max_dies to store the result.
die_id will be non-zero
From: Len Brown
The existing sysfs cpu/topology/core_siblings (and core_siblings_list)
attributes are documented, implemented, and used by programs to
represent set of logical CPUs sharing the same package.
This makes sense if the next topology level above a core
is always a package. But on
While loading firmware blobs parallely in different threads, it is possible
to free sysfs node of glue_dirs in device_del() from a thread while another
thread is trying to add subdir from device_add() in glue_dirs sysfs node.
CPU1 CPU2
On Tue, Apr 30, 2019 at 8:43 PM Randy Dunlap wrote:
>
> Hi,
>
> On 4/30/19 8:34 PM, Andrey Smirnov wrote:
> > diff --git a/drivers/power/supply/Kconfig b/drivers/power/supply/Kconfig
> > index e901b9879e7e..c614c8a196f3 100644
> > --- a/drivers/power/supply/Kconfig
> > +++
> On Apr 30, 2019, at 5:13 PM, kbuild test robot wrote:
>
> tree:
>
On Tue, Apr 30, 2019 at 12:42 PM Viresh Kumar wrote:
>
> On 29-04-19, 11:18, Rob Herring wrote:
> > On Sun, Apr 28, 2019 at 4:53 AM Frank Lee wrote:
> > >
> > > On Sat, Apr 27, 2019 at 5:15 AM Rob Herring wrote:
> > > >
> > > > On Wed, Apr 10, 2019 at 01:41:39PM -0400, Yangtao Li wrote:
> > > >
On Tue 30 Apr 19:27 PDT 2019, Jeffrey Hugo wrote:
> Add MSM8998 Multimedia Clock Controller DT node.
>
> Signed-off-by: Jeffrey Hugo
Reviewed-by: Bjorn Andersson
(But same comment as earlier wrt clocks vs clock-names ordering)
Regards,
Bjorn
> ---
> arch/arm64/boot/dts/qcom/msm8998.dtsi |
Hi,
On 4/30/19 8:34 PM, Andrey Smirnov wrote:
> diff --git a/drivers/power/supply/Kconfig b/drivers/power/supply/Kconfig
> index e901b9879e7e..c614c8a196f3 100644
> --- a/drivers/power/supply/Kconfig
> +++ b/drivers/power/supply/Kconfig
> @@ -660,4 +660,13 @@ config FUEL_GAUGE_SC27XX
>Say
On Tue 30 Apr 19:27 PDT 2019, Jeffrey Hugo wrote:
> +static const struct of_device_id mmcc_msm8998_match_table[] = {
> + { .compatible = "qcom,mmcc-msm8998" },
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, mmcc_msm8998_match_table);
> +
> +static int mmcc_msm8998_probe(struct platform_device
Hi Dmitry,
Today's linux-next merge of the input tree got a conflict in:
Documentation/devicetree/bindings/vendor-prefixes.txt
between commit:
2c98d9e47533 ("dt-bindings: vendor-prefixes: add AZW")
from the arm-soc tree and commit:
7b5bb55d0dad ("Input: add support for Azoteq
On Tue, Apr 30, 2019 at 6:31 AM Thomas Backlund wrote:
>
>
> Den 30-04-2019 kl. 16:06, skrev Song Liu:
> > On Tue, Apr 30, 2019 at 12:55 AM Thomas Backlund wrote:
> >> Den 30-04-2019 kl. 10:26, skrev Thomas Backlund:
> >>> Building perf in 5.1-rc5/6/7 fails:
> >>>
> >>>
> >>> Build start:
> >>>
On Tue 30 Apr 19:26 PDT 2019, Jeffrey Hugo wrote:
> Document the multimedia clock controller found on MSM8998.
>
> Signed-off-by: Jeffrey Hugo
> Reviewed-by: Rob Herring
Reviewed-by: Bjorn Andersson
> ---
> .../devicetree/bindings/clock/qcom,mmcc.txt| 21 +++
>
On Tue 30 Apr 19:25 PDT 2019, Jeffrey Hugo wrote:
> GCC is a consumer of the xo clock. Add a reference to the clock supplier
> to the gcc node.
>
> Signed-off-by: Jeffrey Hugo
Reviewed-by: Bjorn Andersson
(Although I prefer clock-names following clocks)
Regards,
Bjorn
> ---
>
Add bindings for Microchip UCS1002 Programmable USB Port Power
Controller with Charger Emulation.
Signed-off-by: Andrey Smirnov
Reviewed-by: Rob Herring
Cc: Enric Balletbo Serra
Cc: Chris Healy
Cc: Lucas Stach
Cc: Fabio Estevam
Cc: Guenter Roeck
Cc: Sebastian Reichel
Cc:
Add driver for Microchip UCS1002 Programmable USB Port Power
Controller with Charger Emulation. The driver exposed a power supply
device to control/monitor various parameter of the device as well as a
regulator to allow controlling VBUS line.
Signed-off-by: Enric Balletbo Serra
Signed-off-by:
On Tue 30 Apr 19:24 PDT 2019, Jeffrey Hugo wrote:
> The global clock controller on MSM8998 can consume a number of external
> clocks. Document them.
>
> Signed-off-by: Jeffrey Hugo
> ---
> Documentation/devicetree/bindings/clock/qcom,gcc.txt | 10 ++
> 1 file changed, 10 insertions(+)
Everyone:
This small series adds a driver for UCS1002 Programmable USB Port
Power Controller with Charger Emulation. See [page] for product page
and [datasheet] for device dataseet. Hopefully each individual patch
is self explanatory.
Note that this series is a revival of the upstreaming effort
Add POWER_SUPPLY_HEALTH_OVERCURRENT constant in order to allow
singalling overcurrent condition via power supply health information.
Signed-off-by: Andrey Smirnov
Reviewed-by: Guenter Roeck
Cc: Enric Balletbo Serra
Cc: Chris Healy
Cc: Lucas Stach
Cc: Fabio Estevam
Cc: Guenter Roeck
Cc:
On Tue 30 Apr 19:26 PDT 2019, Jeffrey Hugo wrote:
> The XO clock generally feeds into other clock controllers as the parent
> for a lot of clock generators.
>
> Drop the "fake" XO clock in GCC now that it is redundant can will cause a
> namespace conflict.
>
> Signed-off-by: Jeffrey Hugo
> ---
On Mon, Apr 29, 2019 at 01:31:58PM -0400, Debabrata Banerjee wrote:
> Fixes:
> commit 1e381f60dad9 ("ext4: do not allow journal_opts for fs w/o journal")
>
> Instead of removing EXT4_MOUNT_JOURNAL_CHECKSUM from s_def_mount_opt as
> I assume was intended, all other options were blown away leading
Add MSM8998 Multimedia Clock Controller DT node.
Signed-off-by: Jeffrey Hugo
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi
b/arch/arm64/boot/dts/qcom/msm8998.dtsi
index 9c88801..5b63fa2 100644
Add a driver for the multimedia clock controller found on MSM8998
based devices. This should allow most multimedia device drivers
to probe and control their clocks.
Signed-off-by: Jeffrey Hugo
---
drivers/clk/qcom/Kconfig|9 +
drivers/clk/qcom/Makefile |1 +
Document the multimedia clock controller found on MSM8998.
Signed-off-by: Jeffrey Hugo
Reviewed-by: Rob Herring
---
.../devicetree/bindings/clock/qcom,mmcc.txt| 21 +++
include/dt-bindings/clock/qcom,mmcc-msm8998.h | 210 +
2 files changed, 231 insertions(+)
Eric Wong wrote:
> Deepa Dinamani wrote:
> > I'm not sure what the hang in the userspace is about. Is it because
> > the syscall did not return an error or the particular signal was
> > blocked etc.
>
> Uh, ok; that's less comforting.
Nevermind, I think I understand everything, now.
GCC is a consumer of the xo clock. Add a reference to the clock supplier
to the gcc node.
Signed-off-by: Jeffrey Hugo
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi
b/arch/arm64/boot/dts/qcom/msm8998.dtsi
The XO clock generally feeds into other clock controllers as the parent
for a lot of clock generators.
Drop the "fake" XO clock in GCC now that it is redundant can will cause a
namespace conflict.
Signed-off-by: Jeffrey Hugo
---
drivers/clk/qcom/clk-smd-rpm.c | 24
The global clock controller on MSM8998 can consume a number of external
clocks. Document them.
Signed-off-by: Jeffrey Hugo
---
Documentation/devicetree/bindings/clock/qcom,gcc.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git
The multimedia clock controller (mmcc) is the main clock controller for
the multimedia subsystem and is required to enable things like display and
camera.
v3:
-Rebase onto linux-next to get the final version of the clk parent rewrite
series
-Moved the bindings header to the bindings patch per Rob
Deepa Dinamani wrote:
> I was also not able to reproduce this.
> Arnd and I were talking about this today morning. Here is something
> Arnd noticed:
>
> If there was a signal after do_epoll_wait(), we never were not
> entering the if (err = -EINTR) at all before.
I'm not sure which `if'
On Tue, Apr 30, 2019 at 12:18:13PM -0600, Keith Busch wrote:
> On Tue, Apr 30, 2019 at 12:05:09PM -0600, Keith Busch wrote:
> > On Tue, Apr 30, 2019 at 11:11:51AM -0500, Bjorn Helgaas wrote:
> > > > I'm not convinced a revert is the best call.
> > >
> > > I have very limited options at this stage
On Tue, Apr 30, 2019 at 6:35 PM Steven Rostedt wrote:
>
>
> Probably easier to move it from inline asm to ftrace_X.S and use the
> lockdep TRACE_ON/OFF macros.
Yeah, that should clean up the percpu stuff too since we have helper
macros for it for *.S files anyway.
I only did the asm() in C
On Wed, May 01, 2019 at 08:06:07AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 60ae11086c04 ("unicode: update unicode database unicode version 12.1.0")
>
> is missing a Signed-off-by from its committer.
Oops, thanks for pointing this out. Will fix.
On Tue, Apr 30, 2019 at 05:00:43AM +0100, Al Viro wrote:
> Where would you put that synchronize_rcu()? Doing that before ->put_super()
> is too early - inode references might be dropped in there. OTOH, doing
> that after that point means that while struct super_block itself will be
> there, any
On Tue, 30 Apr 2019 17:53:34 -0400
Steven Rostedt wrote:
> + if (ftrace_location(ip)) {
> + /* A breakpoint at the beginning of the function was hit */
> + if (in_nmi()) {
> + /* NMIs have their own trampoline */
> +
Convert HiSilicon hi6xxx PMIC drivers to SPDX identifier.
Signed-off-by: Axel Lin
---
drivers/regulator/hi6421-regulator.c | 24 +-
drivers/regulator/hi6421v530-regulator.c | 26 ++--
drivers/regulator/hi655x-regulator.c | 22
Currently we parse user data byte after byte which leads to
overcomplicating of parsing algorithm. There are no performance
critical users of bitmap_parse_user(), and so we can duplicate
user data to kernel buffer and simply call bitmap_parselist().
This rework lets us unify and simplify
New design of inner bitmap_parse() allows to avoid
calculating the size of a null-terminated string.
Signed-off-by: Yury Norov
---
include/linux/cpumask.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/include/linux/cpumask.h b/include/linux/cpumask.h
index
New version of bitmap_parse() is unified with bitmap_parse_list(),
and therefore:
- weakens rules on whitespaces and commas between hex chunks;
- in addition to \0 allows using \n as the line ending symbol;
- allows passing UINT_MAX or any other big number as the length
of input string
bitmap_parse() is ineffective and full of opaque variables and opencoded
parts. It leads to hard understanding and usage of it. This rework
includes:
- remove bitmap_shift_left() call from the cycle. Now it makes the
complexity of the algorithm as O(nbits^2). In the suggested approach
the
On top of next-20190418.
Similarly to recently revisited bitmap_parselist() [1],
bitmap_parse() is ineffective and overcomplicated. This
series reworks it, aligns its interface with bitmap_parselist()
and makes usage simpler.
The series also adds a test for the function and fixes usage of it
in
Introduce BITS_TO_U64, BITS_TO_U32 and BITS_TO_BYTES as they are handy
in the following patches (BITS_TO_U32 specifically). Reimplement tools/
version of the macros according to the kernel implementation.
Also fix indentation for BITS_PER_TYPE definition.
Signed-off-by: Yury Norov
---
New function works like strchrnul() with a length limited strings.
Signed-off-by: Yury Norov
---
include/linux/string.h | 1 +
lib/string.c | 17 +
2 files changed, 18 insertions(+)
diff --git a/include/linux/string.h b/include/linux/string.h
index
The test is derived from bitmap_parselist()
NO_LEN is reserved for use in following patches.
Signed-off-by: Yury Norov
---
lib/test_bitmap.c | 94 ++-
1 file changed, 93 insertions(+), 1 deletion(-)
diff --git a/lib/test_bitmap.c b/lib/test_bitmap.c
On Tue, Apr 30, 2019 at 09:24:29PM +, Vadim Pasternak wrote:
>
>
> > -Original Message-
> > From: Asmaa Mnebhi
> > Sent: Tuesday, April 30, 2019 8:59 PM
> > To: miny...@acm.org; w...@the-dreams.de; Vadim Pasternak
> > ; Michael Shych
> > Cc: Asmaa Mnebhi ;
From: Kan Liang
IMC uncore unit can only be accessed via MMIO on Snow Ridge.
The MMIO space of IMC uncore is at the specified offsets from the
MEM0_BAR. Add snr_uncore_get_mc_dev() to locate the PCI device with
MMIO_BASE and MEM0_BAR register.
Add new ops to access the IMC registers via MMIO.
From: Kan Liang
The patch series intends to enable perf uncore support for Snow Ridge
server.
Here is the link for the uncore document.
https://cdrdv2.intel.com/v1/dl/getContent/611319
Patch 1: Fixes a generic issue for uncore free-running counter, which
also impacts the Snow Ridge server.
From: Kan Liang
A new MMIO type uncore box is introduced on Snow Ridge server. The
counters of MMIO type uncore box can only be accessed by MMIO.
Add a new uncore type, uncore_mmio_uncores, for MMIO type uncore blocks.
Support MMIO type uncore blocks in CPU hot plug. The MMIO space has to
be
From: Kan Liang
The client IMC block is accessed by MMIO. Current code uses an informal
way to access the block, which is not recommended.
Cleaning up the code by using __iomem annotation and the accessor
functions (read[lq]()).
Move exit_box() and read_counter() to generic code, which can be
From: Kan Liang
Counting with invalid event coding for free-running counter may cause
OOPs, e.g. uncore_iio_free_running_0/event=1/.
Current code only validate the event with free-running event format,
event=0xff,umask=0xXY. Non-free-running event format never be checked
for the PMU with
From: Kan Liang
For uncore box which can only be accessed by MSR, its reference
box->refcnt is updated in CPU hot plug. The uncore boxes needs to be
init/exit accordingly for the first/last CPU of a socket.
Starts from Snow Ridge server, a new type of uncore box is introduced,
which can only be
From: Kan Liang
The uncore subsystem on Snow Ridge is similar as previous SKX server.
The uncore units on Snow Ridge include Ubox, Chabox, IIO, IRP, M2PCIE,
PCU, M2M, PCIE3 and IMC.
- The config register encoding and pci device IDs are changed.
- For CHA, the umask_ext and filter_tid fields are
On Sun, Apr 28, 2019 at 07:57:45PM +0300, Andy Shevchenko wrote:
> On Sat, Apr 27, 2019 at 08:29:34PM -0700, Yury Norov wrote:
> > bitmap_parse() is ineffective and full of opaque variables and opencoded
> > parts. It leads to hard understanding of it. This rework includes:
> > - remove
On Thu, 25 Apr 2019 06:35:06 PDT (-0700), Anup Patel wrote:
The Linux kernel will auto-disables all boot consoles whenever it
gets a preferred real console.
Currently on RISC-V systems, if we have a real console which is not
RISCV SBI console then boot consoles (such as earlycon=sbi) are not
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/mm
head: 3950746d9d8ef981c1cb842384e0e86e8d1aad76
commit: c7b6f29b6257532792fc722b68fcc0e00b5a856c [14/35] bpf: Fail
bpf_probe_write_user() while mm is switched
config: s390-defconfig (attached as .config)
compiler:
On Thu, 25 Apr 2019 01:38:24 PDT (-0700), Anup Patel wrote:
This patch series adds support to access CSR using both CSR name and
CSR numbers.
Also, we should prefer accessing CSRs using their CSR numbers because:
1. It compiles fine with older toolchains.
2. We can use latest CSR names in
On 2019-04-30 14:44, Sodagudi Prasad wrote:
+Sudeep
Hi Mark/Will,
I would like to understand whether ARM linux community have plans to
support PSCI version 1.1 or not.
PSCI_1_1 specification introduced support for SYSTEM_RESET2 command
and this new command helps mobile devices to
Hi,
Looks like I've created a bit of confusion trying to fix memleaks in
calls to kobject_init_and_add(). Its spread over various patches and
mailing lists so I'm starting a new thread and CC'ing anyone that
commented on one of those patches.
If there is a better way to go about this discussion
On 4/30/19 3:32 PM, Rob Herring wrote:
On Tue, Apr 30, 2019 at 09:15:42AM -0700, Guenter Roeck wrote:
On Mon, Apr 29, 2019 at 11:45:57PM -0700, Andrey Smirnov wrote:
Add bindings for Microchip UCS1002 Programmable USB Port Power
Controller with Charger Emulation.
Signed-off-by: Andrey Smirnov
On Tue, Apr 30, 2019 at 12:16 AM Yinbo Zhu wrote:
>
> From: Yinbo Zhu
The patch title better to be "dt-bindings: mmc: ..."
>
> Add "fsl,ls1028a-esdhc" bindings for ls1028a eSDHC host controller
>
> Signed-off-by: Yinbo Zhu
> ---
> .../devicetree/bindings/mmc/fsl-esdhc.txt |1 +
>
On Tue, Apr 30, 2019 at 12:05:09PM -0600, Keith Busch wrote:
> On Tue, Apr 30, 2019 at 11:11:51AM -0500, Bjorn Helgaas wrote:
> > > I'm not convinced a revert is the best call.
> >
> > I have very limited options at this stage of the release, but I'd be
> > glad to hear suggestions. My concern
Hi Serge,
On Fri, Apr 26, 2019 at 03:00:36AM +0300, Serge Semin wrote:
> > 1) Older systems generally had something like an ISA bus which used
> > addresses below the kernel, and bootloaders like YAMON left behind
> > functions that could be called right at the start of RAM. This sort
>
On Thu, Apr 25, 2019 at 01:48:59AM +0300, Dmitry Osipenko wrote:
> Add new property that designates the PMIC as the system's power
> controller.
>
> Signed-off-by: Dmitry Osipenko
> ---
> Documentation/devicetree/bindings/mfd/max77620.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff
On Sun, Apr 28, 2019 at 09:40:00AM +1000, Tobin C. Harding wrote:
> Currently error return from kobject_init_and_add() is not followed by a
> call to kobject_put(). This means there is a memory leak.
>
> Add call to kobject_put() in error path of kobject_init_and_add().
>
> Signed-off-by: Tobin
On Thu, Apr 25, 2019 at 01:48:58AM +0300, Dmitry Osipenko wrote:
> Maxim 77663 has a few minor differences in regards to hardware interface
> and available capabilities by comparing it with 77620 and 20024 models,
> hence re-use 77620 device-tree binding for the 77663.
>
> Signed-off-by: Dmitry
During mdev parent registration in mdev_register_device(),
if parent device is duplicate, it releases the reference of existing
parent device.
This is incorrect. Existing parent device should not be touched.
Fixes: 7b96953bc640 ("vfio: Mediated device Core driver")
Reviewed-by: Cornelia Huck
Instead of masking return error to -EBUSY, return actual error
returned by the driver.
Reviewed-by: Cornelia Huck
Reviewed-by: Maxim Levitsky
Signed-off-by: Parav Pandit
---
drivers/vfio/mdev/mdev_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Remove unused kref from the mdev_device structure.
Fixes: 7b96953bc640 ("vfio: Mediated device Core driver")
Reviewed-by: Cornelia Huck
Reviewed By: Kirti Wankhede
Reviewed-by: Maxim Levitsky
Signed-off-by: Parav Pandit
---
drivers/vfio/mdev/mdev_core.c| 1 -
device_for_each_child() stops executing callback function for remaining
child devices, if callback hits an error.
Each child mdev device is independent of each other.
While unregistering parent device, mdev core must remove all child mdev
devices.
Therefore, mdev_device_remove_cb() always returns
On Mon, Apr 22, 2019 at 08:40:44AM +0200, Oleksij Rempel wrote:
> Add binding documentation for Atheros/QCA networking IP core used
> in many routers.
>
> Signed-off-by: Oleksij Rempel
> ---
> .../devicetree/bindings/net/qca,ar71xx.txt| 44 +++
> 1 file changed, 44
As section 15 of Documentation/process/coding-style.rst clearly
describes that compiler will be able to optimize code.
Hence drop inline for get and put helpers for parent.
Signed-off-by: Parav Pandit
---
drivers/vfio/mdev/mdev_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
1 - 100 of 972 matches
Mail list logo
