Nothing apart from only being used by arm64 platforms today, which is
circumstantial.
I understand you need to find a place to add the:
acpi_indirect_io_scan_init()
to be called from core ACPI code because ACPI can't handle probe
dependencies in any other way but other than that this patch is
On Wed, Feb 14, 2018 at 03:41:22PM -0600, Pierre-Louis Bossart wrote:
> On 02/14/2018 01:23 PM, kbuild test robot wrote:
> This was reported by Arnd Bergman and fixed with a patch sent on January 24
> to alsa-devel ("ASoC: Intel: atom: fix ACPI/PCI Kconfig"), but I don't see
> it in Mark's tree?
Hi Christian,
On Thu, Feb 15, 2018 at 12:14 PM, Christian Borntraeger
wrote:
> To enable the virtual terminal layer with virtio-gpu, we need to
> provide the dummy console. This console is hidden behind CONFIG_IOMEM
> via the graphics support. Instead of fully enabling the graphic
> drivers lets
On Tue 13-02-18 14:31:56, Pavel Tatashin wrote:
> Start qemu with the following arguments:
> -m 64G,slots=2,maxmem=66G -object memory-backend-ram,id=mem1,size=2G
>
> Which: boots machine with 64G, and adds a device mem1 with 2G which can be
> hotplugged later.
>
> Also make sure that config has t
On Tue 13-02-18 14:31:57, Pavel Tatashin wrote:
> Memory sections are combined into "memory block" chunks. These chunks are
> the units upon which memory can be added and removed.
>
> On x86, the new memory may be added after the end of the boot memory,
> therefore, if block size does not align wi
On Thu, Feb 15, 2018 at 12:19 PM, John Garry wrote:
>> Nothing apart from only being used by arm64 platforms today, which is
>> circumstantial.
>>
>>>
>>> I understand you need to find a place to add the:
>>>
>>> acpi_indirect_io_scan_init()
>>>
>>> to be called from core ACPI code because ACPI ca
On Wed, Feb 14, 2018 at 06:53:44PM +, Mathieu Desnoyers wrote:
> However, given the scenario involves multiples CPUs (one doing exit_mm(),
> the other doing context switch), the actual order of perceived load/store
> can be shuffled. And AFAIU nothing prevents the CPU from ordering the
> atomic
On Thu, Feb 15, 2018 at 10:39:41AM +0100, Geert Uytterhoeven wrote:
> On Wed, Feb 14, 2018 at 5:28 PM, Mark Brown wrote:
> > Signed-off-by: Harald Geyer
> > Acked-by: Rob Herring
> > Signed-off-by: Mark Brown
> What about using the DT node name instead, as is done for single-output
> clocks?
On Tue 13-02-18 14:31:58, Pavel Tatashin wrote:
> During boot we poison struct page memory in order to ensure that no one is
> accessing this memory until the struct pages are initialized in
> __init_single_page().
>
> This patch adds more scrutiny to this checking, by making sure that flags
> do
On 15/02/2018 11:12, Jerome Brunet wrote:
> add the secure AO system controller with chipid enabled
>
> Signed-off-by: Jerome Brunet
> ---
> arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
> b/
On 15/02/2018 11:10, Jerome Brunet wrote:
> The compatible in pwm_AO_cd is wrong and does not match anything.
> Correct this with the correct compatible string
>
> Fixes: 4a81e5ddfb43 ("ARM64: dts: meson-axg: add PWM DT info for Meson-Axg
> SoC")
> Signed-off-by: Jerome Brunet
> ---
> arch/arm6
On 04/12/2017 06:38, Yixun Lan wrote:
> Enable IR remote controller which find in Amlogic's Meson-AXG SoC.
>
> Signed-off-by: Yixun Lan
>
> ---
>
> Changes since v1 at [1]:
> - drop the compatbile 'amlogic,meson-gx-ir'
>
> [1]
> http://lists.infradead.org/pipermail/linux-amlogic/2017-Novembe
On 02/15/2018 12:26 PM, Geert Uytterhoeven wrote:
> Hi Christian,
>
> On Thu, Feb 15, 2018 at 12:14 PM, Christian Borntraeger
> wrote:
>> To enable the virtual terminal layer with virtio-gpu, we need to
>> provide the dummy console. This console is hidden behind CONFIG_IOMEM
>> via the graphics s
On 15.02.2018 12:26, Geert Uytterhoeven wrote:
> Hi Christian,
>
> On Thu, Feb 15, 2018 at 12:14 PM, Christian Borntraeger
> wrote:
>> To enable the virtual terminal layer with virtio-gpu, we need to
>> provide the dummy console. This console is hidden behind CONFIG_IOMEM
>> via the graphics supp
On 2018-02-15 10:57, Philipp Hahn wrote:
> Hello,
>
> Am 15.02.2018 um 03:28 schrieb Richard Guy Briggs:
> > Fix handlink to hardlink.
>
> and introduce a new sp*el*ling error in the subject line ;-)
That one was quite intentional for ironic effect. I could have added an
extra "e" for exaggerat
On 02/15/2018 12:57 PM, Thomas Huth wrote:
> On 15.02.2018 12:26, Geert Uytterhoeven wrote:
>> Hi Christian,
>>
>> On Thu, Feb 15, 2018 at 12:14 PM, Christian Borntraeger
>> wrote:
>>> To enable the virtual terminal layer with virtio-gpu, we need to
>>> provide the dummy console. This console is
On Thu, Jan 25, 2018 at 03:21:44PM +0800, Aaron Lu wrote:
> When freeing a batch of pages from Per-CPU-Pages(PCP) back to buddy,
> the zone->lock is held and then pages are chosen from PCP's migratetype
> list. While there is actually no need to do this 'choose part' under
> lock since it's PCP pag
This patch introduces sysfs entries that will provide read-only access to
device management data that could be received with UFS query requests.
User-space applications will be able to read UFS device descriptors,
flags and attributes. This will allow to get full UFS device configuration
and its st
This patch introduces attribute group to show existing sysfs entries.
Signed-off-by: Stanislav Nijnikov
Reviewed-by: Greg Kroah-Hartman
---
drivers/scsi/ufs/Makefile| 3 +-
drivers/scsi/ufs/ufs-sysfs.c | 156 +++
drivers/scsi/ufs/ufs-sysfs.h | 14 +
This patch introduces a sysfs group entry for the UFS interconnect
descriptor parameters. The group adds "interconnect_descriptor" folder
under the UFS driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*).
The parameters are shown as hexadecimal numbers. The full information
about the parameters
The patch introduces an additional field in the scsi_host_template
structure - struct attribute_group **sdev_group.
This field allows to define groups of attributes. It will provide an
ability to use binary attributes as well as device attributes and
to group them under subfolders if necessary.
Si
This patch introduces a sysfs group entry for the UFS flags. The group adds
"flags" folder under the UFS driver sysfs entry
(/sys/bus/platform/drivers/ufshcd/*). The flags are shown as boolean value
("true" or "false"). The full information about the UFS flags could be
found at UFS specifications 2
This patch introduces a sysfs group entry for the UFS health descriptor
parameters. The group adds "health_descriptor" folder under the UFS driver
sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The parameters are shown
as hexadecimal numbers. The full information about the parameters could be
fo
On Thu, Feb 15, 2018 at 11:39 AM, Andrzej Hajda wrote:
> OF graph describes MHL data lanes between MHL and respective USB
> connector.
>
> Signed-off-by: Andrzej Hajda
> ---
> .../boot/dts/exynos/exynos5433-tm2-common.dtsi | 31
> +++---
> 1 file changed, 28 insertions(+), 3
This patch introduces a sysfs group entry for the UFS attributes. The
group adds "attributes" folder under the UFS driver sysfs entry
(/sys/bus/platform/drivers/ufshcd/*). The attributes are shown
as hexadecimal numbers. The full information about the attributes could
be found at UFS specifications
This patch introduces a sysfs group entry for the UFS string descriptors.
The group adds "string_descriptors" folder under the UFS driver
sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The folder will contain
5 files that will show string values defined by the UFS spec:
a manufacturer name, a pr
This patch introduces a sysfs group entry for the UFS unit descriptor
parameters. The group adds "unit_descriptor" folder under the corresponding
SCSI device sysfs entry (/sys/class/scsi_device/*/device/). The parameters
are shown as hexadecimal numbers. The full information about the parameters
co
This patch introduces a sysfs group entry for the UFS geometry descriptor
parameters. The group adds "geometry_descriptor" folder under the UFS
driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The parameters
are shown as hexadecimal numbers. The full information about the parameters
could b
This patch introduces a sysfs group entry for the UFS device descriptor
parameters. The group adds "device_descriptor" folder under the UFS driver
sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The parameters are shown
as hexadecimal numbers. The full information about the parameters could be
fo
This patch introduces a sysfs group entry for the UFS power descriptor
parameters. The group adds "power_descriptor" folder under the UFS driver
sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The parameters are shown
as hexadecimal numbers. The full information about the parameters could be
foun
On Thu, Feb 15, 2018 at 1:19 PM, John Garry wrote:
> +static const struct acpi_device_id indirect_io_hosts[] = {
> +{"HISI0191", 0},/* HiSilicon LPC host */
> +{},
Just a nit.
It seems lately this happens more often than usual, I mean a comma in
the terminator line.
If we remove it
From: Markus Elfring
Date: Thu, 15 Feb 2018 11:38:30 +0100
Omit extra messages for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/crypto/atmel-aes.c | 6 +-
drivers/crypto/atmel-sha.c |
The symbol search called by machine__find_kernel_symbol_by_name
is using internally arch__compare_symbol_names function to compare
2 symbol names, because different archs have different ways of
comparing symbols. Mostly for skipping '.' prefixes and similar.
In test 1 when we try to find matching
hi,
sending assorted general fixes that queued
up in my other branches.
v3 changes:
- reworked machine__create_kernel_maps to take into account
kernel modules based on Namhyung's comments
- fixed dso__load changes to take into account namespace switch
- add perf test 1 fix
v2 changes:
And replacing it with __machine__load_kallsyms function.
The current machine__load_kallsyms function has no caller,
so replacing it directly with __machine__load_kallsyms.
Also removing the no_kcore argument as it was always called
with true value.
Link: http://lkml.kernel.org/n/tip-kj9bpn6v213n6
From: Srinivas Kandagatla
BAM_DESC_CNT_TRSHLD register is global register, which can only be written
when BAM is in master mode, So check the mode of operation before writing
it.
Without this check SOC's xPU would catch such access and crash the system.
First noticed on DB820c while testing SLIM
From: Srinivas Kandagatla
Hi Andy,
I did hit few issues while trying out SLIMBus BAM on DB820c, this BAM instance
is remotely controlled and powered up after ADSP is booted using QMI commands.
Firstly some of the master registers are written even when the BAM is remotely
controlled, and secondl
From: Srinivas Kandagatla
Remotely controlled BAM instance should not do any power management from
CPU side, as cpu can not reliably say if the BAM is busy or not.
Disable it for such instances.
Signed-off-by: Srinivas Kandagatla
---
drivers/dma/qcom/bam_dma.c | 11 +--
1 file changed
From: Srinivas Kandagatla
When Linux is master of BAM, it can directly read registers to know number
of supported channels, however when its remotely controlled reading these
registers would trigger a crash if the BAM is not yet initialized or
powered up on the remote side.
This patch allows dri
From: Srinivas Kandagatla
This patch adds 2 new properties for remote controlled bam dt bindings.
1. num-channels to indicate number of dma channels.
2. qcom,num-ees to indicate number of Execution Environments.
Signed-off-by: Srinivas Kandagatla
---
Documentation/devicetree/bindings/dma/qcom_
From: Srinivas Kandagatla
When BAM is remotely controlled it does not sound correct to control
its clk on Linux side. Make it optional, so that its not mandatory
for remote controlled BAM instances.
Signed-off-by: Srinivas Kandagatla
---
drivers/dma/qcom/bam_dma.c | 8 ++--
1 file changed,
There's no need for kernel maps to be allocated at this
point - sample processing.
We search for kernel maps using the kernel map_groups in
machine::kmaps which is static. If vmlinux maps for any
reason still don't exist, the search correctly fails
because they are not in the map group.
Link: htt
We should not search for kernel start address in
__machine__create_kernel_maps function, because it's being
used in 'report' code path, where we are interested in kernel
MMAP data address instead of in current kernel address
The __machine__create_kernel_maps serves purely for creating
the machines
Current code in dso__load calls the is_regular_file function,
but it checks its return value only after calling symsrc__init.
That can make symsrc__init block in elf_* functions on reading
the file if the file happens to be device and not regular one.
Calling symsrc__init only for regular files.
Freeing root_dir in machine__init error path.
Link: http://lkml.kernel.org/n/tip-ng92slsanexqw7h1d6sad...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/machine.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/machine.c b/tools/perf/util/m
So it could be called without event object, just with start
and end values. It will be used in following patch.
Link: http://lkml.kernel.org/n/tip-u4hu7m5fmwwsscy6ki70h...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/machine.c | 13 +++--
1 file changed, 7 insertions(+), 6
Adding check on failed attempt to parse the address
and skip the line parsing early in that case.
The address can be replaced with '(null)' string in
case user don't have enough permissions, like:
$ cat /proc/kallsyms
(null) A irq_stack_union
(null) A __per_cpu_start
...
Link
It simplifies and centralizes the code. The kernel mmap
name is set for machine type, which we know from the
beginning, so there's no reason to generate it every time
we need it.
Link: http://lkml.kernel.org/n/tip-2fx7kxxdc5zcm6990cq2m...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/ut
Am 15.02.2018 um 06:20 schrieb Gustavo A. R. Silva:
Currently, if amdgpu_vm_bo_update() fails, the returned error
is being ignored.
Fix this by properly checking _r_ after calling amdgpu_vm_bo_update.
Also, remove redundant code just before label _error_.
Addresses-Coverity-ID: 1464280 ("Unused
This patch duplicates work performed by Ulrich.
Please consider this patch dropped, and no need for review.
(especially the obvious error in the pin-values)
Oh well - it was a fun exercise to go through :-)
--
Regards
Kieran
On 15/02/18 08:38, Kieran Bingham wrote:
> From: Kieran Bingham
>
On Thu, Feb 15, 2018 at 12:47:25PM +0100, Rafael J. Wysocki wrote:
> On Thu, Feb 15, 2018 at 12:19 PM, John Garry wrote:
> >> Nothing apart from only being used by arm64 platforms today, which is
> >> circumstantial.
> >>
> >>>
> >>> I understand you need to find a place to add the:
> >>>
> >>> ac
Hi Geert,
On 15/02/18 09:07, Geert Uytterhoeven wrote:
> Hi Kieran,
>
> On Thu, Feb 15, 2018 at 9:38 AM, Kieran Bingham wrote:
>> From: Kieran Bingham
>>
>> The r8a77995 D3 platform has 2 LVDS channels connected to the DU.
>>
>> Signed-off-by: Kieran Bingham
>
> I love your patch!
> Yet somet
On Tue 13-02-18 14:31:59, Pavel Tatashin wrote:
[...]
> @@ -201,21 +202,24 @@ static bool pages_correctly_reserved(unsigned long
> start_pfn)
>* SPARSEMEM_VMEMMAP. We lookup the page once per section
>* and assume memmap is contiguous within each section
>*/
> - for (i
On Wed, Feb 14, 2018 at 2:55 AM, David Daney wrote:
> The ISL12026 is a combination RTC and EEPROM device with I2C
> interface. The standard RTC driver interface is provided. The EEPROM
> is accessed via the NVMEM interface via the "eeprom0" directory in the
> sysfs entry for the device.
Thanks
Hi Kieran,
On Thu, Feb 15, 2018 at 1:41 PM, Kieran Bingham
wrote:
> On 15/02/18 09:07, Geert Uytterhoeven wrote:
>> On Thu, Feb 15, 2018 at 9:38 AM, Kieran Bingham wrote:
>>> From: Kieran Bingham
>>>
>>> The r8a77995 D3 platform has 2 LVDS channels connected to the DU.
>>>
>>> Signed-off-by: Ki
On Thu, Jan 25, 2018 at 03:21:44PM +0800, Aaron Lu wrote:
> When freeing a batch of pages from Per-CPU-Pages(PCP) back to buddy,
> the zone->lock is held and then pages are chosen from PCP's migratetype
> list. While there is actually no need to do this 'choose part' under
> lock since it's PCP pag
On Sun, Feb 4, 2018 at 8:25 PM, Steven Presser wrote:
> The information is in kernel bug 198671.
Steve, any news on testing?
Shall I submit the series for official review?
>> Here [1] is the branch with another approach. Can you test it and tell
>> if it fixes the issue?
>>
>> [1]: https://bitb
On 02/13/2018 03:06 PM, Javier González wrote:
From: Javier González
The 2.0 spec provides a report chunk log page that can be retrieved
using the stangard nvme get log page. This replaces the dedicated
get/put bad block table in 1.2.
This patch implements the helper functions to allow targets
On 15/02/2018 12:22, Andy Shevchenko wrote:
On Thu, Feb 15, 2018 at 1:19 PM, John Garry wrote:
Hi Andy,
+static const struct acpi_device_id indirect_io_hosts[] = {
+{"HISI0191", 0},/* HiSilicon LPC host */
+{},
Just a nit.
I noticed that I have this in the LLDD also. I thin
On Thu, Feb 15, 2018 at 9:24 AM, Hans de Goede wrote:
> Sometimes (firmware bug?) the V5 boost GPIO is not configured as output
> by the BIOS, leading to the 5V boost convertor being permanently on,
>
> Explicitly set the direction and drv flags rather then inheriting them
> from the firmware to f
On Thu, Feb 15, 2018 at 2:52 PM, John Garry wrote:
> On 15/02/2018 12:22, Andy Shevchenko wrote:
>> On Thu, Feb 15, 2018 at 1:19 PM, John Garry wrote:
>>> +static const struct acpi_device_id indirect_io_hosts[] = {
>>> +{"HISI0191", 0},/* HiSilicon LPC host */
>>> +{},
>>
>>
>> Just
Hi Jerome,
On 2018-02-14 14:43, Jerome Brunet wrote:
The orphan clocks reparents should migrate any existing count from the
orphan clock to its new acestor clocks, otherwise we may have
inconsistent counts in the tree and end-up with gated critical clocks
Assuming we have two clocks, A and B.
*
On 15/02/2018 11:47, Rafael J. Wysocki wrote:
On Thu, Feb 15, 2018 at 12:19 PM, John Garry wrote:
Nothing apart from only being used by arm64 platforms today, which is
circumstantial.
I understand you need to find a place to add the:
acpi_indirect_io_scan_init()
to be called from core ACPI
> No hardcoded stuff please! :-D
I expected as much :) So I looked into it a bit more and came up with
the patch below. It works for me but I'm unsure about two things in
particular:
In the __overrides__ section of the *.dts, why does gpiopin set reg and
should echopin set this as well?
In pps-g
Hi Matthew,
On Tue, Feb 13, 2018 at 07:16:08AM -0800, Matthew Wilcox wrote:
> On Tue, Feb 13, 2018 at 12:58:51PM +, Will Deacon wrote:
> > This patch resolves the livelock by not taking hlist_bl_lock in
> > d_alloc_parallel if the sequence counter is odd, since any subsequent
> > masked compar
---
drivers/pps/clients/pps-gpio.c | 1 +
include/linux/pps-gpio.h | 2 ++
2 files changed, 3 insertions(+)
diff --git a/drivers/pps/clients/pps-gpio.c b/drivers/pps/clients/pps-gpio.c
index dd7624f1d23f..35c3b14fc9b9 100644
--- a/drivers/pps/clients/pps-gpio.c
+++ b/drivers/pps/clients/pps
---
arch/arm/boot/dts/overlays/pps-gpio-overlay.dts | 13 -
drivers/pps/clients/pps-gpio.c | 26 ++---
include/linux/pps-gpio.h| 1 +
3 files changed, 24 insertions(+), 16 deletions(-)
diff --git a/arch/arm/boot/dts/overlay
Avoid issue when probing the RNG without
reset if bad status has been detected previously
Signed-off-by: Lionel Debieve
---
drivers/char/hw_random/stm32-rng.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/char/hw_random/stm32-rng.c
b/drivers/char/hw_random/stm32-rng.c
ind
Add optional property to enable the clock detection error
on rng block. It is used to allow slow clock source which
give correct entropy for rng.
Signed-off-by: Lionel Debieve
---
Documentation/devicetree/bindings/rng/st,stm32-rng.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documenta
Adding optional resets property for rng.
Signed-off-by: Lionel Debieve
---
Documentation/devicetree/bindings/rng/st,stm32-rng.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/rng/st,stm32-rng.txt
b/Documentation/devicetree/bindings/rng/st,stm32-rng.tx
Add a new property that allow to disable the clock error
detection which is required when the clock source selected
is out of specification (which is not mandatory).
Signed-off-by: Lionel Debieve
---
drivers/char/hw_random/stm32-rng.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(
This set of patches add extended functionalities for stm32 rng
driver.
Patch #1 includes a reset during probe to avoid any error status
which can occur during bootup process and keep safe rng integrity.
Patch #3 adds a new property to manage the clock error detection
feature which can be disabled
Increase timeout delay to support longer timing linked
to rng initialization. Measurement is based on timer instead
of instructions per iteration which is not powerful on all
targets.
Signed-off-by: Lionel Debieve
---
drivers/char/hw_random/stm32-rng.c | 25 ++---
1 file chan
Make the 1.2 data structures explicit, so it will be easy to identify
the 2.0 data structures. Also fix the order of which the nvme_nvm_*
are declared, such that they follow the nvme_nvm_command order.
Signed-off-by: Matias Bjørling
---
drivers/nvme/host/lightnvm.c | 82 ++---
A couple of patches for 2.0 support for the lightnvm subsystem. They
form the foundation for the integration.
The first two patches is preparation for the 2.0 work. The third patch
implements the 2.0 data structures, the geometry command, and exposes
the sysfs attributes that comes with the 2.0 sp
The value of max_phys_sect is always static. Instead of
defining it in the nvm_dev_ops structure, declare it as a global
value.
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/core.c | 28 +++-
drivers/lightnvm/pblk-init.c | 9 -
drivers/lightnvm
- On Feb 15, 2018, at 6:49 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Wed, Feb 14, 2018 at 06:53:44PM +, Mathieu Desnoyers wrote:
>> However, given the scenario involves multiples CPUs (one doing exit_mm(),
>> the other doing context switch), the actual order of perceived load/sto
The nvme driver sets up the size of the nvme namespace in two steps.
First it initializes the device with standard logical block and
metadata sizes, and then sets the correct logical block and metadata
size. Due to the OCSSD 2.0 specification relies on the namespace to
expose these sizes for correc
Implement the geometry data structures for 2.0 and enable a drive
to be identified as one, including exposing the appropriate 2.0
sysfs entries.
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/core.c | 8 +-
drivers/nvme/host/lightnvm.c | 334 +-
There are no groups in the 2.0 specification, make sure that the
nvm_id structure is flattened before 2.0 data structures are added.
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/core.c | 25 ++-
drivers/nvme/host/lightnvm.c | 100 +--
The field is no longer used.
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/core.c | 1 -
include/linux/lightnvm.h | 2 --
2 files changed, 3 deletions(-)
diff --git a/drivers/lightnvm/core.c b/drivers/lightnvm/core.c
index 9b1255b3e05e..511c81c319ee 100644
--- a/drivers/lightnvm/core.c
+
On 15/02/2018 at 14:45:11 +0200, Andy Shevchenko wrote:
> On Wed, Feb 14, 2018 at 2:55 AM, David Daney wrote:
> > The ISL12026 is a combination RTC and EEPROM device with I2C
> > interface. The standard RTC driver interface is provided. The EEPROM
> > is accessed via the NVMEM interface via the
>
> BTW... I'd really like to have a database of machine, kernel version,
> cpuinfo, config... So that questions like "what is the latest kernel
> that is known to be running on this hardware" and "what config should
> I start from".
>
> For example, I have nokia N810 here. It was supported by Linu
Hi,
Geert Uytterhoeven writes:
> Add dummies for usb_gadget_{,un}map_request{,_by_dev}(), to allow
> compile-testing if NO_DMA=y.
>
> This prevents the following from showing up later:
>
> ERROR: "usb_gadget_unmap_request_by_dev"
> [drivers/usb/renesas_usbhs/renesas_usbhs.ko] undefined!
>
From: Srinivas Kandagatla
This patch adds supplies that are required for msm8996. vdda
is analog supply that go in to controller, and vddpe_3v3 is
supply to PCIe endpoint.
Without these supplies PCIe endpoints which require power supplies are
not enumerated at all, as there is no one to power it
From: Dave Hansen
Kernel mappings are historically _PAGE_GLOBAL. But, with PTI, we do not
want them to be _PAGE_GLOBAL. We currently accomplish this by simply
clearing _PAGE_GLOBAL from the suppotred mask which ensures it is
cleansed from many of our PTE construction sites:
if (!stati
From: Dave Hansen
The entry/exit text and cpu_entry_area are mapped into userspace and
the kernel. But, they are not _PAGE_GLOBAL. This creates unnecessary
TLB misses.
Add the _PAGE_GLOBAL flag for these areas.
After this patch, we can see that "GLB" shows up in each copy of the
page tables,
From: Dave Hansen
The pageattr code has a pattern repeated where it sets a PTE bit
for present PTEs but clears it for non-present PTEs. This helps
to keep pte_none() from getting messed up. _PAGE_GLOBAL is the
most frequent target of this pattern.
This pattern also includes a nice, copy-and-p
The later verions of the KAISER pathces (pre-PTI) allowed the user/kernel
shared areas to be GLOBAL. The thought was that this would reduce the
TLB overhead of keeping two copies of these mappings.
During the switch over to PTI, we seem to have lost our ability to have
GLOBAL mappings. This adds
The (clock) id argument of clockid_to_kclock() comes straight from user
space via various syscalls and is used as index into the posix_clocks
array.
Protect it against spectre v1 array out of bounds speculation.
Signed-off-by: Thomas Gleixner
Cc: sta...@vger.kernel.org
---
kernel/time/posix-tim
Thank you Mel!
Pavel
On Thu, Feb 15, 2018 at 5:55 AM, Mel Gorman wrote:
> On Wed, Feb 14, 2018 at 11:33:43AM -0500, Pavel Tatashin wrote:
>> Deferred page initialization allows the boot cpu to initialize a small
>> subset of the system's pages early in boot, with other cpus doing the rest
>> lat
From: Srinivas Kandagatla
This patch converts existing regulators to use regulator bulk apis,
to make it consistent with msm8996 changes also cut down some redundant code.
Signed-off-by: Srinivas Kandagatla
---
Changes since v1:
updated index correctly and use ARRAY_SIZE
drivers/pci/d
Geert Uytterhoeven writes:
> Remove dependencies on HAS_DMA where a Kconfig symbol depends on another
> symbol that implies HAS_DMA, and, optionally, on "|| COMPILE_TEST".
> In most cases this other symbol is an architecture or platform specific
> symbol, or PCI.
>
> Generic symbols and drivers w
Hi Michal,
Thank you very much for your reviews and for Acking this patch.
>
> The whole memblock != section_size sucks! It leads to corner cases like
> you see. There is no real reason why we shouldn't be able to to online
> 2G unaligned memory range. Failing for that purpose is just wrong. The
From: Ludovic Barre
This patch serie adds support of stm32 SDMMC controller.
stm32h7 is the first SoC to use stm32 SDMMC controller
(previous SoC had pl180 controller).
The SDMMC features include the following:
-Full compliance with MultiMediaCard System Specification Version 4.51.
Card support
From: Ludovic Barre
This patch adds sdmmc support for stm32h743.
2×SD/SDIO/MMC interfaces (up to 125 MHz)
Signed-off-by: Ludovic Barre
---
arch/arm/boot/dts/stm32h743.dtsi | 26 ++
1 file changed, 26 insertions(+)
diff --git a/arch/arm/boot/dts/stm32h743.dtsi b/arch/ar
From: Ludovic Barre
This patch adds support of
-mmc framework and stm32 sdmmc controller
-ext2/3/4 filesystem
-LBDAF to support huge file (needed for ext4)
Signed-off-by: Ludovic Barre
---
arch/arm/configs/stm32_defconfig | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/a
From: Ludovic Barre
This patch adds support of micro sd card connected to sdmmc1.
Signed-off-by: Ludovic Barre
---
arch/arm/boot/dts/stm32h743-pinctrl.dtsi | 26 ++
arch/arm/boot/dts/stm32h743i-eval.dts| 11 +++
2 files changed, 37 insertions(+)
diff --git
From: Ludovic Barre
This patch adds support for stm32 SDMMC controller.
The SDMMC controller provides an interface for SD,SDIO
cards and MMC devices.
The SDMMC features include the following:
-Full compliance with MultiMediaCard System Specification Version 4.51.
Card support for three differen
From: Ludovic Barre
Document the binding for stm32 sdmmc controller.
Signed-off-by: Ludovic Barre
---
.../devicetree/bindings/mmc/st,stm32-sdmmc.txt | 35 ++
1 file changed, 35 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mmc/st,stm32-sdmmc.txt
d
101 - 200 of 1436 matches
Mail list logo
