On (04/04/17 11:01), Petr Mladek wrote:
[..]
> > +static atomic_t printk_emergency __read_mostly;
> > +/*
> > + * Disable printk_kthread permanently. Unlike `oops_in_progress'
> > + * it doesn't go back to 0.
> > + */
>
> The comment is not valid once we allow to modify the variable using
> the sy
On Thu 30-03-17 15:22:29, Andrew Morton wrote:
> On Thu, 30 Mar 2017 13:27:16 +0300 Andrey Ryabinin
> wrote:
[...]
> > This can be fixed in vmgfx, but it would be better to make vfree()
> > non-sleeping again because we may have other bugs like this one.
>
> I tend to disagree: adding yet anothe
On Tue, Apr 04 2017, Michael Wang wrote:
> Hi, Neil
>
> On 04/03/2017 11:25 PM, NeilBrown wrote:
>> On Mon, Apr 03 2017, Michael Wang wrote:
>>
>>> blk_attempt_plug_merge() try to merge bio into request and chain them
>>> by 'bi_next', while after the bio is done inside request, we forgot to
>>>
On Thu 30-03-17 13:27:16, Andrey Ryabinin wrote:
> Commit 5803ed292e63 ("mm: mark all calls into the vmalloc subsystem
> as potentially sleeping") added might_sleep() to remove_vm_area() from
> vfree(), and commit 763b218ddfaf ("mm: add preempt points into
> __purge_vmap_area_lazy()") actually made
acpi_execute_simple_method() takes a method parameter which tells it to
look for the given method underneath the given handle, so calling
acpi_get_handle() beforehand is redundant. Replace the call to
acpi_get_handle() with a call to acpi_execute_simple_method(), thus
eliminating the need for a lo
Hi Neil,
Thank you for the patch.
On Monday 03 Apr 2017 16:42:36 Neil Armstrong wrote:
> Some display pipelines can only provide non-RBG input pixels to the HDMI TX
> Controller, this patch takes the pixel format from the plat_data if
> provided.
The commit message doesn't seem to match the subj
On Tue, Apr 04, 2017 at 02:45:26PM +0530, Pushkar Jambhlekar wrote:
> diff --git a/drivers/staging/lustre/lustre/obdclass/cl_page.c
> b/drivers/staging/lustre/lustre/obdclass/cl_page.c
> index cd9a40c..71fcc4c 100644
> --- a/drivers/staging/lustre/lustre/obdclass/cl_page.c
> +++ b/drivers/staging/
Hi Neil,
Thank you for the patch.
On Monday 03 Apr 2017 16:42:37 Neil Armstrong wrote:
> This patch adds a new DRM documentation entry and links to the input
> format table added in the dw_hdmi header.
>
> Reviewed-by: Archit Taneja
> Signed-off-by: Neil Armstrong
Acked-by: Laurent Pinchart
On Thu 30-03-17 13:27:19, Andrey Ryabinin wrote:
> vfree() can be used in any atomic context and there is no
> vfree_atomic() callers left, so let's remove it.
>
> This reverts commit bf22e37a6413 ("mm: add vfree_atomic()")
>
> Signed-off-by: Andrey Ryabinin
the idea was nice but reality hits t
On Thu 30-03-17 17:48:39, Andrey Ryabinin wrote:
> From: Andrey Ryabinin
> Subject: mm/vmalloc: allow to call vfree() in atomic context fix
>
> Don't spawn worker if we already purging.
>
> Signed-off-by: Andrey Ryabinin
I would rather put this into a separate patch. Ideally with some numners
Hello, Sinclair!
> Here, the check should be "> DRM_VMW_MAX_MIP_LEVELS" because req->mip_levels
> is only for one layer.
Got it, thanks!
> Also, as long as we can doing a check, I would suggest we check for 0 as
> well.
Do you mean a check for "req->mip_levels > 0" or for "req->mip_levels >= 0"
Replacing 'unsigned' with 'unsigned int'
Signed-off-by: Pushkar Jambhlekar
---
drivers/staging/lustre/lustre/llite/namei.c | 2 +-
drivers/staging/lustre/lustre/llite/rw26.c | 2 +-
drivers/staging/lustre/lustre/llite/vvp_dev.c | 6 +++---
drivers/staging/lustr
Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> The pu regulator request will return -EPROBE_DEFER if it has a supply
> from PMIC and this supply is not yet registered. This does not represent
> an error since the driver will call probe again later, so only print a
> warning mess
Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> From: Irina Tirdea
>
> If there are any errors in getting the cpu0 regulators, the driver returns
> -ENOENT. In case the regulators are not yet available, the devm_regulator_get
> calls will return -EPROBE_DEFER, so that the drive
On 04/04/2017 11:41 AM, Michal Hocko wrote:
> On Thu 30-03-17 17:48:39, Andrey Ryabinin wrote:
>> From: Andrey Ryabinin
>> Subject: mm/vmalloc: allow to call vfree() in atomic context fix
>>
>> Don't spawn worker if we already purging.
>>
>> Signed-off-by: Andrey Ryabinin
> I would rather put thi
On Tue, 04 Apr 2017, Krzysztof Kozlowski wrote:
> On Mon, Apr 3, 2017 at 12:18 PM, Lee Jones wrote:
> > On Tue, 28 Mar 2017, Krzysztof Kozlowski wrote:
> >
> >>
> >> Hi Lee,
> >>
> >>
> >> This is dependency for mfd/exynos-lpass driver changes from Marek
> >> Szyprowski.
> >> That's a material f
Allwinner SoCs after sun6i-a31 nearly all have a R_CCU in PRCM part.
(V3s and R40 do not have it, as they have even no PRCM)
This patch adds support for the ones on H3/A64.
Some clock/reset values are reserved for easier extending the support to
A31/A23, but for this I think some changes to the P
Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> If the cpufreq driver tries to modify voltage/freq during suspend/resume
> it might need to control an external PMIC via I2C or SPI but those
> devices might be already suspended.
>
> To avoid this scenario we just increase cpufreq
From: Icenowy Zheng
Many Allwinner SoCs after A31 have a CCU in PRCM block.
Give the ones on H3 and A64 compatible strings.
Signed-off-by: Icenowy Zheng
Acked-by: Rob Herring
---
Changes in v4:
- Add Rob's ACK.
Changes in v3:
- Removed frequency info of iosc in this device tree binding docume
Commit-ID: b91473ff6e979c0028f02f90e40c844959c736d8
Gitweb: http://git.kernel.org/tip/b91473ff6e979c0028f02f90e40c844959c736d8
Author: Peter Zijlstra
AuthorDate: Thu, 23 Mar 2017 15:56:12 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 4 Apr 2017 11:44:06 +0200
sched,tracing: Update
Commit-ID: e96a7705e7d3fef96aec9b590c63b2f6f7d2ba22
Gitweb: http://git.kernel.org/tip/e96a7705e7d3fef96aec9b590c63b2f6f7d2ba22
Author: Xunlei Pang
AuthorDate: Thu, 23 Mar 2017 15:56:08 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 4 Apr 2017 11:44:05 +0200
sched/rtmutex/deadline: F
Commit-ID: 19830e55247cddb3f46f1bf60b8e245593491bea
Gitweb: http://git.kernel.org/tip/19830e55247cddb3f46f1bf60b8e245593491bea
Author: Peter Zijlstra
AuthorDate: Thu, 23 Mar 2017 15:56:14 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 4 Apr 2017 11:44:07 +0200
rtmutex: Fix more prio
Hi,
On 04-04-17 05:25, Dmitry Torokhov wrote:
There is no point in registering I2C bus notifier if DMI data does not
match.
Signed-off-by: Dmitry Torokhov
Good idea, patch looks good to me:
Reviewed-by: Hans de Goede
Regards,
Hans
---
drivers/platform/x86/silead_dmi.c | 20 ++
Hi,
On 04-04-17 05:25, Dmitry Torokhov wrote:
I2C bus has both i2c clients and adapter devices, so we must be careful in
notifier code and verify that we are actually dealing with an i2c client
before using it as such.
Fixes: cef9dd85acd7 ("platform/x86: add support for devices with Silead...")
On Mon, Apr 03, 2017 at 02:01:06PM -0500, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> The peripherals EDACs only exist on the Arria10 SoCFPGA. The Cyclone5
> initialization has EDAC warnings when the peripherals aren't found
> in the device tree. Fix by checking for Arria10 in the
From: Icenowy Zheng
SoCs after A31 has a clock controller module in the PRCM part.
Support the clock controller module on H3/5 and A64 now.
Signed-off-by: Icenowy Zheng
---
Changes in v4:
- Add missing twd items in *_ccu_clks.
Changes in v3:
- Change osc32000 mux to iosc, as its frequency vari
Commit-ID: e0aad5b44ff5d28ac1d6ae70cdf84ca228e889dc
Gitweb: http://git.kernel.org/tip/e0aad5b44ff5d28ac1d6ae70cdf84ca228e889dc
Author: Peter Zijlstra
AuthorDate: Thu, 23 Mar 2017 15:56:13 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 4 Apr 2017 11:44:06 +0200
rtmutex: Fix PI chain
On Tue, Apr 04, 2017 at 10:50:54AM +0100, Lee Jones wrote:
> On Tue, 04 Apr 2017, Krzysztof Kozlowski wrote:
>
> > On Mon, Apr 3, 2017 at 12:18 PM, Lee Jones wrote:
> > > On Tue, 28 Mar 2017, Krzysztof Kozlowski wrote:
> > >
> > >>
> > >> Hi Lee,
> > >>
> > >>
> > >> This is dependency for mfd/ex
01.04.2017 20:49, H. Peter Anvin пишет:
,linux-ms...@vger.kernel.org,wine-de...@winehq.org
From: h...@zytor.com
Message-ID: <3fd12652-aa83-4d73-9914-bba089e58...@zytor.com>
On April 1, 2017 6:08:43 AM PDT, Stas Sergeev wrote:
30.03.2017 08:14, Ricardo Neri пишет:
You know the wine's
requireme
Commit-ID: 7bf8222b9bd0ba867e18b7f4537b61ef2e92eee8
Gitweb: http://git.kernel.org/tip/7bf8222b9bd0ba867e18b7f4537b61ef2e92eee8
Author: Keith Busch
AuthorDate: Mon, 3 Apr 2017 15:25:53 -0400
Committer: Thomas Gleixner
CommitDate: Tue, 4 Apr 2017 11:57:28 +0200
irq/affinity: Fix CPU spre
On 2017-04-04 05:21, Richard Guy Briggs wrote:
> Tracefs or debugfs were causing hundreds to thousands of PATH records to
> be associated with the init_module and finit_module SYSCALL records on a
> few modules when the following rule was in place for startup:
> -a always,exit -F arch=x86_64
((void)sizeof !!(exp)) => I believe it is for compiler to unflag
"unused variable" warning.
On Tue, Apr 4, 2017 at 3:08 PM, Dan Carpenter wrote:
> On Tue, Apr 04, 2017 at 02:45:26PM +0530, Pushkar Jambhlekar wrote:
>> diff --git a/drivers/staging/lustre/lustre/obdclass/cl_page.c
>> b/drivers/sta
Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> Setting the supply is optional but beneficial, it will cause PMIC
> voltages to be dynamically changed with cpu frequency.
>
> Signed-off-by: Leonard Crestez
Reviewed-by: Lucas Stach
> ---
> arch/arm/boot/dts/imx6qdl-sabresd.d
> Elena Reshetova writes:
>
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-after-free
> > situations.
> >
> > Signed-off-by: Ele
Hi Suzuki,
On Mon, Apr 03, 2017 at 03:12:43PM +0100, Suzuki K Poulose wrote:
> In kvm_free_stage2_pgd() we don't hold the kvm->mmu_lock while calling
> unmap_stage2_range() on the entire memory range for the guest. This could
> cause problems with other callers (e.g, munmap on a memslot) trying to
From: Icenowy Zheng
A64 SoC have a CCU (r_ccu) in PRCM block.
Add the device node for it.
The mux 3 of R_CCU is an internal oscillator, which is 16MHz according
to the user manual, and has only 30% accuracy based on our experience
on older SoCs. The real mesaured value of it on two Pine64 board
Configuring DMA ops at probe time will allow deferring device probe when
the IOMMU isn't available yet. The dma_configure for the device is
now called from the generic device_attach callback just before the
bus/driver probe is called. This way, configuring the DMA ops for the
device would be called
This is an equivalent to the DT's handling of the iommu master's probe
with deferred probing when the corrsponding iommu is not probed yet.
The lack of a registered IOMMU can be caused by the lack of a driver for
the IOMMU, the IOMMU device probe not having been performed yet, having
been deferred,
From: Robin Murphy
Now that the appropriate ordering is enforced via probe-deferral of
masters in core code, rip it all out and bask in the simplicity.
Tested-by: Hanjun Guo
Acked-by: Will Deacon
Signed-off-by: Robin Murphy
[Sricharan: Rebased on top of ACPI IORT SMMU series]
Signed-off-by: S
From: Lorenzo Pieralisi
The IORT linker section introduced by commit 34ceea275f62
("ACPI/IORT: Introduce linker section for IORT entries probing")
was needed to make sure SMMU drivers are registered (and therefore
probed) in the kernel before devices using the SMMU have a chance
to probe in turn.
With arch_setup_dma_ops now being called late during device's probe after
the device's iommu is probed, the notifier trick required to handle the
early setup of dma_ops before the iommu group gets created is not
required. So removing the notifier's here.
Tested-by: Marek Szyprowski
Tested-by: Han
Hi,
On 09-03-17 11:43, Hans de Goede wrote:
Hi,
On 09-03-17 10:59, Jean Delvare wrote:
So I would really like to see support for this kernel cmdline option merged.
Takashi Iwai has been working on some quirks for headphone detection for
the GPDwin machine, which also rely on being able to
From: Robin Murphy
In preparation for some upcoming cleverness, rework the control flow in
of_iommu_configure() to minimise duplication and improve the propogation
of errors. It's also as good a time as any to switch over from the
now-just-a-compatibility-wrapper of_iommu_get_ops() to using the g
This series calls the dma ops configuration for the devices
at a generic place so that it works for all busses.
The dma_configure_ops for a device is now called during
the device_attach callback just before the probe of the
bus/driver is called. Similarly dma_deconfigure is called during
device/dri
From: Laurent Pinchart
Failures to look up an IOMMU when parsing the DT iommus property need to
be handled separately from the .of_xlate() failures to support deferred
probing.
The lack of a registered IOMMU can be caused by the lack of a driver for
the IOMMU, the IOMMU device probe not having b
From: Robin Murphy
IOMMU configuration represents unchanging properties of the hardware,
and as such should only need happen once in a device's lifetime, but
the necessary interaction with the IOMMU device and driver complicates
exactly when that point should be.
Since the only reasonable tool a
On 04/04/2017 11:37 AM, NeilBrown wrote:
> On Tue, Apr 04 2017, Michael Wang wrote:
[snip]
>>>
>>> If sync_request_write() is using a bio that has already been used, it
>>> should call bio_reset() and fill in the details again.
>>> However I don't see how that would happen.
>>> Can you give specif
From: Laurent Pinchart
Invalid dma-ranges values should be worked around when retrieving the
DMA range in of_dma_get_range(), not by all callers of the function.
This isn't much of a problem now that we have a single caller, but that
situation will change when moving DMA configuration to device p
From: Laurent Pinchart
As part of moving DMA initializing to probe time the
of_dma_deconfigure() function will need to be called from different
source files. Make it public and move it to drivers/of/device.c where
the of_dma_configure() function is.
Tested-by: Marek Szyprowski
Signed-off-by: La
Size of the dma-range is calculated as coherent_dma_mask + 1
and passed to arch_setup_dma_ops further. It overflows when
the coherent_dma_mask is set for full 64 bits 0x,
resulting in size getting passed as 0 wrongly. Fix this by
passsing in max(mask, mask + 1). Note that in this ca
From: Lorenzo Pieralisi
The IOMMU probe deferral implementation requires a mechanism to detect
if drivers for SMMU components are built-in in the kernel to detect
whether IOMMU configuration for a given device should be deferred (ie
SMMU drivers present but still not probed) or not (drivers not p
Commit-ID: 85e2d4f992868ad78dc8bb2c077b652fcfb3661a
Gitweb: http://git.kernel.org/tip/85e2d4f992868ad78dc8bb2c077b652fcfb3661a
Author: Xunlei Pang
AuthorDate: Thu, 23 Mar 2017 15:56:09 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 4 Apr 2017 11:44:05 +0200
sched/deadline/rtmutex: D
On Tue, 2017-04-04 at 11:46 +0200, Lucas Stach wrote:
> Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> >
> > The pu regulator request will return -EPROBE_DEFER if it has a supply
> > from PMIC and this supply is not yet registered. This does not represent
> > an error since the
Am Dienstag, den 04.04.2017, 13:28 +0300 schrieb Leonard Crestez:
> On Tue, 2017-04-04 at 11:46 +0200, Lucas Stach wrote:
> > Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> > >
> > > The pu regulator request will return -EPROBE_DEFER if it has a supply
> > > from PMIC and this
From: Icenowy Zheng
Now we have driver for the PRCM CCU, switch to use it instead of
old-style clock nodes for apb0-related clocks in sunxi-h3-h5.dtsi .
The mux 3 of R_CCU is still the internal oscillator, which is said to be
16MHz plus minus 30%, and get a measured value of 15MHz~16MHz on my tw
On Tue, 2017-04-04 at 10:18 +0200, Philipp Zabel wrote:
> Rename the internal __reset_control_get/put functions to
> __reset_control_get/put_internal and add an exported
> __reset_control_get equivalent to __of_reset_control_get
> that takes a struct device parameter.
> This avoids the confusing ca
Hi Christoffer,
On 04/04/17 11:13, Christoffer Dall wrote:
Hi Suzuki,
On Mon, Apr 03, 2017 at 03:12:43PM +0100, Suzuki K Poulose wrote:
In kvm_free_stage2_pgd() we don't hold the kvm->mmu_lock while calling
unmap_stage2_range() on the entire memory range for the guest. This could
cause problem
On Mon, 2017-04-03 at 10:28 +0200, Hans Verkuil wrote:
> On 03/31/2017 11:06 AM, Smitha T Murthy wrote:
> > Added V4l2 controls for HEVC encoder
> >
> > Signed-off-by: Smitha T Murthy
> > ---
> > Documentation/media/uapi/v4l/extended-controls.rst | 355
> > +
> > 1 file chan
Hey Logan,
We create a configfs attribute in each nvme-fabrics target port to
enable p2p memory use. When enabled, the port will only then use the
p2p memory if a p2p memory device can be found which is behind the
same switch as the RDMA port and all the block devices in use. If
the user enabled
Hi Philipp,
On 04/03/2017 10:06 PM, Philipp Zabel wrote:
Hi Vivek,
thank you for the patch series. A few comments below: I'd like to reduce
the API surface a bit and include the counting and array allocation in
the _get functions, if possible.
Thank you for reviewing the patch. Please find m
> Il giorno 31 mar 2017, alle ore 17:31, Bart Van Assche
> ha scritto:
>
> On Fri, 2017-03-31 at 14:47 +0200, Paolo Valente wrote:
>> -static bool bfq_update_peak_rate(struct bfq_data *bfqd, struct bfq_queue
>> *bfqq,
>> -bool compensate)
>> +static bool bfq_bfq
+static void setup_memwin_p2pmem(struct adapter *adap)
+{
+ unsigned int mem_base = t4_read_reg(adap, CIM_EXTMEM2_BASE_ADDR_A);
+ unsigned int mem_size = t4_read_reg(adap, CIM_EXTMEM2_ADDR_SIZE_A);
+
+ if (!use_p2pmem)
+ return;
This is weird, why even call this
commit d98ecda (arm64: perf: Count EL2 events if the kernel is running in HYP)
is returning error for perf syscall with mixed attribute set for exclude_kernel
and exlude_hv.
This change is breaking some applications (observed with hhvm) when
ran with VHE enabled. Adding change to enable EL2 event
Commit-ID: aa2bfe55366552cb7e93e8709d66e698d79ccc47
Gitweb: http://git.kernel.org/tip/aa2bfe55366552cb7e93e8709d66e698d79ccc47
Author: Peter Zijlstra
AuthorDate: Thu, 23 Mar 2017 15:56:10 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 4 Apr 2017 11:44:05 +0200
rtmutex: Clean up
Pre
From: Icenowy Zheng
Allwinner A64 have a dedicated pin controller to manage the PL pin bank.
As the driver and the required clock support are added, add the device
node for it.
Signed-off-by: Icenowy Zheng
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 12
1 file changed, 12
+ p2pmem_debugfs_root = debugfs_create_dir("p2pmem", NULL);
+ if (!p2pmem_debugfs_root)
+ pr_info("could not create debugfs entry, continuing\n");
+
Why continue? I think it'd be better to just fail it.
Besides, this can be safely squashed into patch 1.
Hi,
On 03-04-17 13:14, Hans de Goede wrote:
Hi,
On 03-04-17 09:24, Chanwoo Choi wrote:
As I already said, I think that extcon focus on sending the notification
to all of extcon consumers.
Ok, then lets keep your patches as they are, I've added the patches
from your extcon-test branch to
On 04/04/17 11:18, Sricharan R wrote:
> From: Laurent Pinchart
>
> Invalid dma-ranges values should be worked around when retrieving the
> DMA range in of_dma_get_range(), not by all callers of the function.
> This isn't much of a problem now that we have a single caller, but that
> situation wil
On 04/04/17 11:18, Sricharan R wrote:
> From: Laurent Pinchart
>
> As part of moving DMA initializing to probe time the
> of_dma_deconfigure() function will need to be called from different
> source files. Make it public and move it to drivers/of/device.c where
> the of_dma_configure() function i
Hi Alexey,
On 04/03/2017 11:07 PM, Alexey Klimov wrote:
(adding Prashanth to c/c)
Hi George,
On Fri, Mar 31, 2017 at 06:24:02AM +, George Cherian wrote:
Based on Section 14.1 of ACPI specification, it is possible to have a
maximum of 256 PCC subspace ids. Add support of multiple PCC subs
Hi,
On 2017년 04월 04일 19:47, Hans de Goede wrote:
> Hi,
>
> On 03-04-17 13:14, Hans de Goede wrote:
>> Hi,
>>
>> On 03-04-17 09:24, Chanwoo Choi wrote:
>
>
>
>>> As I already said, I think that extcon focus on sending the notification
>>> to all of extcon consumers.
>>
>> Ok, then lets keep you
Hi,
On 04-04-17 08:31, Chanwoo Choi wrote:
Hi,
On 2017년 04월 03일 20:26, Hans de Goede wrote:
Disable the 5v boost converter on probe in case it was left on by
the BIOS, this fixes 2 problems:
1) This gets seen by the external battery charger as a valid Vbus
supply and it then tries to feed
Provide Support for Hisilicon SoC(HiP05/06/07) Hardware event counters.
The Hisilicon SoC HiP0x series has many uncore or non-CPU performance
events and counters units.
This v7 version has addressed review comments of v6 version and based on
4.11-rc1.
This patch series is implemented refering to
Commit 7613c922315e308a ("backlight: pwm_bl: Move the checks for initial
power state to a separate function") not just moved some code, but made
slight changes in semantics.
If a gpiochip doesn't implement the optional .get_direction() callback,
gpiod_get_direction always returns -EINVAL, which is
From: Tan Xiaojun
Add Hisilicon HiP05/06/07 Djtag dts bindings for CPU and IO Die
Signed-off-by: Tan Xiaojun
Signed-off-by: Anurup M
Acked-by: Rob Herring
---
.../devicetree/bindings/arm/hisilicon/djtag.txt| 51 ++
1 file changed, 51 insertions(+)
create mode 100644
1) Device tree bindings for Hisilicon SoC PMU.
2) Add example for Hisilicon L3 cache and MN PMU.
3) Add child nodes of L3C and MN in djtag bindings example.
Signed-off-by: Anurup M
Signed-off-by: Shaokun Zhang
---
.../devicetree/bindings/arm/hisilicon/djtag.txt| 29 +++
.../devicetree/b
Documentation for perf usage and Hisilicon SoC PMU uncore events.
The Hisilicon SOC has event counters for hardware modules like
L3 cache, Miscellaneous node etc. These events are all uncore.
Signed-off-by: Anurup M
Signed-off-by: Shaokun Zhang
---
Documentation/perf/hisi-pmu.txt | 75 +
Update Kconfig for HiP05/06/07 PMU support.
Signed-off-by: Anurup M
Signed-off-by: Shaokun Zhang
Signed-off-by: John Garry
---
drivers/perf/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/perf/Kconfig b/drivers/perf/Kconfig
index 9365190..248d730 100644
--- a/driver
From: Tan Xiaojun
The Hisilicon Djtag is an independent component which connects
with some other components in the SoC by Debug Bus. This driver
can be configured to access the registers of connecting components
(like L3 cache) during real time debugging.
Signed-off-by: Tan Xiaojun
Signed-off-b
Add support for Hisilicon SoC hardware event counters
for HiP05/06/07 chip versions.
Signed-off-by: Anurup M
Signed-off-by: Shaokun Zhang
---
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6d7b7a7..4a95977 100644
--- a/MAINTAINERS
+++
1. HiP05/06/07 uncore PMU to support different hardware event counters.
2. Hisilicon PMU shall use the DJTAG hardware interface to access
hardware event counters and configuration register.
3. Routines to enable/disable/add/del/start/stop hardware event counting.
4. Add support to count L3 cache
Add nodes for djtag, L3 cache and MN to support uncore events.
Signed-off-by: Anurup M
---
arch/arm64/boot/dts/hisilicon/hip07.dtsi | 87
1 file changed, 87 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hip07.dtsi
b/arch/arm64/boot/dts/hisilicon/hip0
From: Shaokun Zhang
1. Add support to count MN hardware events.
2. Mn events are listed in sysfs at /sys/devices/hisi_mn_2/events/
The events can be selected as shown in perf list
e.g.: For MN_READ_REQUEST event for Super CPU cluster 2 the
event format is -e "hisi_mn_2/read_req/"
3. MN P
Hi Hoan/Prashanth,
On 04/03/2017 11:20 PM, Hoan Tran wrote:
Hi George,
On Mon, Apr 3, 2017 at 9:44 AM, Prakash, Prashanth
wrote:
Hi George,
On 3/31/2017 12:24 AM, George Cherian wrote:
The current cppc acpi driver works with only one pcc subspace id.
It maintains and registers only one pcc
Hi Vignesh,
[auto build test WARNING on spi/for-next]
[also build test WARNING on v4.11-rc5 next-20170404]
[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/Vignesh-R/spi-ti-qspi-Handle-vmalloc-d
u16 nvmet_copy_to_sgl(struct nvmet_req *req, off_t off, const void *buf,
size_t len)
{
- if (sg_pcopy_from_buffer(req->sg, req->sg_cnt, buf, len, off) != len)
+ bool iomem = req->p2pmem;
+ size_t ret;
+
+ ret = sg_copy_buffer(req->sg, req->sg_cnt, (void
Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> On imx6qp-sabresd LDO_ARM is connected to a different PMIC output than
> the other imx6qdl-sabresd boards.
>
> Setting cpu0 arm-supply to sw2_reg is wrong, this must have mistakenly
> slipped out of the vendor tree where this is ar
On 04/04/17 11:18, Sricharan R wrote:
> From: Lorenzo Pieralisi
>
> The IOMMU probe deferral implementation requires a mechanism to detect
> if drivers for SMMU components are built-in in the kernel to detect
> whether IOMMU configuration for a given device should be deferred (ie
> SMMU drivers p
Hi Sakari,
Thank you for the time to review this again.
On 04/04/2017 12:31 PM, Sakari Ailus wrote:
> Hi Todor,
>
> On Mon, Apr 03, 2017 at 05:02:28PM +0300, Todor Tomov wrote:
>> Add the document for ov5645 device tree binding.
>>
>> Signed-off-by: Todor Tomov
>> Reviewed-by: Laurent Pinchart
Commit-ID: acd58620e415aee4a43a808d7d2fd87259ee0001
Gitweb: http://git.kernel.org/tip/acd58620e415aee4a43a808d7d2fd87259ee0001
Author: Peter Zijlstra
AuthorDate: Thu, 23 Mar 2017 15:56:11 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 4 Apr 2017 11:44:06 +0200
sched/rtmutex: Refacto
On 04/04/17 11:18, Sricharan R wrote:
> Size of the dma-range is calculated as coherent_dma_mask + 1
> and passed to arch_setup_dma_ops further. It overflows when
> the coherent_dma_mask is set for full 64 bits 0x,
> resulting in size getting passed as 0 wrongly. Fix this by
> passs
From: Markus Elfring
Date: Tue, 4 Apr 2017 13:02:03 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Return directly after a failed memory allocation in policydb_index()
Return an error code only as a constant in sidtab_insert()
U
Hi,
Just as an update (and for future reference for anyone having similar issue):
I got this all this sorted-out. Had to change some dt-binding for
device and it was mostly drivers related changes for hardware
components. Mostly nothing to do with DT.
Thanks
Fawad Lateef
-- Fawad Lateef
On 3
On Thu 2017-03-30 14:55:46, Sergey Senozhatsky wrote:
> On (03/28/17 14:56), Petr Mladek wrote:
> [..]
> > > > Is it better? If not, I will send a version with console_cmdline_last.
> > >
> > > personally I'm fine with the nested loop. the latest version
> > > "for (last = MAX_CMDLINECONSOLES -
From: Markus Elfring
Date: Tue, 4 Apr 2017 11:33:53 +0200
* Return an error code without storing it in an intermediate variable.
* Delete the local variable "rc" and the jump label "out" which became
unnecessary with this refactoring.
Signed-off-by: Markus Elfring
---
security/selinux/ss/si
From: Markus Elfring
Date: Tue, 4 Apr 2017 12:23:41 +0200
The error code "-ENOMEM" was also returned so far when the parameter "s"
of this function contained a null pointer.
Now I find that the code "-EINVAL" is more appropriate in this case.
Signed-off-by: Markus Elfring
---
security/selinux/
Hello,
Quoting Felipe Balbi :
Hi,
"Gustavo A. R. Silva" writes:
Code refactoring to make the flow easier to follow.
Cc: Alan Stern
Cc: Greg Kroah-Hartman
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/misc/usbtest.c | 67
+-
1 file chan
From: Markus Elfring
Date: Tue, 4 Apr 2017 10:20:46 +0200
Replace five goto statements (and previous variable assignments) by
direct returns after a memory allocation failure in this function.
Signed-off-by: Markus Elfring
---
security/selinux/ss/policydb.c | 15 +--
1 file changed
On Tue, Apr 04, 2017 at 04:10:55PM +0530, Ganapatrao Kulkarni wrote:
> commit d98ecda (arm64: perf: Count EL2 events if the kernel is running in HYP)
> is returning error for perf syscall with mixed attribute set for
> exclude_kernel
> and exlude_hv.
>
> This change is breaking some applications
Hi Neil,
Thank you for the patch.
On Monday 03 Apr 2017 16:42:38 Neil Armstrong wrote:
> The HDMI TX controller support HPD and RXSENSE signaling from the PHY
> via it's STAT0 PHY interface, but some vendor PHYs can manage these
> signals independently from the controller, thus these STAT0 handli
101 - 200 of 944 matches
Mail list logo
