On Wed, May 23, 2018 at 1:00 PM, Stefan Agner wrote:
> On 23.05.2018 11:56, Krzysztof Kozlowski wrote:
>> Add a generic /memory node in each Tegra DTSI (with empty reg property,
>> to be overidden by each DTS) and set proper unit address for /memory
>> nodes to fix the DTC warnings:
>>
>> arch
[Please keep me CC'ed; I'm not subscribed to the list]
Hi!
The program shown below (also available at [0]) does the following:
* Create two sockets
* Enable SO_REUSEADDR on both
* Bind both sockets to [::1]:12345
* Spawn two threads which both call listen(2) on one socket each
* Check that
2018-03-12 19:53 GMT+08:00 Wanpeng Li :
> Provides userspace with per-VM capability(KVM_CAP_X86_DISABLE_EXITS) to
> not intercept MWAIT/HLT/PAUSE in order that to improve latency in some
> workloads.
When running cyclictest in the guest w/ vCPU pin on host and
cyclictest pin in guest, the avg late
Hi Leo,
On 22/05/18 10:52, Leo Yan wrote:
On Tue, May 22, 2018 at 04:39:20PM +0800, Leo Yan wrote:
[...]
Rather than the patch I posted in my previous email, I think below new
patch is more reasonable for me.
In the below change, 'etmq->prev_packet' is only used to store the
previous CS_ETM_R
Am Mittwoch, 23. Mai 2018, 08:51:10 CEST schrieb Elaine Zhang:
> This driver is modified to support RK3128 SoC.
>
> Signed-off-by: Elaine Zhang
applied for 4.18 or 4.19 (not sure yet).
Patch 8/13 had the licensing issue Rob pointed out, so while
with your fixed SPDX tag everything should be fin
Hi Michel,
On Wed, May 23, 2018 at 11:20 AM, M P wrote:
> On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven
> wrote:
>> On Tue, May 22, 2018 at 12:01 PM, Michel Pollet
>> wrote:
>> > + #address-cells = <1>;
>> > + #size-cells = <1>;
>> > +
>> > + cpus {
>> > + #ad
On 05/22/2018 06:41 PM, Reinette Chatre wrote:
> On 5/21/2018 4:48 PM, Mike Kravetz wrote:
>> I'm guessing that most (?all?) allocations will be order based. The use
>> cases I am aware of (hugetlbfs, Intel Cache Pseudo-Locking, RDMA) are all
>> order based. However, as commented in previous vers
Am Mittwoch, 23. Mai 2018, 08:50:31 CEST schrieb Elaine Zhang:
> According to a description from TRM, add all the power domains.
>
> Signed-off-by: Elaine Zhang
applied for 4.18 or 4.19 (not sure yet) after adding
Rob's Review-tag from v2.
Thanks
Heiko
Am Mittwoch, 23. Mai 2018, 08:50:48 CEST schrieb Elaine Zhang:
> Add binding documentation for the power domains
> found on Rockchip RK3128 SoCs.
>
> Signed-off-by: Elaine Zhang
> Acked-by: Rob Herring
applied for 4.18 or 4.19 (not sure yet).
On 05/22/2018 07:01 AM, Tudor Ambarus wrote:
> Hi, Marek,
Hi!
> On 05/21/2018 07:59 PM, Marek Vasut wrote:
>> On 05/21/2018 06:42 PM, Tudor Ambarus wrote:
>>> Hi, Marek,
>>
>> [...]
>>
> This is a transitional patch: non-uniform erase maps will be used
> later
> when initialized based
> >>> I think the bigger issues as you've pointed out are the cost of
> >>> the additional spin lock and should the additional state be
> >>> stored in-band (fewer cache lines) or out-of band (less risk of
> >>> breaking due to unpredictable application behavior).
> >>
> >> We don't need the spinlo
On 23/05/18 12:00, Oleksandr Andrushchenko wrote:
> On 05/23/2018 12:19 PM, Juergen Gross wrote:
>> On 21/05/18 09:39, Oleksandr Andrushchenko wrote:
>>> From: Oleksandr Andrushchenko
>>>
>>> Building for a 32-bit target results in warnings from casting
>>> between a 32-bit pointer and a 64-bit in
> -Original Message-
> From: Sudeep Holla
> Sent: Wednesday, May 23, 2018 13:40
> To: Ilia Lin ; vire...@kernel.org; n...@ti.com;
> sb...@kernel.org; r...@kernel.org; mark.rutl...@arm.com;
> r...@rjwysocki.net; linux...@vger.kernel.org; devicet...@vger.kernel.org;
> linux-kernel@vger.ker
On 23.05.2018 11:56, Krzysztof Kozlowski wrote:
> Add a generic /memory node in each Tegra DTSI (with empty reg property,
> to be overidden by each DTS) and set proper unit address for /memory
> nodes to fix the DTC warnings:
>
> arch/arm/boot/dts/tegra20-harmony.dtb: Warning (unit_address_vs_
From: kbuild test robot
net/netfilter/nft_numgen.c:117:1-3: WARNING: PTR_ERR_OR_ZERO can be used
Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Generated by: scripts/coccinelle/api/ptr_ret.cocci
Fixes: d734a2888922 ("netfilter: nft_numgen: add map lookups for numgen
statements")
Am Mittwoch, 23. Mai 2018, 08:48:40 CEST schrieb Elaine Zhang:
> From: Finley Xiao
>
> Solve the pd could only ever turn off but never turn them on again,
> If the pd registers have the writemask bits.
>
> Fix up the code error for commit:
> commit 79bb17ce8edb3141339b5882e372d0ec7346217c
Am Mittwoch, 23. Mai 2018, 08:48:39 CEST schrieb Elaine Zhang:
> From: Caesar Wang
>
> This driver is modified to support RK3036 SoC.
>
> Signed-off-by: Caesar Wang
> Signed-off-by: Elaine Zhang
> @@ -102,6 +103,14 @@ struct rockchip_pmu {
> .ack_mask = (ack >= 0) ? BIT(ack) : 0,
On 22/05/18 19:47, Ray Jui wrote:
Update the SP805 binding document to add optional 'timeout-sec'
devicetree property
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
Documentation/devicetree/bindings/watchdog/sp805-wdt.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Document
On Wed, May 23, 2018 at 10:26:23AM +, Robin Gong wrote:
> >
> > >
> > > + u32 bd_size_sum;
> > This variable is never used for anything.
> Yes, it's not for significative use but debug to see how many current
> bds used.
I am not convinced this is useful. The vari
Am Mittwoch, 23. Mai 2018, 08:48:37 CEST schrieb Elaine Zhang:
> From: Caesar Wang
>
> According to a description from TRM, add all the power domains.
>
> Signed-off-by: Caesar Wang
> Signed-off-by: Elaine Zhang
applied for 4.18 or 4.19 (not sure yet) after adding
Rob's Review-tag from v2.
Am Mittwoch, 23. Mai 2018, 08:48:38 CEST schrieb Elaine Zhang:
> From: Caesar Wang
>
> Add binding documentation for the power domains
> found on Rockchip RK3036 SoCs.
>
> Signed-off-by: Caesar Wang
> Signed-off-by: Elaine Zhang
> Acked-by: Rob Herring
applied for 4.18 or 4.19 (not sure yet
On Sat 2018-05-19 21:53:02, Christian Krüger wrote:
> Hi,
>
> Since the old "in-order-execution" Intel CPUs like the Intel Atom N270
> (known for being installed in many Netbooks and Nettops) are not sensitive
> for "Meltdown" & "Spectre" , wouldn't it be a good idea to exclude these
> anyway "wea
Hi,
On 05/22/2018 04:06 PM, Marc Zyngier wrote:
On a system where firmware can dynamically change the state of the
mitigation, the CPU will always come up with the mitigation enabled,
including when coming back from suspend.
If the user has requested "no mitigation" via a command line option,
l
Hi Laura,
On Tue, May 22, 2018 at 04:50:49PM -0700, Laura Abbott wrote:
> Commit 15122ee2c515 ("arm64: Enforce BBM for huge IO/VMAP mappings")
> disallowed block mappings for ioremap since that code does not honor
> break-before-make. The same APIs are also used for permission updating
> though an
This patch is required when the pcie controller sits on a bus with
its own power domain and clocks which are controlled via a bus driver
like simple pm bus. As these bus driver have runtime pm enabled, it makes
sense to update the usage counter so that the runtime pm does not suspend
the clks or po
On 23.05.2018 11:56, Krzysztof Kozlowski wrote:
> Remove the usage of skeleton.dtsi because it was deprecated since commit
> 9c0da3cc61f1 ("ARM: dts: explicitly mark skeleton.dtsi as deprecated").
> It also allows later to fix DTC warnings for missing unit name in
> /memory nodes.
>
> The /chosen
On 23-05-18, 11:10, Srinivas Kandagatla wrote:
>
>
> On 23/05/18 07:15, Vinod wrote:
> > On 18-05-18, 00:07, Bjorn Andersson wrote:
> >
> > > diff --git a/drivers/pci/dwc/pcie-qcom.c b/drivers/pci/dwc/pcie-qcom.c
> > > index 5897af7d3355..3f35098b71b1 100644
> > > --- a/drivers/pci/dwc/pcie-qcom
On 23.05.2018 08:58, Viresh Kumar wrote:
> On 23-05-18, 00:14, Dmitry Osipenko wrote:
>> Tegra20-cpufreq driver missed enabling the CPU clocks. This results in a
>> clock-enable refcount disbalance on PLL_P <-> PLL_X reparent, causing
>> PLL_X to get disabled while it shouldn't. Fix this by enablin
On Tue, 22 May 2018 20:03:41 +0200
Peter Rosin wrote:
> On 2018-04-11 17:34, Nicolas Ferre wrote:
> > On 11/04/2018 at 16:44, Peter Rosin wrote:
> >> Hi Nicolas,
> >>
> >> Boris asked for your input on this (the datasheet difference appears to
> >> have no bearing on the issue) elsewhere in the
On Tue 2018-05-15 14:57:44, Steven Rostedt wrote:
> On Tue, 15 May 2018 09:55:13 -0700
> Linus Torvalds wrote:
>
> > On Tue, May 15, 2018 at 7:06 AM Steven Rostedt wrote:
> > > - smp_mb();
> > > + smp_wmb();
> > > WRITE_ONCE(have_filled_random_ptr_key, true);
> >
> >
> >
Hi!
> When system is rebooted, halted or kexeced device_shutdown() is
> called.
>
> This function shuts down every single device by calling either:
>
> dev->bus->shutdown(dev)
> dev->driver->shutdown(dev)
...
> Finally, with ixgbe_shutdown() it takes 0.37 for each device, but that ti
On 23/05/18 10:40, Ilia Lin wrote:
> In Certain QCOM SoCs like apq8096 and msm8996 that have KRYO processors,
> the CPU frequency subset and voltage value of each OPP varies
> based on the silicon variant in use. Qualcomm Process Voltage Scaling Tables
> defines the voltage and frequency value ba
On Tue, 2018-05-22 at 13:55 +0200, Hans Verkuil wrote:
> On 21/05/18 18:59, Ezequiel Garcia wrote:
> > From: Gustavo Padovan
> >
> > Now that we've introduced the V4L2_FMT_FLAG_UNORDERED flag,
> > mark the appropriate formats.
> >
> > v2: Set unordered flag before calling the driver callback.
>
On 23.5.2018 11:44, Linus Walleij wrote:
> On Tue, May 15, 2018 at 3:26 PM, Michal Simek wrote:
>
>> Have you done any decision about this patch?
>
> Yeah I applied the patch. It's a bit of "choose the lesser evil" approach
> but what can I do...
Thanks,
Michal
On 05/19/2018 12:27 AM, Anders Roxell wrote:
> The reuseport_bpf_numa test case fails there's no numa support. The
> test shouldn't fail if there's no support it should be skipped.
>
> Fixes: 3c2c3c16aaf6 ("reuseport, bpf: add test case for bpf_get_numa_node_id")
> Signed-off-by: Anders Roxell
On Wed, May 23, 2018 at 1:48 PM, Maxime Ripard
wrote:
> On Wed, May 23, 2018 at 11:44:56AM +0530, Jagan Teki wrote:
>> On Tue, May 22, 2018 at 8:00 PM, Maxime Ripard
>> wrote:
>> > On Tue, May 22, 2018 at 06:52:28PM +0530, Jagan Teki wrote:
>> >> Amarula A64-Relic is Allwinner A64 based IoT devic
On 二, 2018-05-22 at 12:09 +0200, Sascha Hauer wrote:
> Hi Robin,
>
> Several comments inside.
>
> Sascha
>
> On Fri, Mar 23, 2018 at 12:18:19AM +0800, Robin Gong wrote:
> >
> > The legacy sdma driver has below limitations or drawbacks:
> > 1. Hardcode the max BDs number as "PAGE_SIZE / sizeof
On Wed, 23 May 2018 04:56:45 +0200
Dong Jia Shi wrote:
Still s/traceponits/tracepoints/ (can fix up when applying).
> From: Halil Pasic
>
> Add some tracepoints so we can inspect what is not working as is should.
>
> Signed-off-by: Halil Pasic
> Signed-off-by: Dong Jia Shi
> ---
> drivers/
On 23/05/18 10:47, Ulf Hansson wrote:
On 23 May 2018 at 11:45, Jon Hunter wrote:
On 23/05/18 10:33, Ulf Hansson wrote:
On 23 May 2018 at 11:27, Rajendra Nayak wrote:
On 05/23/2018 02:37 PM, Jon Hunter wrote:
On 23/05/18 07:12, Ulf Hansson wrote:
...
Thanks for sending this. Belie
On Wed, 23 May 2018 04:56:41 +0200
Dong Jia Shi wrote:
> Dear Reviewers,
>
> Here is a new version for this patch series.
>
> We didn't get agreement on patch #4 (#5 in v2) in the former cycle though,
> I made it based on my understanding. We can continue discussing on it.
I'll probably go ahe
Sergey Senozhatsky wrote:
> On (05/17/18 20:21), Sergey Senozhatsky wrote:
> > Dunno...
> > For instance, can we store context tracking info as a extended record
> > data? We have that dict/dict_len thing. So may we can store tracking
> > info there? Extended records will appear on the serial conso
>> If you take a look at
>> arch/arm64/boot/dts/xilinx/zynqmp-zcu100-revC.dts
>> which is Ultra96 board gpio-line-names are filled there for the whole PS
>> part. Definitely take a look and let know if you find out any issue there.
>
> It looks good. I even managed to boot my Ultra96 board which
>
On Mon, May 21, 2018 at 07:28:26PM +0100, Will Deacon wrote:
> Hi Dave,
>
> On Mon, May 14, 2018 at 06:14:17PM +0100, Dave Martin wrote:
> > The core framework for the prctl() syscall is unloved and looking
> > rather crusty these days. It also relies on defining ancillary
> > boilerplate macros
On 23/05/18 11:47, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit 152db033d775 (schedutil: Allow cpufreq requests to be made
> even when kthread kicked) made changes to prevent utilization updates
> from being discarded during processing a previous request, but it
> left a small wi
On 23-05-18, 11:47, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit 152db033d775 (schedutil: Allow cpufreq requests to be made
> even when kthread kicked) made changes to prevent utilization updates
> from being discarded during processing a previous request, but it
> left a small w
Hi Marc,
On 05/22/2018 04:06 PM, Marc Zyngier wrote:
In order to avoid checking arm64_ssbd_callback_required on each
kernel entry/exit even if no mitigation is required, let's
add yet another alternative that by default jumps over the mitigation,
and that gets nop'ed out if we're doing dynamic m
Hi Marc,
On 05/22/2018 04:06 PM, Marc Zyngier wrote:
We're about to need the mitigation state in various parts of the
kernel in order to do the right thing for userspace and guests.
Let's expose an accessor that will let other subsystems know
about the state.
Signed-off-by: Marc Zyngier
Rev
On 23/05/18 07:15, Vinod wrote:
On 18-05-18, 00:07, Bjorn Andersson wrote:
diff --git a/drivers/pci/dwc/pcie-qcom.c b/drivers/pci/dwc/pcie-qcom.c
index 5897af7d3355..3f35098b71b1 100644
--- a/drivers/pci/dwc/pcie-qcom.c
+++ b/drivers/pci/dwc/pcie-qcom.c
@@ -1088,6 +1088,8 @@ static int qcom_p
Hi Marc,
On 05/22/2018 04:06 PM, Marc Zyngier wrote:
On a system where the firmware implements ARCH_WORKAROUND_2,
it may be useful to either permanently enable or disable the
workaround for cases where the user decides that they'd rather
not get a trap overhead, and keep the mitigation permanent
Data about the implemented readout modes is partially stored in
imx274_formats[], the rest is scattered in several arrays. The latter
are then accessed using the mode index, e.g.:
min_frame_len[priv->mode_index]
Consolidate all these data in imx274_formats[], and store a pointer to
the selected
imx274_write_table() is a mere wrapper (and the only user) to
imx274_regmap_util_write_table_8(). Remove this useless indirection by
merging the two functions into one.
Also get rid of the wait_ms_addr and end_addr parameters since it does
not make any sense to give them any values other than
IMX2
After restructuring struct imx274_frmfmt, the mode_index field is
still in use only for two dev_dbg() calls in imx274_s_stream(). Let's
remove it and avoid duplicated information.
Replacing the first usage requires some rather annoying but trivial
pointer math. The other one can be removed entirel
The current probe function calls v4l2_ctrl_handler_setup() before
initializing the format info. This triggers call paths such as:
imx274_probe -> v4l2_ctrl_handler_setup -> imx274_s_ctrl ->
imx274_set_exposure, where priv->mode_index is accessed before being
assigned.
This is wrong but does not tr
Hi Peter,
On 10.05.2018 13:14, Peter Zijlstra wrote:
> On Thu, May 10, 2018 at 12:42:38PM +0300, Alexey Budankov wrote:
>>> The Changelog needs to state that user_regs->bp is in fact valid and
>>
>> That actually was tested on binaries compiled without and with BP exposed
>> and in the latter cas
On 23-05-18, 02:42, Joel Fernandes wrote:
> Probably. But then Rafael is changing single policy to use the lock
> so then barrier wouldn't be needed at all. In that case, both mine
> and Rafael new patch can go into stable which handles your race (
> optimization == fix in this case :P )
Yeah, we
Currently this driver does not support cropping. The supported modes
are the following, all capturing the entire area:
- 3840x2160, 1:1 binning (native sensor resolution)
- 1920x1080, 2:1 binning
- 1280x720, 3:1 binning
The set_fmt callback chooses among these 3 configurations the one that
ma
IMX274_DEFAULT_MODE is defined but not used. Start using it, so the
default can be more easily changed without digging into the code.
Signed-off-by: Luca Ceresoli
Cc: Sakari Ailus
---
Changed v2 -> v3: nothing
Changed v1 -> v2:
- add "media: " prefix to commit message
---
drivers/media/i2c/i
Tables of struct reg_8 are used to simplify multi-byte register
assignment. However filling these snippets with values computed at
runtime is currently implemented by very similar functions doing the
needed shift & mask manipulation.
Replace all those functions with a unique helper function to fil
Hi Marc,
On 05/22/2018 04:06 PM, Marc Zyngier wrote:
As for Spectre variant-2, we rely on SMCCC 1.1 to provide the
discovery mechanism for detecting the SSBD mitigation.
A new capability is also allocated for that purpose, and a
config option.
Signed-off-by: Marc Zyngier
---
arch/arm64/Kcon
Hi,
this patchset introduces cropping support for the Sony IMX274 sensor
using the SELECTION API.
v3 has a few minor improvements over v2. It also removes the first 6
patches, already applied on the media_tree master branch.
After v2 there has been a short discussion with Sakari Ailus on how
cr
On 23-05-18, 12:40, Ilia Lin wrote:
> In Certain QCOM SoCs like apq8096 and msm8996 that have KRYO processors,
> the CPU frequency subset and voltage value of each OPP varies
> based on the silicon variant in use. Qualcomm Process Voltage Scaling Tables
> defines the voltage and frequency value bas
Hi Marc,
On 05/22/2018 04:06 PM, Marc Zyngier wrote:
In a heterogeneous system, we can end up with both affected and
unaffected CPUs. Let's check their status before calling into the
firmware.
Signed-off-by: Marc Zyngier
Reviewed-by: Julien Grall
Cheers,
---
arch/arm64/kernel/cpu_errat
On 23 May 2018 at 08:48, Elaine Zhang wrote:
> add power domain support for RK3036/RK3128/RK3228/PX30 Soc.
> fix up the wrong value when set power domain up.
>
> Change in V2:
> Fix up the commit message description and Assign author.
>
> Change in V3:
> [PATCH 01/13]: The Copyright description us
On 05/23/2018 12:19 PM, Juergen Gross wrote:
On 21/05/18 09:39, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Building for a 32-bit target results in warnings from casting
between a 32-bit pointer and a 64-bit integer. Fix the warnings
by casting those pointers to uintptr_t firs
On 23-05-18, 10:40, Russell King - ARM Linux wrote:
> On Wed, May 23, 2018 at 12:05:24PM +0300, Ilia Lin wrote:
> > + np = dev_pm_opp_of_get_opp_desc_node(cpu_dev);
> > + if (IS_ERR(np))
> > + return PTR_ERR(np);
> ...
> > +
> > + pdev = platform_device_register_simple("cpufreq-dt",
From: Esben Haabendal
This fixes a race condition, where the DMAEN bit ends up being set after
I2C slave has transmitted a byte following the dummy read. When that
happens, an interrupt is generated instead, and no DMA request is generated
to kickstart the DMA read, and a timeout happens after D
On 05/23/2018 12:07 AM, Andrew Morton wrote:
> On Tue, 22 May 2018 22:50:12 +0300 Andrey Ryabinin
> wrote:
>
>>
>>
>> On 05/22/2018 07:36 PM, David Hildenbrand wrote:
>>> On 22.05.2018 18:26, Andrey Ryabinin wrote:
On 05/22/2018 01:07 PM, David Hildenbrand wrote:
> Using mod
Remove the usage of skeleton.dtsi because it was deprecated since commit
9c0da3cc61f1 ("ARM: dts: explicitly mark skeleton.dtsi as deprecated").
It also allows later to fix DTC warnings for missing unit name in
/memory nodes.
The /chosen and /aliases nodes are added only when dependent DTSes do
no
Colibri-T20 can come in 256 MB RAM (with 512 MB NAND) or 512 MB RAM
(with 1024 MB NAND) flavors. Both of them will use the same DTSI
expecting the bootloader to do the fixup of /memory node. However in
case it does not happen, let's stay on safe side by limiting the memory
to 256 MB for both vers
Remove unneeded address/size cells properties and unit addresses to fix
DTC warnings like:
arch/arm/boot/dts/tegra30-apalis-eval.dtb: Warning (unit_address_vs_reg):
/i2c@7000d000/stmpe811@41/stmpe_touchscreen@0: node has a unit name,
but no reg property
arch/arm/boot/dts/tegra30-a
Add a generic /memory node in each Tegra DTSI (with empty reg property,
to be overidden by each DTS) and set proper unit address for /memory
nodes to fix the DTC warnings:
arch/arm/boot/dts/tegra20-harmony.dtb: Warning (unit_address_vs_reg):
/memory: node has a reg or ranges property,
From: Esben Haabendal
Always update the stopped state when busy status have been checked.
This is identical to what was done before, with the exception of error
handling.
Without this change, some errors cause the stopped state to be left in
incorrect state in i2c_imx_stop(), i2c_imx_dma_read(),
On 23-05-18, 10:00, Daniel Lezcano wrote:
> On 23/05/2018 07:41, Viresh Kumar wrote:
> > Right and that's why I said "Which is fine" in my comment above. My
> > question was more on why we error out in idle_injection_start() if
> > run_duration_ms is 0.
> >
> > Just for my understanding, is it a v
From: Esben Haabendal
Make sure to call reinit_completion() before dma is started to avoid race
condition where reinit_compleition() is called after complete() and before
wait_for_completion_timeout().
Signed-off-by: Esben Haabendal
---
drivers/i2c/busses/i2c-imx.c | 3 +--
1 file changed, 1 i
From: Esben Haabendal
Gives substantial performance improvement for transfers larger than 16
bytes (DMA_THRESHOLD). Smaller transfers are unaffected.
Signed-off-by: Esben Haabendal
---
arch/arm/boot/dts/ls1021a.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/l
On Wed, May 23, 2018 at 2:19 PM, Daniel Vetter wrote:
> On Mon, May 21, 2018 at 10:27:44AM +0530, Souptick Joarder wrote:
>> On Thu, May 10, 2018 at 7:18 PM, Souptick Joarder
>> wrote:
>> > On Wed, Apr 25, 2018 at 10:29 AM, Souptick Joarder
>> > wrote:
>> >> Use new return type vm_fault_t for
Dear all,
I just noticed that replying to my earlier email thread failed, and that
I thereby created a new thread. The original thread is the following one:
https://lkml.org/lkml/2018/2/16/274
I am sorry for the confusion!
Best,
Norbert
On 05/23/2018 08:22 AM, Norbert Manthey wrote:
> The curr
On Tue, May 22, 2018 at 02:59:50PM -0700, Guenter Roeck wrote:
> Most people are not aware that they have a backwards compatibility problem
> with the topology file. They will typically notice and report that it is
> impossible to get audio working with an upstream kernel on a recent
> Chromebook,
On Wed, May 16, 2018 at 7:40 PM, Geert Uytterhoeven
wrote:
> I guess I should base my next pull request on the new commit
> 73dacc3403436fc2 ("pinctrl: sh-pfc: Add r8a77470 PFC support") in your
> tree, instead of on my previous pull request? Else there will be some
> conflicts (I checked: so far
On Mon, May 21, 2018 at 02:57:18PM -0700, Vito Caputo wrote:
> On Mon, May 21, 2018 at 12:53:20PM -0700, Vito Caputo wrote:
> > Hello all,
> >
> > 4.17-rc4 (my latest kernel ATM) consistently fails to start xgalaga
> > without -window. I will try find time to build the latest rc this
> > evening.
From: Rafael J. Wysocki
Commit 152db033d775 (schedutil: Allow cpufreq requests to be made
even when kthread kicked) made changes to prevent utilization updates
from being discarded during processing a previous request, but it
left a small window in which that still can happen in the one-CPU
polic
On Fri, May 4, 2018 at 6:53 PM, Grigoryev Denis wrote:
> The driver stores the result of irq_set_type() in the internal variables
> irq_trig_raise and irq_trig_fall, which later are used to determine
> the GPIOs that must be re-configured as input. These variables retain their
> value between gpi
On 23 May 2018 at 11:45, Jon Hunter wrote:
>
> On 23/05/18 10:33, Ulf Hansson wrote:
>>
>> On 23 May 2018 at 11:27, Rajendra Nayak wrote:
>>>
>>>
>>>
>>> On 05/23/2018 02:37 PM, Jon Hunter wrote:
On 23/05/18 07:12, Ulf Hansson wrote:
...
> Thanks for sending
On Wed, May 16, 2018 at 9:33 AM, Jisheng Zhang
wrote:
> Use the appropriate SPDX license identifier in the berlin pinctrl
> driver source file and drop the previous license text.
>
> Signed-off-by: Jisheng Zhang
Patch applied.
Yours,
Linus Walleij
On 23/05/18 10:33, Ulf Hansson wrote:
On 23 May 2018 at 11:27, Rajendra Nayak wrote:
On 05/23/2018 02:37 PM, Jon Hunter wrote:
On 23/05/18 07:12, Ulf Hansson wrote:
...
Thanks for sending this. Believe it or not this has still been on my to-do list
and so we definitely need a solution f
This patch fixed the potential illegal operation when using the
extend sge buffer cross page in post send operation. The bug
will cause the calltrace.
Reported-by: Jie Chen
Reported-by: Xiping Zhang (Francis)
Fixes: b1c158350968("RDMA/hns: Get rid of virt_to_page and vmap calls after
dma_alloc_
This patchset included fixing bug, some optimization, reset
process for hns driver.
v1->v2: 1.pull the patch out of the series. The name of the patch is
RDMA/hns: Implement the disassociate_ucontext API.
2.Modify the fixes statement according to Leon's comment.
3.Address
This patch increases checking CMQ status timeout value and
uses the same value with NIC driver to avoid deficiency of
time.
Signed-off-by: Wei Hu (Xavier)
Reviewed-by: Leon Romanovsky
---
drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
On Tue, May 15, 2018 at 3:26 PM, Michal Simek wrote:
> Have you done any decision about this patch?
Yeah I applied the patch. It's a bit of "choose the lesser evil" approach
but what can I do...
Yours,
Linus Walleij
This patch added reset process for RoCE in hip08.
Signed-off-by: Wei Hu (Xavier)
---
v1->v2: 1.Delete handle->priv = NULL in hns_roce_hw_v2_uninit_instance.
2.Add hns_roce_hw_v2_reset_notify_init callback function,
When RoCE reinit failed in this function, inform NIC driver.
This patch modified uar allocation algorithm in hns_roce_uar_alloc
function to avoid bitmap exhaust.
Signed-off-by: Wei Hu (Xavier)
Reviewed-by: Leon Romanovsky
---
drivers/infiniband/hw/hns/hns_roce_device.h | 1 +
drivers/infiniband/hw/hns/hns_roce_pd.c | 10 ++
2 files changed,
On May 23, 2018 2:01:01 AM PDT, Viresh Kumar wrote:
>On 22-05-18, 15:09, Joel Fernandes wrote:
>> I agree with the race you describe for single policy slow-switch.
>Good find :)
>>
>> The mainline sugov_work could also do such reordering in sugov_work,
>I think. Even
>> with the mutex_unlock in
On Wed, May 2, 2018 at 4:19 PM, Michal Simek wrote:
> On 2.5.2018 15:56, Linus Walleij wrote:
>> Would it be possible that I apply the patch, and somehow also
>> establish some understanding with all users of the Xilinx
>> platform that whatever legacy applications are out there
>> must start to
> > commit a9c002732695eab2096580a0d1a1687bc2f95928
> > Author: ming_qian
> > Date: Wed May 9 10:13:08 2018 +0800
> >
> > media: uvcvideo: Support UVC 1.5 video probe & commit controls
> >
> > The length of UVC 1.5 video control is 48, and it is 34 for UVC 1.1.
> > Change it to 48
On Wednesday, May 23, 2018 12:55:53 AM CEST Joel Fernandes wrote:
> From: "Joel Fernandes (Google)"
>
> Currently there is a chance of a schedutil cpufreq update request to be
> dropped if there is a pending update request. This pending request can
> be delayed if there is a scheduling delay of t
On Wed, May 23, 2018 at 12:05:24PM +0300, Ilia Lin wrote:
> + np = dev_pm_opp_of_get_opp_desc_node(cpu_dev);
> + if (IS_ERR(np))
> + return PTR_ERR(np);
...
> +
> + pdev = platform_device_register_simple("cpufreq-dt", -1, NULL, 0);
> + if (!IS_ERR(pdev))
Do you need to
In Certain QCOM SoCs like apq8096 and msm8996 that have KRYO processors,
the CPU frequency subset and voltage value of each OPP varies
based on the silicon variant in use. Qualcomm Process Voltage Scaling Tables
defines the voltage and frequency value based on the msm-id in SMEM
and speedbin blown
[v10]
* Split the series into domains
* Addressed comments from Viresh and Sudeep about logical CPU numbering.
The qcom-cpufreq-kryo driver is aimed to support different SOC versions.
The driver reads eFuse information and chooses the required OPP subset
by passing the OPP supported-hw parameter
The qcom-cpufreq-kryo driver reads the msm-id and efuse value from the SoC
to provide the OPP framework with required information.
This is used to determine the voltage and frequency value for each OPP of
operating-points-v2 table when it is parsed by the OPP framework.
This change adds documentat
On Wed, May 16, 2018 at 10:05 AM, Souptick Joarder wrote:
> On Fri, May 11, 2018 at 2:52 PM, Russell King - ARM Linux
> wrote:
>> On Thu, May 10, 2018 at 08:34:48PM +0530, Souptick Joarder wrote:
>>> Use new return type vm_fault_t for fault handler in
>>> struct vm_operations_struct. For now, thi
801 - 900 of 1075 matches
Mail list logo
