On 10/1/19 9:29 PM, Krzysztof Kozlowski wrote:
> On Wed, Aug 21, 2019 at 12:42:55PM +0200, Lukasz Luba wrote:
>> Hi all,
>>
>> This is v13 which makes cosmetic changes. It is based on current mainline
>> (v5.3-rc5) with with devfreq/for-next where there is a PPMU patch [1].
>>
>> The patch set
Hi all,
This is a v3 patch set for the Exynos5 Dynamic Memory Controller
driver which could be found in Krzysztof's for-next branch [1].
It adds interrupt mode which does not relay on devfreq polling.
Instead of checking the device state by the framework, driver uses local
performance event
There is a need to access registers at address offset near 0x1.
These registers are private DMC performance counters, which might be used
as interrupt trigger when overflow. Potential usage is to skip polling
in devfreq framework and switch to interrupt managed bandwidth control.
Introduce a new interrupt driven mechanism for managing speed of the
memory controller. The interrupts are generated due to performance
counters overflow. The performance counters might track memory reads,
writes, transfers, page misses, etc. In the basic algorithm tracking
read transfers and
Add interrupt to Dynamic Memory Controller in Exynos5422 and Odroid
XU3-family boards. It will be used instead of devfreq polling mode
governor. The interrupt is connected to performance counters private
for DMC, which might track utilisation of the memory channels.
Signed-off-by: Lukasz Luba
Add description for optional interrupt lines. It provides a new operation
mode, which uses internal performance counters interrupt when overflow.
This is more reliable than using default polling mode implemented in
devfreq.
Signed-off-by: Lukasz Luba
---
Hi,
On Tue, Oct 01, 2019 at 10:06:56PM +0200, Jernej Skrabec wrote:
> GPU PLL was designed with dynamic frequency switching in mind so driver
> can adjust rate based on the GPU load.
>
> Allow GPU clock to change parent rate (GPU PLL is the only possible
> parent of GPU clock).
>
> Signed-off-by:
Skip the memmove checking for those archs who don't support it.
Signed-off-by: Nick Hu
---
mm/kasan/common.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/kasan/common.c b/mm/kasan/common.c
index 6814d6d6a023..897f9520bab3 100644
--- a/mm/kasan/common.c
+++ b/mm/kasan/common.c
@@
This patch ports the feature Kernel Address SANitizer (KASAN).
Note: The start address of shadow memory is at the beginning of kernel
space, which is 2^64 - (2^39 / 2) in SV39. The size of the kernel space is
2^38 bytes so the size of shadow memory should be 2^38 / 8. Thus, the
shadow memory
KASAN is an important runtime memory debugging feature in linux kernel
which can detect use-after-free and out-of- bounds problems.
Changes in v2:
- Remove the porting of memmove and exclude the check instead.
- Fix some code noted by Christoph Hellwig
Nick Hu (2):
kasan: Archs don't check
On 9/20/19 4:44 AM, Navid Emamdoost wrote:
> In gs_can_open if usb_submit_urb fails the allocated urb should be
> released.
>
> Signed-off-by: Navid Emamdoost
> ---
> drivers/net/can/usb/gs_usb.c | 1 +
> 1 file changed, 1 insertion(+)
Added Fixes line and added stable@v.k.o on Cc.
Marc
--
On 9/18/19 12:11 PM, Colin King wrote:
> From: Colin Ian King
>
> Currently the error return paths do not free skb and this results
> in a memory leak. Fix this by freeing them before the return.
>
> Addresses-Coverity: ("Resource leak")
> Fixes: 9d71dd0c7009 ("can: add support of SAE J1939
Update the Aspeed PECI driver with the AST2600 compatible string.
A new comptabile string is needed for the extended HW feature of
AST2600.
Chia-Wei, Wang (2):
peci: aspeed: Add AST2600 compatible string
dt-bindings: peci: aspeed: Add AST2600 compatible
The AST2600 SoC contains the same register set as AST25xx.
Signed-off-by: Chia-Wei, Wang
---
drivers/peci/peci-aspeed.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/peci/peci-aspeed.c b/drivers/peci/peci-aspeed.c
index 51cb2563ceb6..4eed119dc83b 100644
---
Document the AST2600 PECI controller compatible string.
Signed-off-by: Chia-Wei, Wang
---
Documentation/devicetree/bindings/peci/peci-aspeed.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/peci/peci-aspeed.txt
Hi,
I sent in another patch earlier that added support for specifying a file
in devicetree to initilize the eeprom from, corresponding to the case of
pre-flashed eeprom. Maybe these two patches should be merged so this
initialization is only done if no file is specified?
/BA
On 10/1/19
On Tue, 1 Oct 2019 at 19:12, Valentin Schneider
wrote:
>
> On 19/09/2019 08:33, Vincent Guittot wrote:
> > clean up load_balance and remove meaningless calculation and fields before
> > adding new algorithm.
> >
> > Signed-off-by: Vincent Guittot
>
> We'll probably want to squash the removal of
Hi Tejun,
Sorry for the late reply.
On Sat, Sep 21, 2019 at 6:04 AM Tejun Heo wrote:
>
> On Fri, Sep 20, 2019 at 05:47:45PM +0900, Namhyung Kim wrote:
> > Thanks for the sharing information! For 32-bit, while the ino itself is not
> > monotonic, gen << 32 + ino is monotonic right? I think we
On Wed, 2019-10-02 at 09:53 +0800, Alan Kao wrote:
> On Tue, Oct 01, 2019 at 03:10:16AM -0700, h...@infradead.org wrote:
> > On Tue, Oct 01, 2019 at 08:22:37AM +, Atish Patra wrote:
> > > riscv_of_processor_hartid() or seems to be a better candidate. We
> > > already check if "rv" is present
On 01.10.19 22:08, Jiri Kosina wrote:
> arch/s390/kvm/kvm-s390.c calls on several places __cpacf_query() directly,
> which makes it impossible to meet the "i" constraint for the asm operands
> (opcode in this case).
>
> As we are now force-enabling CONFIG_OPTIMIZE_INLINING on all
>
On Tue, 1 Oct 2019 at 18:53, Dietmar Eggemann wrote:
>
> On 01/10/2019 10:14, Vincent Guittot wrote:
> > On Mon, 30 Sep 2019 at 18:24, Dietmar Eggemann
> > wrote:
> >>
> >> Hi Vincent,
> >>
> >> On 19/09/2019 09:33, Vincent Guittot wrote:
>
> [...]
>
> >>> @@ -7347,7 +7362,7 @@ static int
On Tue, Oct 01, 2019 at 10:08:01PM +0200, Jiri Kosina wrote:
> arch/s390/kvm/kvm-s390.c calls on several places __cpacf_query() directly,
> which makes it impossible to meet the "i" constraint for the asm operands
> (opcode in this case).
>
> As we are now force-enabling
On Wed, Oct 02, 2019 at 08:46:05AM +0200, Heiko Carstens wrote:
> On Tue, Oct 01, 2019 at 10:08:01PM +0200, Jiri Kosina wrote:
> > I am wondering how is it possible that none of the build-testing
> > infrastructure we have running against linux-next caught this? Not enough
> > non-x86 coverage?
Hi Laurent,
On Tue, 1 Oct 2019 15:29:28 +0200 Laurent Dufour wrote:
>
> Fixes: 1211ee61b4a8 ("powerpc/pseries: Read TLB Block Invalidate
> Characteristics")
> Reported-by: Stephen Rothwell
Please use my external email address , thanks.
--
Cheers,
Stephen Rothwell
pgpu_iF55Ewhm.pgp
Hi,
Any updates on this?
On Mon, Sep 16, 2019 at 02:13:10PM +0300, Mike Rapoport wrote:
> From: Mike Rapoport
>
> The memory initialization of SGI-IP27 is already half-way to support
> SPARSEMEM. It only had free_bootmem_with_active_regions() left-overs
> interfering with
On Wed, Oct 02, 2019 at 08:46:05AM +0200, Heiko Carstens wrote:
> On Tue, Oct 01, 2019 at 10:08:01PM +0200, Jiri Kosina wrote:
> >
> >In file included from arch/s390/kvm/kvm-s390.c:44:
> >./arch/s390/include/asm/cpacf.h: In function '__cpacf_query':
> >
On 02.10.19 02:06, kbuild test robot wrote:
> Hi David,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on mmotm/master]
>
> url:
> https://github.com/0day-ci/linux/commits/David-Hildenbrand/mm-memory_hotplug-Shrink-zones-before-
From: Hans Andersson
When we read user ID / Synopsys ID we might still be in reset,
so read muliple times if needed.
Signed-off-by: Hans Andersson
---
drivers/net/ethernet/stmicro/stmmac/hwif.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
On Wed, Oct 2, 2019 at 1:39 AM Kees Cook wrote:
> > diff --git a/arch/x86/math-emu/reg_ld_str.c b/arch/x86/math-emu/reg_ld_str.c
> > index f3779743d15e..fe6246ff9887 100644
> > --- a/arch/x86/math-emu/reg_ld_str.c
> > +++ b/arch/x86/math-emu/reg_ld_str.c
> > @@ -85,7 +85,7 @@ int
Daniel Axtens a écrit :
Hi,
/*
* Find a place in the tree where VA potentially will be
* inserted, unless it is merged with its sibling/siblings.
@@ -741,6 +752,10 @@ merge_or_add_vmap_area(struct vmap_area *va,
if (sibling->va_end == va->va_start) {
On 02.10.19 02:55, Alexander Duyck wrote:
> On Tue, Oct 1, 2019 at 12:16 PM Nitesh Narayan Lal wrote:
>>
>>
>> On 10/1/19 12:21 PM, Alexander Duyck wrote:
>>> On Tue, 2019-10-01 at 17:35 +0200, David Hildenbrand wrote:
On 01.10.19 17:29, Alexander Duyck wrote:
> This series provides an
From: Bartosz Golaszewski
The first patch converts the at24 DT binding to yaml. The second adds a new
compatible special case that's being used undocumented currently.
v1 -> v2:
- modified the compatible property: we now list all possible combinations and
non-standard types with appropriate
From: Bartosz Golaszewski
Convert the binding document for at24 EEPROMs from txt to yaml. The
compatible property uses a regex pattern to address all the possible
combinations of "vendor,model" strings.
Signed-off-by: Bartosz Golaszewski
[robh: rework compatible schema, fix missing allOf for
From: Bartosz Golaszewski
arch/arm/boot/dts/at91-dvk_som60.dt.yaml uses the compatible string
'giantec,gt24c32a' for an at24 EEPROM with a fallback to 'atmel,24c32'.
Add this model as a special case to the binding document.
Reported-by: Rob Herring
Signed-off-by: Bartosz Golaszewski
---
Hi Vishal,
On Tue, Jun 04, 2019 at 07:25:55PM +0530, Vishal Sagar wrote:
> Add bindings documentation for Xilinx UHD-SDI Receiver Subsystem.
>
> The Xilinx UHD-SDI Receiver Subsystem consists of SMPTE UHD-SDI (RX) IP
> core, an SDI RX to Video Bridge IP core to convert SDI video to native
>
On Wed, Oct 02, 2019 at 11:27:26AM +1000, Duncan Roe wrote:
> On Tue, Oct 01, 2019 at 09:34:13PM +0300, Julian Anastasov wrote:
> >
> > Hello,
> >
> > On Tue, 1 Oct 2019, Haishuang Yan wrote:
> >
> > > This series patch include test cases for ipvs.
> > >
> > > The test topology is who as
On Wed, Oct 2, 2019 at 12:54 AM Eric W. Biederman wrote:
> Kees Cook writes:
> > On Tue, Oct 01, 2019 at 01:36:32PM -0500, Eric W. Biederman wrote:
> >
> > I think you can actually take this further and remove (or at least
> > empty) the uapi/linux/sysctl.h file too.
>
> I copied everyone who
On Tue, Sep 24, 2019 at 09:46:20AM +, David Laight wrote:
> From: Anson Huang
> > Sent: 24 September 2019 10:00
> > Add helper variable dev = >dev to simply the code.
> >
> > Signed-off-by: Anson Huang
> > ---
> > drivers/pwm/pwm-imx27.c | 13 +++--
> > 1 file changed, 7
From: Eugen Hristev
Add bindings for Microchip SAM9X60 Watchdog Timer
It has the same bindings as
Documentation/devicetree/bindings/watchdog/atmel-sama5d4-wdt.txt
except the compatible.
Signed-off-by: Eugen Hristev
---
.../devicetree/bindings/watchdog/sam9x60-wdt.txt | 34
From: Eugen Hristev
This is the driver for SAM9X60 watchdog timer.
The offered functionality is the same as sama5d4_wdt.
The difference comes in register map, way to configure the timeout and
interrupts.
Developed starting from sama5d4_wdt.c
Signed-off-by: Eugen Hristev
---
From: Eugen Hristev
Add sam9x60_wdt watchdog driver to at91 soc support.
Signed-off-by: Eugen Hristev
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 296de2b..109b030 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1972,6 +1972,7 @@ F:
On 01.10.2019 17:16, Boris Ostrovsky wrote:
> Currently execution of panic() continues until Xen's panic notifier
> (xen_panic_event()) is called at which point we make a hypercall that
> never returns.
>
> This means that any notifier that is supposed to be called later as
> well as significant
On 01.10.19 19:45, Boris Ostrovsky wrote:
> On 10/1/19 5:01 AM, David Hildenbrand wrote:
>> Let's simply use balloon_append() directly.
>>
>> Cc: Boris Ostrovsky
>> Cc: Juergen Gross
>> Cc: Stefano Stabellini
>> Signed-off-by: David Hildenbrand
>
> For the series (and your earlier patch)
>
>
On Tue, Oct 01, 2019 at 05:21:09PM -0500, Rob Herring wrote:
> On Fri, Sep 20, 2019 at 06:21:22PM +0200, Krzysztof Kozlowski wrote:
> > Convert Samsung S3C/S5P/Exynos watchdog bindings to DT schema format
> > using json-schema.
> >
> > Signed-off-by: Krzysztof Kozlowski
> >
> > ---
> >
> >
Hello Manivannan,
On Tue, Oct 01, 2019 at 08:25:03PM +0530, Manivannan Sadhasivam wrote:
> The caller of v4l2_fwnode_endpoint_alloc_parse() is expected to pass a
> valid bus_type parameter for proper working of this API. Hence, pass
> V4L2_MBUS_CSI2_DPHY as the bus_type parameter as this driver
On Tue 01-10-19 10:40:05, Qian Cai wrote:
> On Tue, 2019-10-01 at 16:22 +0200, Arnd Bergmann wrote:
> > Removing the mem_cgroup_id_get() stub function introduced a new warning
> > of the same kind when CONFIG_MMU is disabled:
>
> Shouldn't CONFIG_MEMCG depends on CONFIG_MMU instead?
I wanted to
On Tue 01-10-19 09:36:24, Nick Desaulniers wrote:
> On Tue, Oct 1, 2019 at 7:22 AM Arnd Bergmann wrote:
> >
> > Removing the mem_cgroup_id_get() stub function introduced a new warning
> > of the same kind when CONFIG_MMU is disabled:
> >
> > mm/memcontrol.c:4929:13: error: unused function
Hi,
On Wed, 2 Oct 2019, Stephen Rothwell wrote:
> In commit
>
> e66e52c5b742 ("ASoC: SOF: pcm: fix resource leak in hw_free")
>
> Fixes tag
>
> Fixes: c29d96c3b9b4 ("ASoC: SOF: reset DMA state in prepare")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Did you mean
>
On Tue, Oct 1, 2019 at 9:37 PM Matthias Kaehlcke wrote:
>
> On Tue, Oct 01, 2019 at 02:08:46PM -0400, Steven Rostedt wrote:
> > On Tue, 1 Oct 2019 10:42:35 -0700
> > Matthias Kaehlcke wrote:
> >
> > > On Tue, Oct 01, 2019 at 01:03:43PM -0400, Steven Rostedt wrote:
> > > > On Tue, 1 Oct 2019
On 02.10.19 09:47, David Hildenbrand wrote:
On 01.10.19 19:45, Boris Ostrovsky wrote:
On 10/1/19 5:01 AM, David Hildenbrand wrote:
Let's simply use balloon_append() directly.
Cc: Boris Ostrovsky
Cc: Juergen Gross
Cc: Stefano Stabellini
Signed-off-by: David Hildenbrand
For the series
On 10/1/19 10:43 AM, Jonathan Cameron wrote:
> On Mon, 30 Sep 2019 13:44:49 -0700
> Yizhuo wrote:
>
>> Several functions in this file are trying to use regmap_read() to
>> initialize the specific variable, however, if regmap_read() fails,
>> the variable could be uninitialized but used directly,
Hi Benoit,
+Hugues
If you're considering an helper, this thread might be useful to you:
https://patchwork.kernel.org/patch/11019673/
Thanks
j
On Tue, Oct 01, 2019 at 11:23:41AM -0500, Benoit Parrot wrote:
> Hi Sakari,
>
> Thanks for the review.
>
> Sakari Ailus wrote on Tue [2019-Oct-01
This commit adds Tegra194 XUSB host mode controller support. This is
very similar to the existing Tegra124/Tegra210/Tegra186 XHCI, except
1. the number of ports and PHYs differs
2. the IPFS wrapper being removed
3. mailbox registers address changes
Signed-off-by: JC Kuo
---
Extend the bindings to cover the set of features found in Tegra194.
Note that, technically, there are four more supplies connected to the
XUSB pad controller (DVDD_PEX, DVDD_PEX_PLL, HVDD_PEX and HVDD_PEX_PLL)
, but the power sequencing requirements of Tegra194 require these to be
under the
Adds the XUSB pad and XUSB controllers on Tegra194.
Signed-off-by: JC Kuo
---
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 130 +++
1 file changed, 130 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra194.dtsi
b/arch/arm64/boot/dts/nvidia/tegra194.dtsi
index
Add support for the XUSB pad controller found on Tegra194 SoCs. It is
mostly similar to the same IP found on Tegra186, but the number of
pads exposed differs, as do the programming sequences. Because most of
the Tegra194 XUSB PADCTL registers definition and programming sequence
are the same as
Tegra194 XUSB host controller has rearranged mailbox registers. This
commit makes mailbox registers address a part of "soc" data so that
xhci-tegra driver can be used for Tegra194.
Signed-off-by: JC Kuo
---
drivers/usb/host/xhci-tegra.c | 58 +--
1 file changed,
This commit enables XUSB host and pad controller in Tegra194
P2972- board.
Signed-off-by: JC Kuo
---
.../arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 31 +-
.../boot/dts/nvidia/tegra194-p2972-.dts | 59 +++
2 files changed, 89 insertions(+), 1 deletion(-)
diff
We assert / de-assert the reset line, but the CPU is too fast and the IP is
still
in reset when we later try to read user ID / Synopsys ID. Another option would
be to add a delay after we reset.
-Original Message-
From: Jose Abreu
Sent: den 2 oktober 2019 09:52
To: Hans Andersson ;
Hi,
This series introduces support for Tegra194 XUSB host and pad
controller. Tegra194 XUSB host and pad controller are highly
similar to the controllers found on Tegra186. Therefore, we
decided to resue xhci-tegra.c and xusb-tegra186.c for Tegra194.
JC Kuo (6):
xhci: tegra: Parameterize
On Tue, Oct 01, 2019 at 08:07:03PM +0200, Geert Uytterhoeven wrote:
> As platform_get_irq() now prints an error when the interrupt does not
> exist, counting interrupts by looping until failure causes the printing
> of scary messages like:
>
> renesas_sdhi_internal_dmac ee14.sd: IRQ index
From: Hans Andersson
Date: Oct/02/2019, 08:07:21 (UTC+00:00)
> When we read user ID / Synopsys ID we might still be in reset,
> so read muliple times if needed.
We shouldn't even try to read it if IP is in reset ...
---
Thanks,
Jose Miguel Abreu
Hi Vishal,
On Tue, Jun 04, 2019 at 07:25:56PM +0530, Vishal Sagar wrote:
> The Xilinx UHD-SDI Rx subsystem soft IP is used to capture native SDI
> streams from SDI sources like SDI broadcast equipment like cameras and
> mixers. This block outputs either native SDI, native video or
> AXI4-Stream
From: Hans Andersson
Date: Oct/02/2019, 09:02:02 (UTC+00:00)
> We assert / de-assert the reset line, but the CPU is too fast and the IP is
> still
> in reset when we later try to read user ID / Synopsys ID. Another option would
> be to add a delay after we reset.
Then I think you should fix
On Tue, Oct 01, 2019 at 08:08:34PM +0200, Geert Uytterhoeven wrote:
> As platform_get_irq() now prints an error when the interrupt does not
> exist, a scary warning may be printed for an optional interrupt:
>
> sh_mmcif ee20.mmc: IRQ index 1 not found
>
> Fix this by calling
Dear Beneficiary
Your email address has been selected to receive Visa Atm card value of
$3,000,000,00 from the United Nations,This visa atm card work in all bank atm
card world wide that has visa logo. Please reply for more information.
Regards
Jürgen Bergmann
Hi Stan,
On 9/12/19 01:29, Stanimir Varbanov wrote:
> This aims to add a requests for bandwidth scaling depending
> on the resolution and framerate (macroblocks per second). The
> exact value of the requested bandwidth is get from a
> pre-calculated tables for encoder and decoder.
>
>
On Wed, Sep 04, 2019 at 05:10:59PM +0530, Vinod Koul wrote:
> On 04-09-19, 12:48, Michal Suchánek wrote:
> > On Wed, 4 Sep 2019 15:00:52 +0530
> > Vinod Koul wrote:
> >
> > > On 30-08-19, 11:56, Randy Dunlap wrote:
> > > > On 8/30/19 11:52 AM, Michal Suchanek wrote:
> > > > > Fixes the
On 26/09/2019 13.45, Peter Ujfalusi wrote:
> ti_clk_register() calls it already so the driver should not create
> duplicated alias.
This patch will leave 'ret' as unused in of_dra7_atl_clock_setup(), I'll
send v2 in a minute or so.
> Signed-off-by: Peter Ujfalusi
> ---
>
On Wed, Oct 02, 2019 at 09:03:33AM +0200, Michal Kubecek wrote:
> On Wed, Oct 02, 2019 at 08:46:05AM +0200, Heiko Carstens wrote:
> > On Tue, Oct 01, 2019 at 10:08:01PM +0200, Jiri Kosina wrote:
> > >
> > >In file included from arch/s390/kvm/kvm-s390.c:44:
> > >
On Tue, 1 Oct 2019 at 18:53, Dietmar Eggemann wrote:
>
> On 01/10/2019 10:14, Vincent Guittot wrote:
> > On Mon, 30 Sep 2019 at 18:24, Dietmar Eggemann
> > wrote:
> >>
> >> Hi Vincent,
> >>
> >> On 19/09/2019 09:33, Vincent Guittot wrote:
>
[...]
>
> >>> + if (busiest->group_weight
On Tue, Oct 01, 2019 at 10:03:50AM -0700, Nick Desaulniers wrote:
> On Tue, Oct 1, 2019 at 1:37 AM Masahiro Yamada
> wrote:
> >
> > KernelCI reports that bcm2835_defconfig is no longer booting since
> > commit ac7c3e4ff401 ("compiler: enable CONFIG_OPTIMIZE_INLINING
> > forcibly")
Hi,
> From: Wolfram Sang, Sent: Wednesday, October 2, 2019 5:16 PM
> Tested on a R-Car H2: it does make the error message go away and the
> MMCIF device acts normal during boot. Can't enter userspace currently
> with v5.4-rc1 but this is unrelated to this patch and MMCIF. Looks like a
>
On Tue, Oct 01, 2019 at 06:27:42PM +0200, Oliver Neukum wrote:
> Am Dienstag, den 01.10.2019, 18:07 +0300 schrieb Mika Westerberg:
>
> Hi,
>
> > OK, but does that break existing .configs? I mean if you have already
> > CONFIG_THUNDERBOLT in your .config/defconfig does it now just get
> > dropped
On Tue, 1 Oct 2019 at 19:47, Valentin Schneider
wrote:
>
> On 19/09/2019 08:33, Vincent Guittot wrote:
>
> [...]
>
> > @@ -8283,69 +8363,133 @@ static inline void update_sd_lb_stats(struct
> > lb_env *env, struct sd_lb_stats *sd
> > */
> > static inline void calculate_imbalance(struct lb_env
Hi Shimoda-san, Wolfram,
On Wed, Oct 2, 2019 at 10:26 AM Yoshihiro Shimoda
wrote:
> > From: Wolfram Sang, Sent: Wednesday, October 2, 2019 5:16 PM
>
> > Tested on a R-Car H2: it does make the error message go away and the
> > MMCIF device acts normal during boot. Can't enter userspace currently
On Tue 01 Oct 2019 at 19:44, Stephen Boyd wrote:
> We don't check for errors from clk_ops::get_phase() before storing away
> the result into the clk_core::phase member. This can lead to some fairly
> confusing debugfs information if these ops do return an error. Let's
> skip the store when
Now devicetree is supposrted for probing sondwire as well.
Fixes: a2e484585ad3 ("soundwire: core: add device tree support for slave
devices")
Signed-off-by: Michal Suchanek
---
drivers/soundwire/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The device cannot be probed on !ACPI and gives this warning:
drivers/soundwire/slave.c:16:12: warning: ‘sdw_slave_add’ defined but
not used [-Wunused-function]
static int sdw_slave_add(struct sdw_bus *bus,
^
Fixes: 7c3cd189b86d ("soundwire: Add Master registration")
ti_clk_register() calls it already so the driver should not create
duplicated alias.
Signed-off-by: Peter Ujfalusi
---
Hi,
changes since v1:
- removed unused ret variable
Regards,
Peter
drivers/clk/ti/clk-dra7-atl.c | 6 --
1 file changed, 6 deletions(-)
diff --git
From: Sasha Levin
> Sent: 01 October 2019 17:06
> Subject: Re: [PATCH AUTOSEL 5.3 169/203] x86/platform/uv: Fix kmalloc() NULL
> check routine
>
> On Sun, Sep 22, 2019 at 10:25:44PM +0200, Greg KH wrote:
> >On Sun, Sep 22, 2019 at 02:43:15PM -0400, Sasha Levin wrote:
> >> From: Austin Kim
> >>
On Tue, Oct 01, 2019 at 05:05:09PM +, mario.limoncie...@dell.com wrote:
> > @@ -322,9 +398,21 @@ static int tb_switch_nvm_add(struct tb_switch *sw)
> > u32 val;
> > int ret;
> >
> > - if (!sw->dma_port)
> > + if (!nvm_readable(sw))
> > return 0;
> >
> > + /*
> > +
On Wed, Oct 02, 2019 at 10:33:29AM +0200, Michal Suchanek wrote:
> The device cannot be probed on !ACPI and gives this warning:
>
> drivers/soundwire/slave.c:16:12: warning: ‘sdw_slave_add’ defined but
> not used [-Wunused-function]
> static int sdw_slave_add(struct sdw_bus *bus,
>
On Wed, Oct 02, 2019 at 10:33:30AM +0200, Michal Suchanek wrote:
> Now devicetree is supposrted for probing sondwire as well.
>
> Fixes: a2e484585ad3 ("soundwire: core: add device tree support for slave
> devices")
> Signed-off-by: Michal Suchanek
> ---
> drivers/soundwire/Kconfig | 2 +-
> 1
On Tue, Oct 01, 2019 at 06:14:23PM +, mario.limoncie...@dell.com wrote:
> One more thought; would you consider exporting to sysfs sw->config.vendor_id?
> Maybe an attribute that is switch_vendor?
>
> Userland fwupd also does validation on the NVM and will need to follow this.
> The same check
On Wed 02-10-19 07:56:50, Yang Shi wrote:
> The deferred split THPs may get accumulated with some workloads, they
> would get shrunk when memory pressure is hit. Now we use DEFAULT_SEEKS
> to determine how many objects would get scanned then split if possible,
> but actually they are not like
On Wed, Oct 02, 2019 at 11:30:34AM +0300, Mika Westerberg wrote:
> On Tue, Oct 01, 2019 at 06:27:42PM +0200, Oliver Neukum wrote:
> > Am Dienstag, den 01.10.2019, 18:07 +0300 schrieb Mika Westerberg:
> >
> > Hi,
> >
> > > OK, but does that break existing .configs? I mean if you have already
> >
On Wed 02-10-19 06:16:43, Yang Shi wrote:
> The commit 87eaceb3faa59b9b4d940ec9554ce251325d83fe ("mm: thp: make
> deferred split shrinker memcg aware") makes deferred split queue per
> memcg to resolve memcg pre-mature OOM problem. But, all nodes end up
> sharing the same queue instead of one
On Tue, Oct 01, 2019 at 04:53:54PM +, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Mika Westerberg
> > Sent: Tuesday, October 1, 2019 9:59 AM
> > To: Limonciello, Mario
> > Cc: linux-...@vger.kernel.org; andreas.noe...@gmail.com;
> > michael.ja...@intel.com;
Deprecating the driver in Kconfig is one thing, but we also need to
let the users themselves know. Log a warning each time a device is
bound to the deprecated eeprom driver.
Signed-off-by: Jean Delvare
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
---
drivers/misc/eeprom/eeprom.c |4
1
On Wed, Oct 02, 2019 at 10:39:54AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Oct 02, 2019 at 11:30:34AM +0300, Mika Westerberg wrote:
> > On Tue, Oct 01, 2019 at 06:27:42PM +0200, Oliver Neukum wrote:
> > > Am Dienstag, den 01.10.2019, 18:07 +0300 schrieb Mika Westerberg:
> > >
> > > Hi,
> > >
> On September 30, 2019 at 5:28 PM Fabien Parent wrote:
>
>
> Since commit abf4923e97c3 ("i2c: mediatek: disable zero-length transfers
> for mt8183"), there is a NULL pointer dereference for all the SoCs
> that don't have any quirk. mtk_i2c_functionality is not checking that
> the quirks
On Tue, Oct 01, 2019 at 08:42:30PM -0700, Brian Vazquez wrote:
> Thanks for reviewing the patches Andrii!
>
> Although Daniel fixed them and applied them correctly.
After last kernel/maintainer summit at LPC, I reworked all my patchwork scripts
[0]
which I use for bpf trees in order to further
Linus,
On Fri 2019-09-20 14:25:12, Kefeng Wang wrote:
> There are pr_warning and pr_warng to show WARNING level message,
> most of the code using pr_warn, number based on next-20190919,
>
> pr_warn: 5189 pr_warning: 546 (tools: 398, others: 148)
The ratio is 10:1 in favor of pr_warn(). It
Hi Jacopo, Manivannan,
On Wed, Oct 02, 2019 at 09:54:32AM +0200, Jacopo Mondi wrote:
> Hello Manivannan,
>
> On Tue, Oct 01, 2019 at 08:25:03PM +0530, Manivannan Sadhasivam wrote:
> > The caller of v4l2_fwnode_endpoint_alloc_parse() is expected to pass a
> > valid bus_type parameter for proper
> Please cherry-pick the top commit from renesas-devel:
> 6e47c841329eb9b0 ("ARM: fix __get_user_check() in case uaccess_* calls
> are not inlined")
Thanks a lot, Geert. I can confirm this patch fixes the issue I was
seeing:
Tested-by: Wolfram Sang
Could you kindly forward this tag to
From: Bartosz Golaszewski
Remove a stray newline from the probe callback.
Signed-off-by: Bartosz Golaszewski
---
drivers/iio/pressure/bmp280-core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iio/pressure/bmp280-core.c
b/drivers/iio/pressure/bmp280-core.c
index
From: Bartosz Golaszewski
This series contains a couple changes that shrink the driver both in
terms of LOC as well as actual generated code.
Bartosz Golaszewski (4):
iio: pressure: bmp280: use bulk regulator ops
iio: pressure: bmp280: use devm_iio_device_register()
iio: pressure: bmp280:
From: Bartosz Golaszewski
We can drop some duplicate code if we use devm_action for disabling
regulators and pm. This allows us to completely remove all remove()
callbacks from both i2c and spi code.
Signed-off-by: Bartosz Golaszewski
---
drivers/iio/pressure/bmp280-core.c | 61
From: Bartosz Golaszewski
We can use the managed variant of iio_device_register() and remove
the corresponding unregister operation from the remove callback.
Signed-off-by: Bartosz Golaszewski
---
drivers/iio/pressure/bmp280-core.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff
1 - 100 of 926 matches
Mail list logo
