From: Shailendra Verma
The module end boundary check is not proper.The out of bound value
of module end can produce undesired results.
Signed-off-by: Shailendra Verma
Reviewed-by: Ravikant Bijendra Sharma
---
linux-4.3-rc6/arch/arm/mm/pageattr.c |2 +-
1 file changed, 1 insertion(+), 1
Hi,
- Original Message -
> From: "Jiri Kosina"
> To: "Simon Wood"
> Cc: linux-in...@vger.kernel.org, linux-kernel@vger.kernel.org, "Edwin"
> , "Michal Malý"
> , "elias vanderstuyft" ,
> "Benjamin Tissoires"
>
> Sent: Friday, October 30, 2015 2:51:47 PM
> Subject: Re: [RFC 1/5] INPUT:
Hi,
On (11/09/15 16:23), Joonsoo Kim wrote:
[..]
> +static inline int page_count(struct page *page)
> +{
> + return atomic_read(_head(page)->_count);
> +}
> +
> +static inline void set_page_count(struct page *page, int v)
> +{
> + atomic_set(>_count, v);
> +}
> +
> +/*
> + * Setup the
On 2015/11/7 15:56, Arthur Marsh wrote:
> Hi, I've run into a situation where I've been getting a lock-up a few
> seconds into the boot process on a machine with an ASUS A8V-MX
> motherboard, BIOS 050312/06/2005 with AMD Athlon(tm) 64 Processor
> 3200+ (single core) with kernel compiled in 32
- Original Message -
> From: "Elias Vanderstuyft"
> To: "Benjamin Tissoires"
> Cc: "Dmitry Torokhov" , "David Herrmann"
> , "Peter Hutterer"
> , "open list:HID CORE LAYER"
> , linux-kernel@vger.kernel.org
> Sent: Sunday, November 8, 2015 11:55:04 AM
> Subject: Re: [PATCH v3] Input:
* Sasha Levin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Ingo,
>
> Please pull three fixes for liblockdep. Just keeping up with kernel
> code changes and new gcc versions.
>
>
> Thanks,
> Sasha
>
> ===
>
> The following changes since commit
Add support for early printk by writing debug messages to the USB3
debug port. Users can use this type of early printk by specifying
kernel parameter of "earlyprintk=xdbc". This gives users a chance
of providing debug output.
Signed-off-by: Lu Baolu
---
Documentation/kernel-parameters.txt | 1
xHCI debug capability (DbC) is an optional functionality provided
by an xHCI host controller. Software learns this capability by
walking through the extended capability list in mmio of the host.
This patch introduces the code to probe and initialize the debug
capability hardware during early
"printk" is not suitable for dbc debugging especially when console
is in usage. This patch adds a debug buffer in dbc driver and puts
the debug messages in this local buffer. The debug buffer could be
dumped whenever the console is not in use. This part of code will
not be visible unless DBC_DEBUG
This patch adds a sysfs file for users to check 1) whether the debug
capability is implemented by hardware; 2) if supported, which state
does it stay at.
With a host that supports debug port, a file named "debug_port_state"
will be created under the device sysfs directory. Reading this file
will
This patch series adds support for early printk through USB3 debug port.
USB3 debug port is described in xHCI specification as an optional extended
capability.
The first patch adds a file in sysfs, through which users can check
whether the debug capability is supported by a specific host
On Intel platform, if the debug target is connected with debug
host, enabling DCE bit in command register leads to a hung bus
state. In the hung state, the host system will not see a port
connected status bit set. Hence debug target fails to be probed.
The state could be resolved by performing a
On Fri, 30 Oct 2015, Mike Kravetz wrote:
>
> The 'next = start' code is actually from the original truncate_hugepages
> routine. This functionality was combined with that needed for hole punch
> to create remove_inode_hugepages().
>
> The following code was in truncate_hugepages:
>
>
2015-11-05 21:17 GMT+09:00 Catalin Marinas :
> On Thu, Nov 05, 2015 at 08:45:08PM +0900, Joonsoo Kim wrote:
>> 2015-11-05 19:32 GMT+09:00 Catalin Marinas :
>> > On ARM we have a notion of cache writeback granule (CWG) which tells us
>> > "the maximum size of memory that can be overwritten as a
After DbC setup, debug target needs to wait until tty driver and
application (e.g. mincom) on debug taget start. Otherwise, out
messages might be ignored.
This patch adds a ping/pong mechanism between debug target and
host. Debug target will be waiting there until user presses 'Y'
or 'y' in the
Hi Ulf,
Thanks for your answer.
On Fri, Nov 06, 2015 at 05:42:51PM +0100, Ulf Hansson wrote:
> On 6 November 2015 at 16:59, Ludovic Desroches
> wrote:
> > Hi,
> >
> > I would like to have some feedback for these two patches. I have two
> > questions.
> >
> > 1.
> >
> > To suppress the warnings
DbC might exit configured state in some cases (refer to 7.6.4.4 in
xHCI spec 1.1). Software needs detect and clear this situation by
clearing DCCTRL.DCR and wait until the DbC configured before read
or write oprations.
Signed-off-by: Lu Baolu
---
drivers/usb/early/xhci-dbc.c | 28
In case of endpoint stall, software is able to detect the situation
by reading DCCTRL.HIT or DCCTRL.HOT bits. DbC follows the normal USB
framework to handle endpoint stall. When software detects endpoint
stall situation, it should wait until endpoint is recovered before
read or write oprations.
Add Documentation/usb/xhci-dbc.txt. This document includes
development status and user guide for USB3 debug port.
Signed-off-by: Lu Baolu
---
Documentation/usb/xhci-dbc.txt | 325 +
MAINTAINERS| 1 +
drivers/usb/early/xhci-dbc.c |
This patch adds interfaces for bulk out and bulk in ops. These
interfaces could be used to implement early printk bootconsole
or hook to various system debuggers.
Signed-off-by: Lu Baolu
---
drivers/usb/early/xhci-dbc.c | 373 +++
xHCI compatible USB3 host controller may provide debug capability
which enables low-level system debug over USB. In order to probing
this debug capability, Linux kernel needs to map and access the
mmio of the host controller during early boot.
This patch adds permenent fixmap pages in
This patch add dbc debug device support in usb_debug driver.
Signed-off-by: Lu Baolu
Acked-by: Johan Hovold
---
drivers/usb/serial/usb_debug.c | 28 +---
1 file changed, 25 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/serial/usb_debug.c
On Mon, Nov 09, 2015 at 08:27:06AM +0100, LABBE Corentin wrote:
> sun4i-ss implementaton of md5/sha1 is via ahash algorithms.
> A recent change make impossible to load them without giving statesize.
> This patch specifiy statesize for sha1 and md5.
>
> Fixes: 8996eafdcbad ("crypto: ahash - ensure
From: Fu Wei
This driver bases on linux kernel watchdog framework, and
use "pretimeout" in the framework. It supports getting timeout and
pretimeout from parameter and FDT at the driver init stage.
In first timeout, the interrupt routine run panic to save
system context.
Signed-off-by: Fu Wei
From: Fu Wei
This can be a example of adding SBSA Generic Watchdog device node
into some dts files for the Soc which contains SBSA Generic Watchdog.
Acked-by: Arnd Bergmann
Signed-off-by: Fu Wei
---
arch/arm64/boot/dts/arm/foundation-v8.dts | 7 +++
1 file changed, 7 insertions(+)
diff
From: Fu Wei
This can be a example of adding SBSA Generic Watchdog device node
into some dts files for the Soc which contains SBSA Generic Watchdog.
Acked-by: Arnd Bergmann
Acked-by: Suravee Suthikulpanit
Tested-by: Suravee Suthikulpanit
Signed-off-by: Fu Wei
---
From: Fu Wei
Also update Documentation/watchdog/watchdog-kernel-api.txt to
introduce:
(1)the new elements in the watchdog_device and watchdog_ops struct;
(2)the new API "watchdog_init_timeouts"
Reasons:
(1)kernel already has two watchdog drivers are using "pretimeout":
From: Fu Wei
The sbsa-gwdt.txt documentation in devicetree/bindings/watchdog is for
introducing SBSA(Server Base System Architecture) Generic Watchdog
device node info into FDT.
Also add sbsa-gwdt introduction in watchdog-parameters.txt
Acked-by: Arnd Bergmann
Signed-off-by: Fu Wei
---
From: Fu Wei
This patchset:
(1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt
for FDT info of SBSA Generic Watchdog, and give two examples of
adding SBSA Generic Watchdog device node into the dts files:
foundation-v8.dts and amd-seattle-soc.dtsi.
Now, we have tracepoint in test_pages_isolated() to notify
pfn which cannot be isolated. But, in alloc_contig_range(),
some error path doesn't call test_pages_isolated() so it's still
hard to know exact pfn that causes allocation failure.
This patch change this situation by calling
cma allocation should be guranteeded to succeed, but, sometimes,
it could be failed in current implementation. To track down
the problem, we need to know which page is problematic and
this new tracepoint will report it.
Signed-off-by: Joonsoo Kim
---
include/trace/events/cma.h | 26
This is preparation step to report test failed pfn in new tracepoint
to analyze cma allocation failure problem. There is no functional change
in this patch.
Signed-off-by: Joonsoo Kim
---
mm/page_isolation.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git
CMA allocation should be guaranteed to succeed by definition, but,
unfortunately, it would be failed sometimes. It is hard to track down
the problem, because it is related to page reference manipulation and
we don't have any facility to analyze it.
This patch adds tracepoints to track down page
Success of CMA allocation largely depends on success of migration
and key factor of it is page reference count. Until now, page reference
is manipulated by direct calling atomic functions so we cannot follow up
who and where manipulate it. Then, it is hard to find actual reason
of CMA allocation
On 11/6/2015 20:00, Mark Brown wrote:
On Fri, Nov 06, 2015 at 09:38:09AM +0800, Sugar Zhang wrote:
+ /* refine capture channels */
+ if (!of_property_read_u32(node, "rockchip,capture-channels", )) {
+ if (val >= 2 && val <= 8)
+
On 11/09/2015 02:57 AM, Sinan Kaya wrote:
> The mpt2sas and mpt3sas drivers are spinning forever in
> their IRQ handlers if there are a lot of jobs queued up
> by the PCIe card. This handler is causing spikes for
> the rest of the system and sluggish behavior.
>
> Marking all MSI interrupts as
Sorry for the delay, I needed some time set aside to look through.
On Fri, 30 Oct 2015, Mike Kravetz wrote:
> Hugh Dickins pointed out problems with the new hugetlbfs fallocate
> hole punch code. These problems are in the routine remove_inode_hugepages
> and mostly occur in the case where there
On 11/09/2015 02:57 AM, Sinan Kaya wrote:
> Current code gives up when 32 bit DMA is not supported.
> This problem has been observed on systems without any
> memory below 4 gig.
>
> This patch tests 64 bit support before bailing out to find
> a working combination.
>
That feels decidedly odd.
On Fri, Oct 30, 2015 at 04:32:12PM -0700, Mike Kravetz wrote:
> Hugh Dickins pointed out problems with the new hugetlbfs fallocate
> hole punch code. These problems are in the routine remove_inode_hugepages
> and mostly occur in the case where there are holes in the range of
> pages to be
Fixed a comment style issue.
Signed-off-by: Gavin O'Leary
---
drivers/staging/wlan-ng/p80211wep.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/wlan-ng/p80211wep.c
b/drivers/staging/wlan-ng/p80211wep.c
index c363456..e9f990a 100644
---
On Mon, 9 Nov 2015, Dan Carpenter wrote:
> On Sun, Nov 08, 2015 at 10:24:49PM +, Julia Lawall wrote:
> > On Mon, 9 Nov 2015, Dan Carpenter wrote:
> >
> > > Cool. So, in grsec they use a GCC plugin to make these const
> > > automatically since they only contain function pointers. There
On 09.11.2015 14:54, Alim Akhtar wrote:
> Hi Krzysztof,
>
> On 11/07/2015 08:39 AM, Krzysztof Kozlowski wrote:
>> W dniu 07.11.2015 o 07:33, Rob Herring pisze:
>>> On Fri, Oct 30, 2015 at 11:55:31AM +0530, Alim Akhtar wrote:
From: Thomas Abraham
Add dt-binding documentation for
Correct typo in tools/testing/selftests/futex/README.
Signed-off-by: Wei Jiangang
---
tools/testing/selftests/futex/README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/futex/README
b/tools/testing/selftests/futex/README
index
Hi Linus,
Here are the arch/nios2 update for v4.4.
Please consider pulling.
Regards
Ley Foon
The following changes since commit 6a13feb9c82803e2b815eca72fa7a9f5561d7861:
Linux 4.3 (2015-11-01 16:05:25 -0800)
are available in the git repository at:
registering the device with NULL pointer can lead to crash,
hence fixing it
Signed-off-by: Saurabh Sengar
---
> Andy Shevchenko wrote:
> Hmm… Why not just checking it before an register attempt? I think user
> is in right to know as many problems as they have at one shot, with
> your patch if
Free buffer to avoid memory leak upon failure occurs.
Signed-off-by: Wei Jiangang
---
tools/usb/ffs-aio-example/multibuff/device_app/aio_multibuff.c | 4
tools/usb/ffs-aio-example/simple/device_app/aio_simple.c | 4
2 files changed, 8 insertions(+)
diff --git
The basic flow for iommu_group_for_dev is:
iommu_group_get_for_dev
|-> iommu_group_get : increase reference count by 1.
return group;
|-> ops->device_group : Init/increase reference count to/by 1.
iommu_group_add_device : Increase reference count by
On Sun, Nov 8, 2015 at 9:47 PM, Zhenzhong Duan
wrote:
> Tried nr_cpus=4, works.
>
nr_cpus and maxcpus are different.
maxcpus=4 means kernel will only bring up 4 cpus, but other cpus still
can be brought up online.
if there are more cpu are there according acpi MADT.
nr_cpus=4 that means 4 is
On Mon, Nov 9, 2015 at 10:28 AM, William Breathitt Gray
wrote:
> On 11/08/2015 06:53 PM, Alexandre Courbot wrote:
>> Apart from that this patch seems harmless and the repositioning of
>> some constant declarations is also welcome.
>
> I'll create a separate patch to reposition the constant
On Mon, 2015-11-09 at 08:42 +0300, Dan Carpenter wrote:
> On Sun, Nov 08, 2015 at 10:24:49PM +, Julia Lawall wrote:
> > On Mon, 9 Nov 2015, Dan Carpenter wrote:
> >
> > > Cool. So, in grsec they use a GCC plugin to make these const
> > > automatically since they only contain function
Hi Krzysztof,
On 11/07/2015 08:39 AM, Krzysztof Kozlowski wrote:
W dniu 07.11.2015 o 07:33, Rob Herring pisze:
On Fri, Oct 30, 2015 at 11:55:31AM +0530, Alim Akhtar wrote:
From: Thomas Abraham
Add dt-binding documentation for s2mps15 PMIC device. The s2mps15 device
is similar to s2mps11/14
The folded callchain mode is to print all chains in a single line.
Currently perf report --gtk doesn't support folded callchains. Like
flat callchains, only leaf nodes are added to the final rbtree so it
should show entries in parent nodes.
Cc: Brendan Gregg
Cc: Pekka Enberg
Signed-off-by:
The flat callchain mode is to print all chains in a simple flat
hierarchy so make it easy to see.
Currently perf report --gtk doesn't show flat callchains properly. With
flat callchains, only leaf nodes are added to the final rbtree so it
should show entries in parent nodes. To do that, add
The flat callchain mode is to print all chains in a single, simple
hierarchy so make it easy to see.
Currently perf report --tui doesn't show flat callchains properly. With
flat callchains, only leaf nodes are added to the final rbtree so it
should show entries in parent nodes. To do that, add
Tried nr_cpus=4, works.
[root@rwssq01 ~]# cat /sys/devices/system/cpu/possible
0-3
[root@rwssq01 ~]# cat /sys/devices/system/cpu/present
0-3
[root@rwssq01 ~]# uname -a
Linux rwssq01.us.oracle.com 3.8.13-44.1.1.el6uek.x86_64 #2 SMP Wed Sep
10 06:10:25 PDT 2014 x86_64 x86_64 x86_64 GNU/Linux
The folded callchain mode is to print all chains in a single line.
Currently perf report --tui doesn't support folded callchains. Like
flat callchains, only leaf nodes are added to the final rbtree so it
should show entries in parent nodes. To do that, add flat_val list to
struct callchain_node
It's to track the count of occurrences of the callchains.
Acked-by: Brendan Gregg
Acked-by: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/perf/util/callchain.c | 10 ++
tools/perf/util/callchain.h | 7 +++
2 files changed, 17 insertions(+)
diff --git
This function is to print a single callchain list entry. As this
function will be used by other function, factor out to a separate
function.
Cc: Brendan Gregg
Signed-off-by: Namhyung Kim
---
tools/perf/ui/browsers/hists.c | 72 ++
1 file changed, 45
This is a preparation to support for printing other type of callchain
value like count or period.
Acked-by: Brendan Gregg
Signed-off-by: Namhyung Kim
---
tools/perf/ui/browsers/hists.c | 8 +---
tools/perf/ui/gtk/hists.c | 8 ++--
tools/perf/ui/stdio/hist.c | 35
Hello,
This is what Brendan requested on the perf-users mailing list [1] to
support FlameGraphs [2] more efficiently. This patchset adds a few
more callchain options to adjust the output for it.
* changes in v5)
- honor field separator from -t option
- add support for TUI and GTK
*
Now -g/--call-graph option supports how to display callchain values.
Possible values are 'percent', 'period' and 'count'. The percent is
same as before and it's the default behavior. The period displays the
raw period value rather than the percentage. The count displays the
number of
Add new call chain option (-g) 'folded' to print callchains in a line.
The callchains are separated by semicolons, and preceded by (absolute)
percent values and a space.
For example, following 20 lines can be printed in 3 lines with the
folded output mode;
$ perf report -g flat --no-children |
For some reason, it sometimes wants to hide hist lines but only wants to
see callchains. To do that, add virtual 'none' field name to hide all
hist lines. It should be used solely and only meaningful on --stdio.
WIP on TUI
Cc: Brendan Gregg
Signed-off-by: Namhyung Kim
---
On 11/9/2015 12:24 AM, Jiang Liu wrote:
+ u32 possible[ACPI_PCI_LINK_MAX_POSSIBLE];
>u8 initialized:1;
>u8 reserved:7;
> };
Hi Sinan,
This data structure become some sort of big, any idea to reduce
memory consumption?
Thanks,
Gerry
Hi Gerry,
There are two constants
This series contain two patches, first is to optimize Mediatek I2C driver to
use WRRD
if hardware support auto restart. Because auto restart will issue auto restart
interrupt, change to use WRRD can reduce interrupt latency. The second is to fix
multi transfer error in high speed mode. If
For platform with auto restart support, when doing i2c multi transfer
in high speed, for example, doing write-then-read transfer, the master
code will occupy the first transfer, and the second transfer will be
the read transfer, the write transfer will be discarded. So we should
first send the
For platform with auto restart support, between every transfer,
i2c controller will trigger an interrupt and SW need to handle
it to start new transfer. When doing write-then-read transfer,
instead of restart mechanism, using WRRD mode to have controller
send both transfer in one request to reduce
On Sun, Nov 08, 2015 at 10:24:49PM +, Julia Lawall wrote:
> On Mon, 9 Nov 2015, Dan Carpenter wrote:
>
> > Cool. So, in grsec they use a GCC plugin to make these const
> > automatically since they only contain function pointers. There about
> > 100 struct types marked as __no_const. Kees
Hi Will,
On Fri, Nov 06, 2015 at 12:23:39PM +, Will Deacon wrote:
>On Wed, Nov 04, 2015 at 10:48:28AM +0800, Peng Fan wrote:
>> On Tue, Nov 03, 2015 at 01:17:34PM +, Will Deacon wrote:
>> >On Tue, Nov 03, 2015 at 08:59:17PM +0800, Peng Fan wrote:
>> >> iommu_group_alloc will initialize
From: Seungwon Jeon
This adds Exynos Universal Flash Storage (UFS) Host Controller DT bindings.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
.../devicetree/bindings/ufs/ufs-exynos.txt | 104
1 file changed, 104 insertions(+)
create mode 100644
From: Seungwon Jeon
Some host controller needs specific handling before/after
(un)hibernation, This change adds specific callback function
to support vendor's implementation.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c | 33
From: Seungwon Jeon
This patch introduces Exynos UFS host controller driver,
which mainly handles vendor-specific operations including
link startup, power mode change and hibernation/unhibernation.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/Kconfig |
From: Seungwon Jeon
This makes ufshcd_config_pwr_mode non-static so that other vendors
like exynos can use the same.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c |5 ++---
drivers/scsi/ufs/ufshcd.h |2 ++
2 files changed, 4 insertions(+), 3
On Sun, Nov 8, 2015 at 7:31 PM, Dexuan Cui wrote:
>> From: David Miller [mailto:da...@davemloft.net]
>> Sent: Monday, November 9, 2015 11:24
>> ...
>> > Thanks, David!
>> > I understand 1 TX queue is the bottleneck (however in Simon's
>> > test, TX=1 => 36.7Gb/s, TX=8 => 37.7 Gb/s, so it looks
From: Seungwon Jeon
Some host controller needs nexus type information for handling
command. This change adds specific callback function to support
vendor's implementation.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c |3 +++
From: Seungwon Jeon
Some host controller doesn't support host controller enable via HCE.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c | 75 +++--
drivers/scsi/ufs/ufshcd.h |5 +++
2 files changed, 78
From: Seungwon Jeon
Some host controller supports interrupt aggregation, but doesn't
allow to reset counter and timer by s/w.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c |3 ++-
drivers/scsi/ufs/ufshcd.h |6 ++
2 files changed, 8
From: Seungwon Jeon
In the right behavior, setting the bit to '0' indicates clear and
'1' indicates no change. If host contoller handles this the other way,
UFSHCI_QUIRK_BROKEN_REQ_LIST_CLR can be used.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c |
From: Seungwon Jeon
UTRD(UTP Transfer Request Descriptor)'s field such as offset/length,
especially response's has DWORD expression. This quirk can be specified
for host controller not to conform standard.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c
From: Seungwon Jeon
This patch introduces Exynos UFS PHY driver. This driver
supports to deal with phy calibration and power control
according to UFS host driver's behavior.
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
Cc: Kishon Vijay Abraham I
---
drivers/phy/Kconfig
Adds exynos UFS PHY device tree bindings information.
Signed-off-by: Alim Akhtar
---
.../devicetree/bindings/phy/samsung-phy.txt| 22
1 file changed, 22 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
This patch-set introduces UFS (Universal Flash Storage) host support
for Samsung Exynos SoC. Mostly, it consists of UFS PHY and host specific driver.
And it also contains some quirks handling for Exynos.
NOTE: ** This series has a dependency on [4]. **
-Changes since v4:
* Removed platform
On 2015/11/9 0:07, Sinan Kaya wrote:
> The ACPI compiler uses the extended format when
> used interrupt numbers are greater than 256.
> The PCI link code currently only supports simple
> interrupt format. The IRQ numbers are represented
> using 32 bits when extended IRQ syntax. This patch
>
This patch handles add_disk() return value.
Earlier add_disk() function doesn't handle error
cases, now it is added, so the callers of this function
should also handle it.
Signed-off-by: Vishnu Pratap Singh
--- Verfied on X86 based ubuntu machine.
--- This patch depends on [PATCH 1/8]
The current driver is default to register the two thermal sensors
in probe since some SoCs maybe only have one sensor for thermal.
In some cases, the channel 0 is not always the cpu or gpu sensor.
So add the channel can be configured for sensors.
Signed-off-by: Caesar Wang
---
Changes in v4:
This patch enable the TS-ADC.
When a thermal temperature is invoked use the CRU to reset the chip
on R88 board. TSHUT is low active on this board.
Signed-off-by: Caesar Wang
Acked-by: Eduardo Valentin
---
Changes in v4:
- Missing the ";" caused compile error.
Changes in v3: None
Changes in
This patch add the thermal needed info on RK3368.
Meanwhile, support the trips to throttle for thermal.
Signed-off-by: Caesar Wang
Acked-by: Eduardo Valentin
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- fix a copy wrong name.
Changes in v1:
- support the opt gpio pinctrl
Signed-off-by: Caesar Wang
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- As Eduardo comments on patch v1, split in smaller changes.
Changes in v1: None
drivers/thermal/rockchip_thermal.c | 22 +-
1 file changed, 13 insertions(+), 9 deletions(-)
diff --git
As Temperature is currently represented as int not long in the thermal
framework since use int intead of unsigned long/long to represent
temperature to avoid bogus overheat detection when negative temperature
reported.
Signed-off-by: Caesar Wang
---
Changes in v4:
- fix the warning from the
The conversion table has the adc value and temperature.
In fact, the adc value only has the increment or decrement mode in
conversion table.
Moment, we can add the sort mode to be better support the *code_to_temp*
for differenr SoCs.
Signed-off-by: Caesar Wang
---
Changes in v4:
- rename the
This patchset add the thermal for RK3368 dts,
Since the two CPU clusters, with four CPU core for each cluster,
One cluster is optimized for high-performance(big cluster) and the othe
is optimized for low power(little cluster).
This patch adds the second order for thermal throttle, and the
We should make the conversion table in as a parameter since the different
SoCs have the different conversionion table.
Signed-off-by: Caesar Wang
---
Changes in v4: None
Changes in v3:
- As Eduardo comments, let's change data_mask type with 'u32' instead of
'unsigned long'.
Changes in v2:
-
This patchset attempts to new compatible for thermal founding
on RK3368 SoCs.
Signed-off-by: Caesar Wang
Acked-by: Rob Herring
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
Changes in v1:
- %s/thermal/rockchip-thermal in subject.
The RK3368 SoCs support to 2 channel TS-ADC, the temperature criteria
of each channel can be configurable.
The system has two Temperature Sensors, channel 0 is for CPU,
and channel 1 is for GPU.
Signed-off-by: Caesar Wang
---
Changes in v4:
- :%s/sort_flag/mode.
- rename the 'drivers' to
Thank you all for providing inputs and comments on previous versions of
this patchset.
Especially thanks to the (Eduardo, Dmitry, Heiko,).
This series patchs are working for RK3368 on Rockchip platform.
-
This patchset are based on linus master branch.
Note: Need add the following
Will,
On Fri, Nov 6, 2015 at 4:17 AM, Will Deacon wrote:
> On Tue, Nov 03, 2015 at 11:00:20AM -0800, Doug Anderson wrote:
>> Hi,
>
> Hey Doug,
>
>> When CPUs are hard locked up, they are often found at:
>>
>> v7_coherent_kern_range+0x58/0x74
>> or
>> v7wbi_flush_user_tlb_range+0x30/0x38
>>
On 11/09/2015 01:11 AM, Michael S. Tsirkin wrote:
> On Tue, Sep 15, 2015 at 02:41:53PM +0800, Jason Wang wrote:
>> Hi:
>>
>> This series fixes two issues of fast mmio eventfd:
>>
>> 1) A single iodev instance were registerd on two buses: KVM_MMIO_BUS
>>and KVM_FAST_MMIO_BUS. This will cause
From: John L. Hammond
Remove comment about tracefile handling for user land
version of libcfs that no longer exist. Broken out of
patch http://review.whamcloud.com/11983.
Signed-off-by: John L. Hammond
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2675
Reviewed-on:
From: John L. Hammond
Move the definition of the trace buffer type enum in
libcfs/libcfs/tracefile.h. Remove the then unneeded headers
libcfs/libcfs/linux/linux-tracefile.h and
libcfs/libcfs/posix/posix-tracefile.h.
Signed-off-by: John L. Hammond
Intel-bug-id:
Makes it easier to handle init vs core cleanly, though the change is
fairly invasive across random architectures.
It simplifies the rbtree code immediately, however, while keeping the
core data together in the same cachline (now iff the rbtree code is
enabled).
Cc: Peter Zijlstra
Cc: Josh
1 - 100 of 834 matches
Mail list logo
