From: Chen-Yu Tsai
The ARM CPU cores are fed by the CPU clock from the CCU. Add a
reference to the clock for each CPU core, along with the clock
transition latency.
Signed-off-by: Chen-Yu Tsai
---
arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi | 8
1 file changed, 8 insertions(+)
diff
From: Chen-Yu Tsai
This enables passive cooling by down-regulating CPU voltage and frequency.
The trip points were copied from the H3.
Signed-off-by: Chen-Yu Tsai
---
arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi | 30
1 file changed, 30 insertions(+)
diff --git
From: Chen-Yu Tsai
The Bananapi M2+ uses a GPIO line to change the effective resistance of
the CPU supply regulator's feedback resistor network. The voltages
described in the device tree were given directly by the vendor. This
turns out to be slightly off compared to the real values.
The
From: Chen-Yu Tsai
The Libre Computer ALL-H3-CC H5 variant can work with the standard H5
OPPs. Tie them in to enable CPU frequency scaling.
Signed-off-by: Chen-Yu Tsai
---
arch/arm64/boot/dts/allwinner/sun50i-h5-libretech-all-h3-cc.dts | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Chen-Yu Tsai
The Bananapi M2 Plus H5 v1.2 can work with the standard H5 OPPs.
Tie them in to enable CPU frequency scaling.
The original Bananapi M2 Plus H5 is left out for now, as adding
the fixed regulator along with the enable pin seemed to cause some
glitching in Linux.
Signed-off-by:
From: Chen-Yu Tsai
The device tree currently only assigns the a supply for the first CPU
core, when in reality the regulator supply is shared by all four cores.
This might cause an issue if the implementation does not realize the
sharing of the supply.
Assign the same regulator supply to the
From: Chen-Yu Tsai
Add an OPP (Operating Performance Points) table for the CPU cores for
boards to include to DVFS (Dynamic Voltage & Frequency Scaling) on the
H5. The table originates from Armbian, but the maximum voltage is raised
slightly to account for boards using slightly higher voltages.
From: Chen-Yu Tsai
Hi everyone,
This is v2 of my Allwinner H5 SoC cpufreq support series from way
back [1]. The series enables DVFS for the CPU cores (aka cpufreq)
on the Allwinner H5 SoC. The OPP table was taken from Armbian, with
minor tweaks to the maximum voltage to account for slightly
Hi Jingle,
On Fri, Jul 17, 2020 at 04:31:58PM +0800, jingle wrote:
> Hi Dmitry:
>
> 1.
>
> In this function elan_get_fwinfo().
>
> +static int elan_get_fwinfo(u16 ic_type, u8 iap_version, u8 pattern,
> +u16 *validpage_count, u32 *signature_address,
> +
Hi Jacob,
On 7/16/20 8:45 PM, Jacob Pan wrote:
> IOMMU generic layer already does sanity checks UAPI data for version
> match and argsz range under generic information.
> Remove the redundant version check from VT-d driver and check for vendor
> specific data size.
>
> Signed-off-by: Jacob Pan
I dare to repeat previous patch review aspects once more.
https://lore.kernel.org/cocci/a316f076-1686-25d8-18fe-1bbc0cf9a...@web.de/
…
> +virtual context
> +virtual patch
> +virtual org
> +virtual report
+virtual context, patch, org, report
Is such a SmPL code variant more succinct?
…
> +if
Hi!
On Wed, Jul 15, 2020 at 07:54:12PM +0800, Frank Lee wrote:
> From: Yangtao Li
>
> The sunxi gpio binding defines a few custom cells for its gpio specifier.
> Provide bank name for those.
>
> Signed-off-by: Yangtao Li
Thanks for working on this, I wanted to do it at some point but it kept
On Wed, Jul 15, 2020 at 07:55:07PM +0800, Frank Lee wrote:
> From: Yangtao Li
>
> Use names instead of numbers to describe GPIO. We clean arm64 first.
> Since H5 uses the DTS file in arm directory, we need to modify the
> header file in advance.
>
> Signed-off-by: Yangtao Li
>
> ---
>
On Thu, Jul 16, 2020 at 10:10 PM Alex Shi wrote:
>
>
> >> @@ -950,6 +951,21 @@ static bool too_many_isolated(pg_data_t *pgdat)
> >> if (!(cc->gfp_mask & __GFP_FS) && page_mapping(page))
> >> goto isolate_fail;
> >>
> >> + /*
> >> +
On Wed, Jul 15, 2020 at 07:55:29PM +0800, Frank Lee wrote:
> From: Yangtao Li
>
> Convert gpio.h to sunxi-gpio.h, and convert to use gpio bank name macro.
> This is done using the following command.
>
> sed -i 's/r_pio 0/r_pio PL/g' arch/arm64/boot/dts/allwinner/*
> sed -i 's/r_pio 1/r_pio
It will call devm_request_irq() after platform_get_irq() function
in many drivers, And sometimes, the error handling of these two functions
is incorrect in some drivers. So this function is provided to simplify
the driver.
the first patch will provide devm_platform_request_irq(), and the
second
It will call devm_request_irq() after platform_get_irq() function
in many drivers, And sometimes, the error handling of these two functions
is incorrect in some drivers. So this function is provided to simplify
the driver.
Cc: Michal Simek
Cc: Wolfram Sang
Signed-off-by: Dejin Zheng
---
v3 ->
> > I agree with Nick: A memory barrier is needed somewhere between the
> > assignment at 6 and the return to user mode at 8. Otherwise you end up
> > with the Store Buffer pattern having a memory barrier on only one side,
> > and it is well known that this arrangement does not guarantee any
> >
Use devm_platform_request_irq() to simplify code, and it contains
platform_get_irq() and devm_request_irq().
Cc: Michal Simek
Cc: Wolfram Sang
Signed-off-by: Dejin Zheng
Acked-by: Linus Walleij
Acked-by: Michal Simek
---
v3 -> v4:
- add Michal's Acked-by tag in the second patch. and
I'm happy to announce that after over a year, we finally are able to
release trace-cmd version 2.9!
Features and user visible updates since 2.8:
- git hash is now visible in trace-cmd --version output
- Build: python-dir can be specified on the command line for python
location.
- Build:
Hi Eugeniu
On 07/09/20 09:00, Eugeniu Rosca wrote:
> Hello everyone,
>
> Cc: linux-renesas-soc
> Cc: linux-pm
[...]
> After integrating v4.14.186 commit 5410d158ca2a50 ("usb/ehci-platform:
> Set PM runtime as active on resume") into downstream v4.14.x, we started
> to consistently experience
Em Fri, Jul 17, 2020 at 11:05:04AM -0400, Steven Rostedt escreveu:
> On Sat, 11 Jul 2020 20:40:20 +0800
> Changbin Du wrote:
>
> > This adds an option '-F/--funcs' to list all available functions to trace,
> > which is read from tracing file 'available_filter_functions'.
> >
> > $ sudo ./perf
- On Jul 17, 2020, at 12:11 PM, Alan Stern st...@rowland.harvard.edu wrote:
>> > I agree with Nick: A memory barrier is needed somewhere between the
>> > assignment at 6 and the return to user mode at 8. Otherwise you end up
>> > with the Store Buffer pattern having a memory barrier on only
Doug,
Doug Anderson writes:
> On Thu, Jul 9, 2020 at 3:51 AM Thomas Gleixner wrote:
>> TBH, I don't see why this is a good idea.
>>
>> 1) I'm not following your argumentation that the command line option is
>> a poor Kconfig replacement. The L1TF mode is a boot time (module
>> load
On Fri, 17 Jul 2020 08:17:09 -0700 Shakeel Butt wrote:
> On Thu, Jul 16, 2020 at 11:54 PM SeongJae Park wrote:
> >
> > On Thu, 16 Jul 2020 17:46:54 -0700 Shakeel Butt wrote:
> >
> > > On Mon, Jul 13, 2020 at 1:44 AM SeongJae Park wrote:
> > > >
> > > > From: SeongJae Park
> > > >
> > > >
On Fri, 17 Jul 2020 13:21:16 -0300
Arnaldo Carvalho de Melo wrote:
>
> > Would you like to start contributing to that, and when we get the
> > libtracefs.so packed in distributions, we can easily create the
> > perf ftrace without having to rewrite the wheel 10 times?
>
> Or we can use as
Hi Yi,
On 7/12/20 1:20 PM, Liu Yi L wrote:
> IOMMUs that support nesting translation needs report the capability info
s/needs/need to report
> to userspace, e.g. the format of first level/stage paging structures.
It gives information about requirements the userspace needs to implement
plus other
> On Jul 14, 2020, at 5:42 PM, Arvind Sankar wrote:
>
> On Wed, Jul 08, 2020 at 11:50:19AM -0700, Nick Terrell wrote:
>> From: Nick Terrell
>>
>> * Add unzstd() and the zstd decompress interface.
>> * Add zstd support to decompress_method().
>>
>> The decompress_method() and unzstd()
On Fri, Jul 17, 2020 at 09:30:07PM +0800, Dejin Zheng wrote:
> The kernel test robot reported a compile warning,
>
> drivers/pci/controller/dwc/pci-keystone.c:1236:18: warning: variable 'res'
> is uninitialized when used here [-Wuninitialized]
>
> The commit c59a7d771134b5 ("PCI: dwc: Convert to
On 7/17/20 3:54 AM, Hans Verkuil wrote:
Hi Sowjanya,
On 15/07/2020 06:20, Sowjanya Komatineni wrote:
This series adds support for video capture from external camera sensor to
Tegra video driver.
Jetson TX1 has camera expansion connector and supports custom camera module
designed as per TX1
On Fri, Jul 17, 2020 at 12:13:04AM +0200, Marek Szyprowski wrote:
> Hi Saravana,
>
> On 16.07.2020 23:45, Saravana Kannan wrote:
> > Marek and Guenter reported that commit 287905e68dd2 ("driver core:
> > Expose device link details in sysfs") caused sleeping/scheduling while
> > atomic warnings.
>
On 7/16/2020 4:38 PM, Doug Berger wrote:
> The Hardware Filter Block RAM may not be preserved when the GENET
> block is reset during a deep sleep, so it is not sufficient to
> only backup and restore the enables.
>
> This commit clears out the HFB block and reprograms the rxnfc
> rules when
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1].
[1]
https://www.kernel.org/doc/html/v5.7-rc7/process/deprecated.html?highlight=fallthrough#implicit-switch-case-fall-through
Signed-off-by: Gustavo A. R. Silva
---
Em Fri, Jul 17, 2020 at 12:27:40PM -0400, Steven Rostedt escreveu:
> On Fri, 17 Jul 2020 13:21:16 -0300 Arnaldo Carvalho de Melo
> wrote:
> > > Would you like to start contributing to that, and when we get the
> > > libtracefs.so packed in distributions, we can easily create the
> > > perf
The initcalls like to play joke. In our case, the thermal-netlink
initcall is called after the thermal-core initcall but this one sends
a notification before the former is initialzed. No issue was spotted,
but it could lead to a memory corruption, so instead of relying on the
core_initcall for the
The generic netlink is initialized at subsys_initcall, so far after
the thermal init routine and the thermal generic netlink family
initialization.
On ŝome platforms, that leads to a memory corruption.
The fix was sent to netdev@ to move the genetlink framework
initialization at core_initcall.
On Fri, Jul 17, 2020 at 05:31:11PM +0100, Lorenzo Pieralisi wrote:
> On Fri, Jul 17, 2020 at 09:30:07PM +0800, Dejin Zheng wrote:
> > The kernel test robot reported a compile warning,
> >
> > drivers/pci/controller/dwc/pci-keystone.c:1236:18: warning: variable 'res'
> > is uninitialized when used
Em Fri, Jul 17, 2020 at 09:26:50PM +0800, Changbin Du escreveu:
> On Thu, Jul 16, 2020 at 12:36:30PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Sat, Jul 11, 2020 at 08:40:21PM +0800, Changbin Du escreveu:
> > > +++ b/tools/perf/Documentation/perf-ftrace.txt
> > > @@ -38,6 +38,10 @@ OPTIONS
> >
On Mon, Jul 13, 2020 at 1:02 AM Takashi Iwai wrote:
>
> On Wed, 08 Jul 2020 20:14:27 +0200,
> Dan Williams wrote:
> >
> > +Recommended replacements for 'blacklist/whitelist' are:
> > +'denylist / allowlist'
> > +'blocklist / passlist'
>
> I started looking through the tree now and noticed
On 7/17/20 4:40 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200716:
>
> New tree: init
> Changed tree: dmi (from quilt to git)
>
> My fixes tree contains:
>
> dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
>
> I revreted 3 commits from the powerpc tree due to
On 2020-07-17 18:35:03, Konsta Karsisto wrote:
> Hi,
>
> Found one glitch with this change, see below:
>
> On Thu, Jul 9, 2020 at 9:22 AM Tyler Hicks
> wrote:
> >
> > The args_p member is a simple string that is allocated by
> > ima_rule_init(). Shallow copy it like other non-LSM references in
Mostly little stuff.
Consider refactoring create_feature_instance.
Tom
> diff --git a/drivers/fpga/dfl-pci.c b/drivers/fpga/dfl-pci.c
> index e220bec..22dc025 100644
> --- a/drivers/fpga/dfl-pci.c
> +++ b/drivers/fpga/dfl-pci.c
> @@ -39,6 +39,11 @@ static void __iomem
On Thu, Jul 16, 2020 at 7:51 AM Nicolas Saenz Julienne
wrote:
>
> Aside from being more correct, the non optional version of the function
> prints an error when failing to find the IRQ.
>
> Fixes: eea9b97b4504 ("drm/v3d: Add support for V3D v4.2")
> Signed-off-by: Nicolas Saenz Julienne
> ---
>
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
Only a couple left after this. I'll sort those next week.
Lee Jones (30):
iio: adc: ti_am335x_adc: Remove a couple of unused 'read' variables
On 09/07/2020 18:20, Dmitry Osipenko wrote:
> Power Management Controller (PMC) can override the PLLM clock settings,
> including the enable-state. Although PMC could only act as a second level
> gate, meaning that PLLM needs to be enabled by the Clock and Reset
> Controller (CaR) anyways if we
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/twl4030-madc.c:170: warning: Function parameter or member
'usb3v1' not described in 'twl4030_madc_data'
Cc: J Keerthy
Cc: Mikko Ylinen
Cc: Amit Kucheria
Signed-off-by: Lee Jones
---
drivers/iio/adc/twl4030-madc.c | 4 ++--
1
On 7/17/2020 8:23 AM, Al Cooper wrote:
> Add compatible string for some newer boards that only have this
> as there match sting.
>
> Signed-off-by: Al Cooper
This looks good to me, however you should also include it in the binding
document.
--
Florian
All lines should start with ' *'.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/at91_adc.c:160: warning: bad line:
(Interruptions registers mostly)
Cc: Nicolas Ferre
Cc: Alexandre Belloni
Cc: Ludovic Desroches
Cc: Maxime Ripard
Signed-off-by: Lee
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/ti_am335x_adc.c: In function ‘tiadc_buffer_preenable’:
drivers/iio/adc/ti_am335x_adc.c:297:21: warning: variable ‘read’ set but not
used [-Wunused-but-set-variable]
297 | int i, fifo1count, read;
| ^~~~
Kerneldoc is only suitable for documenting functions and struct/enums.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/qcom-pm8xxx-xoadc.c:133: warning: Excess function parameter
'PM8XXX_CHANNEL_INTERNAL' description in 'PM8XXX_CHANNEL_INTERNAL'
This is the only use of kerneldoc in the source file and no
descriptions are provided.
Fixes the following W=1 kernel build warning(s):
drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c:118: warning: Function parameter or
member 'irq' not described in 'inv_mpu6050_read_fifo'
Kerneldoc gets confused if the variable does not follow the
type/attribute definitions.
Fixes the following W=1 kernel build warning(s):
drivers/iio/gyro/adxrs450.c:79: warning: Function parameter or member
'cacheline_aligned' not described in 'adxrs450_state'
Cc: Michael Hennerich
Fixes the following W=1 kernel build warning(s):
drivers/iio/magnetometer/ak8974.c:200: warning: Function parameter or member
'scan' not described in 'ak8974'
Cc: Linus Walleij
Cc: Samu Onkalo
Signed-off-by: Lee Jones
---
drivers/iio/magnetometer/ak8974.c | 1 +
1 file changed, 1
Kerneldoc expects attributes/parameters to be in '@*.: ' format.
Fixes the following W=1 kernel build warning(s):
drivers/iio/dac/ad5504.c:58: warning: Function parameter or member
'pwr_down_mask' not described in 'ad5504_state'
drivers/iio/dac/ad5504.c:58: warning: Function parameter or
No attempt has been made to document any of the demoted structs here.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/max9611.c:117: warning: cannot understand function prototype:
'const unsigned int max9611_mux_conf[][2] = '
drivers/iio/adc/max9611.c:145: warning: cannot
Very few of the struct attributes have been documented here.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/palmas_gpadc.c:114: warning: Function parameter or member
'dev' not described in 'palmas_gpadc'
drivers/iio/adc/palmas_gpadc.c:114: warning: Function parameter or
Fixes the following W=1 kernel build warning(s):
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h:487:1: warning: ‘inline’ is not at
beginning of declaration [-Wold-style-declaration]
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h:497:44: warning:
‘st_lsm6dsx_accel_ext_info’ defined but not used
No attempt has been made to document any of the demoted functions here.
Fixes the following W=1 kernel build warning(s):
drivers/iio/imu/inv_mpu6050/inv_mpu_core.c:444: warning: Function parameter or
member 'st' not described in 'inv_mpu6050_set_lpf_regs'
On 7/17/2020 8:23 AM, Al Cooper wrote:
> From: Sasi Kumar
>
> Multiple connects/disconnects can cause a crash on the second
> disconnect. The driver had a problem where it would try to send
> endpoint commands after it was disconnected which is not allowed
> by the hardware. The fix is to
On 7/17/20 6:20 AM, Grygorii Strashko wrote:
Hi Santosh,
This series is a set of non critical updates for The TI K3 AM654x/J721E
Ring Accelerator driver.
Thanks. Will have a look and if all looks good, add it to next.
Patch 1 - convert bindings to json-schema
Patches 2,3,5 - code reworking
No attempt has been made to document any of the demoted functions here.
Fixes the following W=1 kernel build warning(s):
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_shub.c:174: warning: Function parameter
or member 'hw' not described in 'st_lsm6dsx_shub_read_output'
This is the only use of kerneldoc in the source file and no
descriptions are provided.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/rockchip_saradc.c:190: warning: Function parameter or member
'reset' not described in 'rockchip_saradc_reset_controller'
Cc: Heiko Stuebner
It doesn't make sense to move it into '*core*' as it's co-located with
other, similar definitions which are used in multiple locations.
Fixes the following W=1 kernel build warning(s):
In file included from drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_i2c.c:17:
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/at91-sama5d2_adc.c:360: warning: cannot understand function
prototype: 'struct at91_adc_dma '
drivers/iio/adc/at91-sama5d2_adc.c:379: warning: cannot understand function
prototype: 'struct at91_adc_touch '
Cc: Ludovic Desroches
Kerneldoc gets confused if the variable does not follow th
type/attribute definitions.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/mcp320x.c:96: warning: Function parameter or member
'cacheline_aligned' not described in 'mcp320x'
Cc: Oskar Andero
Cc: Bendorff Jensen
Kerneldoc expects attributes/parameters to be in '@*.: ' format.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/max1363.c:190: warning: Function parameter or member 'lock'
not described in 'max1363_state'
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Rohit Sarkar
Signed-off-by:
'fxas21002c_reg_fields' is only used in '*core*', meaning that '*i2c*'
and '*spi*' complain of a defined but not used const variable. Let's
move it into the source file.
Fixes the following W=1 kernel build warning(s):
In file included from drivers/iio/gyro/fxas21002c_i2c.c:14:
Fixes the following W=1 kernel build warning(s):
drivers/iio/accel/sca3000.c:210: warning: Function parameter or member
'mot_det_mult_xz' not described in 'sca3000_chip_info'
drivers/iio/accel/sca3000.c:210: warning: Function parameter or member
'mot_det_mult_y' not described in
'*'s are not welcome in kerneldoc parameter names.
Fixes the following W=1 kernel build warning(s):
drivers/iio/temperature/mlx90632.c:175: warning: Function parameter or member
'data' not described in 'mlx90632_perform_measurement'
Cc: Crt Mori
Signed-off-by: Lee Jones
---
Kerneldoc expects attributes/parameters to be in '@*.: ' format.
Fixes the following W=1 kernel build warning(s):
drivers/iio/light/us5182d.c:457: warning: Function parameter or member 'data'
not described in 'us5182d_update_dark_th'
drivers/iio/light/us5182d.c:457: warning: Function
On 7/17/2020 8:23 AM, Al Cooper wrote:
> From: Florian Fainelli
>
> The BDC clock is optional and we may get an -EPROBE_DEFER error code
> which would not be propagated correctly, fix this by using
> devm_clk_get_optional().
>
> Signed-off-by: Florian Fainelli
Since you are carrying this
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/twl4030-madc.c: In function
‘twl4030_madc_threaded_irq_handler’:
drivers/iio/adc/twl4030-madc.c:475:9: warning: variable ‘len’ set but not used
[-Wunused-but-set-variable]
475 | int i, len, ret;
| ^~~
Cc: Sebastian Reichel
We know that it's okay for 'hmc5843_pm_ops' to be unused here.
Fixes the following W=1 kernel build warning(s):
In file included from include/linux/device.h:25,
from include/linux/iio/iio.h:10,
from drivers/iio/magnetometer/hmc5843_core.c:16:
drivers/iio/magnetometer/hmc5843.h:55:26:
Kerneldoc expects attributes/parameters to be in '@*.: ' format.
Fixes the following W=1 kernel build warning(s):
drivers/iio/dac/ltc2632.c:50: warning: Function parameter or member
'powerdown_cache_mask' not described in 'ltc2632_state'
drivers/iio/dac/ltc2632.c:50: warning: Function
Kerneldoc gets confused if the variable does not follow the
type/attribute definitions.
Fixes the following W=1 kernel build warning(s):
drivers/iio/resolver/ad2s1200.c:44: warning: Function parameter or member
'cacheline_aligned' not described in 'ad2s1200_state'
Cc: Michael Hennerich
This is the only use of function related kerneldoc in the sourcefile
and no descriptions are provided.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/ad799x.c:192: warning: Function parameter or member 'irq' not
described in 'ad799x_trigger_handler'
None of the headers demoted here provide any descriptions.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/cpcap-adc.c:100: warning: Function parameter or member
'ato_in' not described in 'cpcap_adc_ato'
drivers/iio/adc/cpcap-adc.c:100: warning: Function parameter or member
No attempt has been made to document any of the demoted functions here
Fixes the following W=1 kernel build warning(s):
drivers/iio/light/si1145.c:192: warning: Function parameter or member 'data'
not described in '__si1145_command_reset'
drivers/iio/light/si1145.c:228: warning: Function
Kerneldoc expects attributes/parameters to be in '@*.: ' format.
Fixes the following W=1 kernel build warning(s):
drivers/iio/adc/twl6030-gpadc.c:110: warning: Function parameter or member
'ideal' not described in 'twl6030_gpadc_platform_data'
drivers/iio/adc/twl6030-gpadc.c:110: warning:
On 7/17/2020 8:23 AM, Al Cooper wrote:
> Version v1.0.40 of the Android host ADB software increased maximum
> transfer sizes from 256K to 1M. Since the STB ADB gadget driver
> requests only 16K at a time, the BDC driver ran out of buffer
> descriptors (BDs) if the queuing happens faster than
v6->v7:
1.Remove "default MACH_INGENIC" and make option silent.
2.Enable the corresponding driver in the platform's Kconfig.
3.Update DT of X1000 and X1830, use SYSOST instead of TCU
to provide clocksource and clockevent.
周琰杰 (Zhou Yanjie) (5):
dt-bindings: timer: Add Ingenic X1000 OST
The previous clocksource patch in this series ([2/3]) has remove
"default MACH_INGENIC" and make option silent, so we need to
enable the corresponding driver in the platform's Kconfig.
Suggested-by: Daniel Lezcano
Tested-by: 周正 (Zhou Zheng)
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v7:
Enable support for HSUSB, USB2.0 and xHCI on iWave RZ/G1H carrier board.
Signed-off-by: Lad Prabhakar
Reviewed-by: Marian-Cristian Rotariu
Reviewed-by: Biju Das
---
arch/arm/boot/dts/r8a7742-iwg21d-q7.dts | 42 +
1 file changed, 42 insertions(+)
diff --git
Add USB1 PWEN pin and group for USB1 interface.
Signed-off-by: Lad Prabhakar
Reviewed-by: Biju Das
---
drivers/pinctrl/sh-pfc/pfc-r8a7790.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a7790.c
Hi All,
This series enables support for following peripherals in iW-RainboW-G21D-Q7
development platform:
* HSUSB
* USB2.0
* xHCI
Changes for v2:
* Added USB1 pwen pin and group
* Fixed pinmux pins for usb1
[v1] https://lkml.org/lkml/2020/5/27/1478
* Rest of the patches from v1 have been
Before this series of patches, X1830 used TCU to provide
clocksource and clockevent, but because the timer of TCU
is only 16 bits, so the timing length is only 16 bits. In
actual use, it is easy to cause some problems such as data
loss during data transmission. The SYSOST driver is provided
in
Function Granular Kernel Address Space Layout Randomization (fgkaslr)
-
This patch set is an implementation of finer grained kernel address space
randomization. It rearranges your kernel code at load time
on a per-function level
On Fri, 17 Jul 2020 21:26:50 +0800
Changbin Du wrote:
> On Thu, Jul 16, 2020 at 12:36:30PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Sat, Jul 11, 2020 at 08:40:21PM +0800, Changbin Du escreveu:
> > > This allows us to trace single thread instead of the whole process.
> > >
> > >
X1000 and SoCs after X1000 (such as X1500 and X1830) had a separate
OST, it no longer belongs to TCU. This driver will register both a
clocksource and a sched_clock to the system.
Tested-by: 周正 (Zhou Zheng)
Co-developed-by: 漆鹏振 (Qi Pengzhen)
Signed-off-by: 漆鹏振 (Qi Pengzhen)
Signed-off-by: 周琰杰
If a .cold function is examined prior to it's parent, the link
to the parent/child function can be overwritten when the parent
is examined. Only update pfunc and cfunc if they were previously
nil to prevent this from happening.
Signed-off-by: Kristen Carlson Accardi
Acked-by: Josh Poimboeuf
---
Introduce a new config option to allow modules to be re-ordered
by function. This option can be enabled independently of the
kernel text KASLR or FG_KASLR settings so that it can be used
by architectures that do not support either of these features.
This option will be selected by default if
This patch makes /proc/kallsyms display in a random order, rather
than sorted by address in order to hide the newly randomized address
layout.
Signed-off-by: Kristen Carlson Accardi
Reviewed-by: Tony Luck
Tested-by: Tony Luck
---
kernel/kallsyms.c | 163
This commit contains the changes required to re-layout the kernel text
sections generated by -ffunction-sections shortly after decompression.
Documentation of the feature is also added.
After decompression, the decompressed image's elf headers are parsed.
In order to manually update certain data
While the relocs tool already supports finding the total number
of section headers if vmlinux exceeds 64K sections, it fails to
read the extended symbol table to get section header indexes for symbols,
causing incorrect symbol table indexes to be used when there are > 64K
symbols.
Parse the elf
When reordering functions, the relative offsets for relocs that
are either in the randomized sections, or refer to the randomized
sections will need to be adjusted. Add code to detect whether a
reloc satisfies these cases, and if so, add them to the appropriate
reloc list.
Signed-off-by: Kristen
From: Kees Cook
Under earlyprintk, each RNG call produces a debug report line. When
shuffling hundreds of functions, this is not useful information (each
line is identical and tells us nothing new). Instead, allow for a NULL
"purpose" to suppress the debug reporting.
Signed-off-by: Kees Cook
Add the OST bindings for the X1 SoC from Ingenic.
Tested-by: 周正 (Zhou Zheng)
Signed-off-by: 周琰杰 (Zhou Yanjie)
Reviewed-by: Paul Cercueil
Reviewed-by: Rob Herring
---
Notes:
No change.
v2->v3:
Fix wrong parameters in "clocks".
v3->v4:
1.Rename
Before this series of patches, X1000 used TCU to provide
clocksource and clockevent, but because the timer of TCU
is only 16 bits, so the timing length is only 16 bits. In
actual use, it is easy to cause some problems such as data
loss during data transmission. The SYSOST driver is provided
in
From: Kees Cook
The preboot malloc() (and free()) implementation in
include/linux/decompress/mm.h (which is also included by the
static decompressors) is static. This is fine when the only thing
interested in using malloc() is the decompression code, but the
x86 preboot environment uses malloc()
When using -ffunction-sections to place each function in
it's own text section so it can be randomized at load time, the
linker considers these .text.* sections "orphaned sections", and
will place them after the first similar section (.text). In order
to accurately represent the end of the text
1 - 100 of 1397 matches
Mail list logo
