On Fri, Jul 14, 2017 at 02:40:04PM -0700, Stephen Boyd wrote:
>
> @@ -175,6 +176,10 @@ static int host_start(struct ci_hdrc *ci)
> if (ci_otg_is_fsm_mode(ci)) {
> otg->host = >self;
> hcd->self.otg_port = 1;
> + } else {
> +
On Fri, Jul 14, 2017 at 02:40:04PM -0700, Stephen Boyd wrote:
>
> @@ -175,6 +176,10 @@ static int host_start(struct ci_hdrc *ci)
> if (ci_otg_is_fsm_mode(ci)) {
> otg->host = >self;
> hcd->self.otg_port = 1;
> + } else {
> +
Previously i.MX SPI controller only works in Master mode.
This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI
controller to work also in Slave mode.
Currently SPI Slave mode support patch has the following limitations:
1. The stale data in RXFIFO will be dropped when the Slave does any new
Previously i.MX SPI controller only works in Master mode.
This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI
controller to work also in Slave mode.
Currently SPI Slave mode support patch has the following limitations:
1. The stale data in RXFIFO will be dropped when the Slave does any new
On Wed, Jul 12, 2017 at 7:31 AM, Jiri Olsa wrote:
> On Tue, Jul 11, 2017 at 04:52:51PM -0700, David Carrillo-Cisneros wrote:
>> v5: - Fix buffer leaking and size changes in
>> perf_event__synthesize_features.
>> - Remove unnecessary renaming.
>> - Remove extra tabs
On Wed, Jul 12, 2017 at 7:31 AM, Jiri Olsa wrote:
> On Tue, Jul 11, 2017 at 04:52:51PM -0700, David Carrillo-Cisneros wrote:
>> v5: - Fix buffer leaking and size changes in
>> perf_event__synthesize_features.
>> - Remove unnecessary renaming.
>> - Remove extra tabs in
On Tue, Jul 11, 2017 at 6:39 PM, David Ahern wrote:
> On 7/11/17 5:52 PM, David Carrillo-Cisneros wrote:
> ...
>> (This is a rebased and updated version of Stephane Eranian's version
>> in https://patchwork.kernel.org/patch/1499081/)
>
> ...
>> With this series, it is possible
On Tue, Jul 11, 2017 at 6:39 PM, David Ahern wrote:
> On 7/11/17 5:52 PM, David Carrillo-Cisneros wrote:
> ...
>> (This is a rebased and updated version of Stephane Eranian's version
>> in https://patchwork.kernel.org/patch/1499081/)
>
> ...
>> With this series, it is possible to get:
>> $
On Wed, Jul 12, 2017 at 12:38 AM, Jiri Olsa wrote:
> On Tue, Jul 11, 2017 at 05:32:40PM -0700, David Carrillo-Cisneros wrote:
>> On Tue, Jun 13, 2017 at 11:54 AM, Jiri Olsa wrote:
>> > On Mon, Jun 12, 2017 at 09:29:31PM -0700, David Carrillo-Cisneros wrote:
>>
On Wed, Jul 12, 2017 at 12:38 AM, Jiri Olsa wrote:
> On Tue, Jul 11, 2017 at 05:32:40PM -0700, David Carrillo-Cisneros wrote:
>> On Tue, Jun 13, 2017 at 11:54 AM, Jiri Olsa wrote:
>> > On Mon, Jun 12, 2017 at 09:29:31PM -0700, David Carrillo-Cisneros wrote:
>> >
>> > SNIP
>> >
>> >>
>> >> void
On Monday 17 July 2017 06:03 PM, Greg KH wrote:
> On Sat, Jul 15, 2017 at 01:21:54PM +0530, suni...@techveda.org wrote:
>> From: Suniel Mahesh
>>
>> It is recommended to use managed function devm_kzalloc, which
>> simplifies driver cleanup paths and driver code.
>> This
On Monday 17 July 2017 06:03 PM, Greg KH wrote:
> On Sat, Jul 15, 2017 at 01:21:54PM +0530, suni...@techveda.org wrote:
>> From: Suniel Mahesh
>>
>> It is recommended to use managed function devm_kzalloc, which
>> simplifies driver cleanup paths and driver code.
>> This patch does the following:
On Mon, Jul 17, 2017 at 03:39:07PM +0200, Rafael J. Wysocki wrote:
> > Sorry, I should describe more.
> >
> > Let's take USB bus as an example, when the new USB device is at the
> > host port, the device structure at device model is not created until
> > it is discoverable by the USB bus. If this
On Mon, Jul 17, 2017 at 03:39:07PM +0200, Rafael J. Wysocki wrote:
> > Sorry, I should describe more.
> >
> > Let's take USB bus as an example, when the new USB device is at the
> > host port, the device structure at device model is not created until
> > it is discoverable by the USB bus. If this
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
drivers/tty/serial/8250/8250_early.c | 8
1
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
drivers/tty/serial/omap-serial.c | 13 ++---
1
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
drivers/tty/serial/8250/8250_ingenic.c | 8
1
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
drivers/tty/serial/xilinx_uartps.c | 2 +-
1 file
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
The earlycon would be alive outside the init code in these cases:
1/ we have keep_bootcon in cmdline.
2/ we don't have a real console to switch to.
So remove the __init marking to avoid invalid memory access.
Signed-off-by: Jeffy Chen
---
drivers/tty/serial/arc_uart.c | 4 ++--
1 file
I was testing earlycon with 8250 dw serial console. And it hangs in
these cases:
1/ kernel hang when calling early write function after free_initmem:
a) the earlycon not disabled after the init code(due to keep_bootcon or
not specify a real console to switch to)
b) the early write func is
I was testing earlycon with 8250 dw serial console. And it hangs in
these cases:
1/ kernel hang when calling early write function after free_initmem:
a) the earlycon not disabled after the init code(due to keep_bootcon or
not specify a real console to switch to)
b) the early write func is
Do not proceed if write_padded error failed.
Also, add comments to remind that the return value of write_*
functions in util/header.c is an erro code and not the number
of bytes written.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 6 +-
1 file
Do not proceed if write_padded error failed.
Also, add comments to remind that the return value of write_*
functions in util/header.c is an erro code and not the number
of bytes written.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 6 +-
1 file changed, 5
Make buf in helper function "writen" constant to simplify
the life of its callers.
This requires to hack a cast of buf prior to passing it to "ion"
which is simpler than the alternative of reworking the "ion"
function to provide a read and a write paths, the latter with
constant buf argument.
Now that writen takes a const buffer, use it in do_write instead
of duplicating its functionality.
Export do_write to use it consistently in header.c and
build_id.c .
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/build-id.c | 2 +-
tools/perf/util/header.c |
Make buf in helper function "writen" constant to simplify
the life of its callers.
This requires to hack a cast of buf prior to passing it to "ion"
which is simpler than the alternative of reworking the "ion"
function to provide a read and a write paths, the latter with
constant buf argument.
Now that writen takes a const buffer, use it in do_write instead
of duplicating its functionality.
Export do_write to use it consistently in header.c and
build_id.c .
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/build-id.c | 2 +-
tools/perf/util/header.c | 14 +-
Introduce struct feat_fd. This patch uses it as a wrapper
around fd in write_* functions for feature headers. Next
patches will extend its functionality to other feature
header functions.
This patch does not change behavior.
Signed-off-by: David Carrillo-Cisneros
---
Introduce struct feat_fd. This patch uses it as a wrapper
around fd in write_* functions for feature headers. Next
patches will extend its functionality to other feature
header functions.
This patch does not change behavior.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/build-id.c
Most callers of readn in perf header read either a 32 or a 64 bits
number, error check it and swap it, if necessary.
Create do_read_u32 and do_read_u64 to simplify these use cases.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 210
struct perf_file_section is used in process_##_feat as container for
size and offset in the file descriptor. These attributes are meaninful
in pipe-mode but struct perf_file_section is not.
Add offset and size variables to struct feat_fd to store
perf_file_section's values in file-mode. Later on,
Most callers of readn in perf header read either a 32 or a 64 bits
number, error check it and swap it, if necessary.
Create do_read_u32 and do_read_u64 to simplify these use cases.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 210
struct perf_file_section is used in process_##_feat as container for
size and offset in the file descriptor. These attributes are meaninful
in pipe-mode but struct perf_file_section is not.
Add offset and size variables to struct feat_fd to store
perf_file_section's values in file-mode. Later on,
As preparation for using header records in pipe-mode, replace
int fd with struct feat_fd ff in process functions for all header
record types.
This patch does not change behavior.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 164
As preparation for using header records in pipe-mode, replace
int fd with struct feat_fd ff in process functions for all header
record types.
This patch does not change behavior.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 164
In pipe-mode, we will operate over a buffer instead of a file descriptor
but write_pmu_mappings uses lseek to move over the perf.data file.
Refactor write_pmu_mappings to avoid the usage of lseek and allow
reusing the same logic in pipe-mode (next patch).
Signed-off-by: David Carrillo-Cisneros
In pipe-mode, we will operate over a buffer instead of a file descriptor
but write_pmu_mappings uses lseek to move over the perf.data file.
Refactor write_pmu_mappings to avoid the usage of lseek and allow
reusing the same logic in pipe-mode (next patch).
Signed-off-by: David Carrillo-Cisneros
Add header record types to pipe-mode, reusing the functions
used in file-mode and leveraging the new struct feat_fd.
For alignment, check that synthesized events don't exceed
pagesize.
Add the perf_event__synthesize_feature event call back to
process the new header records.
Before this patch:
Add header record types to pipe-mode, reusing the functions
used in file-mode and leveraging the new struct feat_fd.
For alignment, check that synthesized events don't exceed
pagesize.
Add the perf_event__synthesize_feature event call back to
process the new header records.
Before this patch:
As preparation for using header records in-pipe mode, replace
int fd with struct feat_fd ff in read functions for all header
record types.
This patch does not change behavior.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 101
As preparation for using header records in-pipe mode, replace
int fd with struct feat_fd ff in read functions for all header
record types.
This patch does not change behavior.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 101
There are three FEAT_OP* macros:
- FEAT_OPA: for features without process record.
- FEAT_OPP: for features with process record.
- FEAT_OPF: like FEAT_OPP but to show only if show_full_info flags
is set.
To add pipe-mode headers we need yet another variation of the macros
(one to specify
Extend struct feat_fd to use a temporal buffer in pipe-mode, instead
of perf.data's file descriptor.
The header features build_id and aux_trace already have logic to
print in file-mode that heavily rely on lseek the file. For now, leave
such features inactive in pipe-mode and print a warning if
As preparation for using header records in pipe mode, replace
int fd with struct feat_fd ff in print functions for all header
record types.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 102 ++-
1 file
There are three FEAT_OP* macros:
- FEAT_OPA: for features without process record.
- FEAT_OPP: for features with process record.
- FEAT_OPF: like FEAT_OPP but to show only if show_full_info flags
is set.
To add pipe-mode headers we need yet another variation of the macros
(one to specify
Extend struct feat_fd to use a temporal buffer in pipe-mode, instead
of perf.data's file descriptor.
The header features build_id and aux_trace already have logic to
print in file-mode that heavily rely on lseek the file. For now, leave
such features inactive in pipe-mode and print a warning if
As preparation for using header records in pipe mode, replace
int fd with struct feat_fd ff in print functions for all header
record types.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 102 ++-
1 file changed, 47
Add event descriptor to perf header output in pipe-mode.
After this patch:
$ perf record -e cycles sleep 1 | perf report --header
#
# captured on: Mon Jun 5 22:52:13 2017
#
#
# hostname : lphh20
# os release : 4.3.5-smp-801.43.0.0
# perf version :
Add event descriptor to perf header output in pipe-mode.
After this patch:
$ perf record -e cycles sleep 1 | perf report --header
#
# captured on: Mon Jun 5 22:52:13 2017
#
#
# hostname : lphh20
# os release : 4.3.5-smp-801.43.0.0
# perf version :
Add show_feat_hdr to control level of printed information
of feature headers.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/builtin-report.c | 4
tools/perf/builtin-script.c | 3 +++
tools/perf/util/tool.h | 7 +++
3 files changed, 14 insertions(+)
Simplify code by adding a macro to handle the common case
of processing header features that are a simple string.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 65 +---
1 file changed, 17 insertions(+), 48
v6: - Avoid buffer resize that would overflow event's header size.
v5: - Fix buffer leaking and size changes in
perf_event__synthesize_features.
- Remove unnecessary renaming.
- Remove extra tabs in do_write_string.
v4: - Limit write_* functions to page_size.
- Fixed bugs spotted
Add show_feat_hdr to control level of printed information
of feature headers.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/builtin-report.c | 4
tools/perf/builtin-script.c | 3 +++
tools/perf/util/tool.h | 7 +++
3 files changed, 14 insertions(+)
diff --git
Simplify code by adding a macro to handle the common case
of processing header features that are a simple string.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/header.c | 65 +---
1 file changed, 17 insertions(+), 48 deletions(-)
diff
v6: - Avoid buffer resize that would overflow event's header size.
v5: - Fix buffer leaking and size changes in
perf_event__synthesize_features.
- Remove unnecessary renaming.
- Remove extra tabs in do_write_string.
v4: - Limit write_* functions to page_size.
- Fixed bugs spotted
ifr name is assumed to be a valid string by the kernel, but nothing
was forcing username to pass a valid string.
In turn, this would cause panics as we tried to access the string
past it's valid memory.
Signed-off-by: Sasha Levin
---
net/core/dev_ioctl.c | 2 ++
ifr name is assumed to be a valid string by the kernel, but nothing
was forcing username to pass a valid string.
In turn, this would cause panics as we tried to access the string
past it's valid memory.
Signed-off-by: Sasha Levin
---
net/core/dev_ioctl.c | 2 ++
2 files changed, 3
Currently the hikey dsi logic cannot generate accurate byte
clocks values for all pixel clock values. Thus if a mode clock
is selected that cannot match the calculated byte clock, the
device will boot with a blank screen.
This patch uses the new mode_valid callback (many thanks to
Jose Abreu for
Currently the hikey dsi logic cannot generate accurate byte
clocks values for all pixel clock values. Thus if a mode clock
is selected that cannot match the calculated byte clock, the
device will boot with a blank screen.
This patch uses the new mode_valid callback (many thanks to
Jose Abreu for
v10:
According to Jiri Olsa's comment, update the patch
"perf/x86/intel: Record branch type". Set the branch_map
array to be static. The previous version has it on stack
then makes the compiler to create it every time when the
function gets called.
Other patches have been
v10:
According to Jiri Olsa's comment, update the patch
"perf/x86/intel: Record branch type". Set the branch_map
array to be static. The previous version has it on stack
then makes the compiler to create it every time when the
function gets called.
Other patches have been
Perf already has support for disassembling the branch instruction
and using the branch type for filtering. The patch just records
the branch type in perf_branch_entry.
Before recording, the patch converts the x86 branch type to
common branch type.
Change log
--
v10: Set the branch_map
The branch info such as predicted/cycles/... are printed at the
callchain entries.
For example: perf report --branch-history --no-children --stdio
--1.07%--main div.c:39 (predicted:52.4% cycles:1 iterations:17)
main div.c:44 (predicted:52.4% cycles:1)
main
Perf already has support for disassembling the branch instruction
and using the branch type for filtering. The patch just records
the branch type in perf_branch_entry.
Before recording, the patch converts the x86 branch type to
common branch type.
Change log
--
v10: Set the branch_map
The branch info such as predicted/cycles/... are printed at the
callchain entries.
For example: perf report --branch-history --no-children --stdio
--1.07%--main div.c:39 (predicted:52.4% cycles:1 iterations:17)
main div.c:44 (predicted:52.4% cycles:1)
main
Create new util/branch.c and util/branch.h to contain the common
branch functions. Such as:
branch_type_count(): Count the numbers of branch types
branch_type_name() : Return the name of branch type
branch_type_stat_display(): Display branch type statistics info
branch_type_str(): Construct the
Create new util/branch.c and util/branch.h to contain the common
branch functions. Such as:
branch_type_count(): Count the numbers of branch types
branch_type_name() : Return the name of branch type
branch_type_stat_display(): Display branch type statistics info
branch_type_str(): Construct the
Show the branch type statistics at the end of perf report --stdio.
For example:
perf report --stdio
COND_FWD: 28.5%
COND_BWD: 9.4%
CROSS_4K: 0.7%
CROSS_2M: 14.1%
COND: 37.9%
UNCOND: 0.2%
IND: 6.7%
CALL: 26.5%
RET: 28.7%
SYSRET: 0.0%
The branch types are:
Show the branch type statistics at the end of perf report --stdio.
For example:
perf report --stdio
COND_FWD: 28.5%
COND_BWD: 9.4%
CROSS_4K: 0.7%
CROSS_2M: 14.1%
COND: 37.9%
UNCOND: 0.2%
IND: 6.7%
CALL: 26.5%
RET: 28.7%
SYSRET: 0.0%
The branch types are:
Show branch type in callchain entry. The branch type is printed
with other LBR information (such as cycles/abort/...).
For example:
perf record -g -j any,save_type
perf report --branch-history --stdio --no-children
38.50% div.c:45[.] maindiv
|
The option indicates the kernel to save branch type during sampling.
One example:
perf record -g --branch-filter any,save_type
Change log
--
v10: Not changed.
v9: Not changed.
v8: Not changed.
v7: Not changed.
v6: Not changed.
v5: Not changed.
Signed-off-by: Jin Yao
Show branch type in callchain entry. The branch type is printed
with other LBR information (such as cycles/abort/...).
For example:
perf record -g -j any,save_type
perf report --branch-history --stdio --no-children
38.50% div.c:45[.] maindiv
|
The option indicates the kernel to save branch type during sampling.
One example:
perf record -g --branch-filter any,save_type
Change log
--
v10: Not changed.
v9: Not changed.
v8: Not changed.
v7: Not changed.
v6: Not changed.
v5: Not changed.
Signed-off-by: Jin Yao
---
It is often useful to know the branch types while analyzing branch
data. For example, a call is very different from a conditional branch.
Currently we have to look it up in binary while the binary may later
not be available and even the binary is available but user has to take
some time. It is
It is often useful to know the branch types while analyzing branch
data. For example, a call is very different from a conditional branch.
Currently we have to look it up in binary while the binary may later
not be available and even the binary is available but user has to take
some time. It is
The explanation for the endpoint ID numbering scheme is convoluted
and hard to understand.
This patch aims to improve the readability of it by combining the
existing two paragraphs, while also providing a diagram example,
and how endpoints should be numbered based on that example.
Signed-off-by:
The explanation for the endpoint ID numbering scheme is convoluted
and hard to understand.
This patch aims to improve the readability of it by combining the
existing two paragraphs, while also providing a diagram example,
and how endpoints should be numbered based on that example.
Signed-off-by:
Greetings Linux
http://biztagious.com/carrello.php?wrong=27wm0vssepacr9a1b
Chagri
Greetings Linux
http://biztagious.com/carrello.php?wrong=27wm0vssepacr9a1b
Chagri
On 07/18/2017 09:12 AM, Frank Rowand wrote:
> Hi Abhijeet,
>
> My qcom-apq8074-dragonboard panics on boot on v4.13-rc1.
>
> I bisected the problem to commit 7f1d4e58dabb, "spmi: pmic-arb:
> optimize table lookups".
there's a fix on its way upstream,
https://patchwork.kernel.org/patch/9810723/
On 07/18/2017 09:12 AM, Frank Rowand wrote:
> Hi Abhijeet,
>
> My qcom-apq8074-dragonboard panics on boot on v4.13-rc1.
>
> I bisected the problem to commit 7f1d4e58dabb, "spmi: pmic-arb:
> optimize table lookups".
there's a fix on its way upstream,
https://patchwork.kernel.org/patch/9810723/
On Mon, Jul 17, 2017 at 6:33 PM, Rafael J. Wysocki wrote:
> On Tue, Jul 18, 2017 at 2:30 AM, dbasehore . wrote:
>> On Sat, Jul 15, 2017 at 5:39 AM, Rafael J. Wysocki
>> wrote:
>>> On Thursday, July 13, 2017 03:58:53 PM dbasehore .
On Mon, Jul 17, 2017 at 6:33 PM, Rafael J. Wysocki wrote:
> On Tue, Jul 18, 2017 at 2:30 AM, dbasehore . wrote:
>> On Sat, Jul 15, 2017 at 5:39 AM, Rafael J. Wysocki
>> wrote:
>>> On Thursday, July 13, 2017 03:58:53 PM dbasehore . wrote:
On Thu, Jul 13, 2017 at 8:09 AM, Rafael J. Wysocki
Hi all,
Changes since 20170717:
The btrfs-kdave tree gained a conflict against Linus' tree.
The net-next tree gained a build failure so I used the version from
next-20170717.
The drm-misc tree gained a confict against the drm-misc-fixes tree and
a build failure for which I applied a merge fix
Hi all,
Changes since 20170717:
The btrfs-kdave tree gained a conflict against Linus' tree.
The net-next tree gained a build failure so I used the version from
next-20170717.
The drm-misc tree gained a confict against the drm-misc-fixes tree and
a build failure for which I applied a merge fix
Hi Abhijeet,
My qcom-apq8074-dragonboard panics on boot on v4.13-rc1.
I bisected the problem to commit 7f1d4e58dabb, "spmi: pmic-arb:
optimize table lookups".
The panic occurs at the top of pmic_arb_ppid_to_apid_v1(), due
to pa->ppid_to_apid being null.
A little more information that might
Hi Abhijeet,
My qcom-apq8074-dragonboard panics on boot on v4.13-rc1.
I bisected the problem to commit 7f1d4e58dabb, "spmi: pmic-arb:
optimize table lookups".
The panic occurs at the top of pmic_arb_ppid_to_apid_v1(), due
to pa->ppid_to_apid being null.
A little more information that might
From: Qiuyang Sun
This patch implements Direct Access (DAX) in F2FS, including:
- a mount option to choose whether to enable DAX or not
- read/write and mmap of regular files in the DAX way
- zero-out of unaligned partial blocks in the DAX way
- garbage collection of DAX
From: Qiuyang Sun
This patch implements Direct Access (DAX) in F2FS, including:
- a mount option to choose whether to enable DAX or not
- read/write and mmap of regular files in the DAX way
- zero-out of unaligned partial blocks in the DAX way
- garbage collection of DAX files, by mapping both
On Thu, Jul 13, 2017 at 10:13 PM, Maxime Ripard
wrote:
> Some channel0 setup has to be done, no matter what the output interface is
> (RGB, CPU, LVDS). Move that code into a common function in order to avoid
> duplication.
>
> Signed-off-by: Maxime Ripard
On Thu, Jul 13, 2017 at 10:13 PM, Maxime Ripard
wrote:
> Some channel0 setup has to be done, no matter what the output interface is
> (RGB, CPU, LVDS). Move that code into a common function in order to avoid
> duplication.
>
> Signed-off-by: Maxime Ripard
> ---
>
Expose fanX_target, pwmX and pwmX_enable hwmon sysfs attributes.
Fans in a PMBus device are driven by the configuration of two registers:
FAN_CONFIG_x_y and FAN_COMMAND_x: FAN_CONFIG_x_y dictates how the fan
and the tacho operate (if installed), while FAN_COMMAND_x sets the
desired fan rate. The
Expose fanX_target, pwmX and pwmX_enable hwmon sysfs attributes.
Fans in a PMBus device are driven by the configuration of two registers:
FAN_CONFIG_x_y and FAN_COMMAND_x: FAN_CONFIG_x_y dictates how the fan
and the tacho operate (if installed), while FAN_COMMAND_x sets the
desired fan rate. The
Hello,
This is a follow-up to the first RFC series[1] and includes some significant
reworks based on Guenter's feedback.
[1] https://lkml.org/lkml/2017/7/10/338
v2 retains the goal of exposing the fan[1-*]_target, pwm[1-*] and
pwm[1-*]_enable attributes, and implementing support for the
Hello,
This is a follow-up to the first RFC series[1] and includes some significant
reworks based on Guenter's feedback.
[1] https://lkml.org/lkml/2017/7/10/338
v2 retains the goal of exposing the fan[1-*]_target, pwm[1-*] and
pwm[1-*]_enable attributes, and implementing support for the
101 - 200 of 2272 matches
Mail list logo