On 09/03, Jonathan Corbet wrote:
> On Wed, 2 Sep 2020 17:08:31 -0700
> Randy Dunlap wrote:
>
> > From: Randy Dunlap
> >
> > Correct grammar and spelling.
> >
> > Drop duplicate section for resize.f2fs.
> >
> > Change one occurrence of F2fs to F2FS for consistency.
> >
> > Signed-off-by:
On Thu, Sep 3, 2020 at 1:40 AM Paolo Abeni wrote:
>
> On Wed, 2020-09-02 at 22:01 -0700, Cong Wang wrote:
> > Can you test the attached one-line fix? I think we are overthinking,
> > probably all
> > we need here is a busy wait.
>
> I think that will solve, but I also think that will kill NOLOCK
On Thu, Sep 3, 2020 at 8:25 AM Namhyung Kim wrote:
>
> The new string should have enough space for the original string and
> the back slashes IMHO.
>
> Cc: John Garry
> Cc: Kajol Jain
> Cc: Ian Rogers
> Signed-off-by: Namhyung Kim
Reviewed-by: Ian Rogers
Definitely looks like the right
On 09/03, Daeho Jeong wrote:
> From: Daeho Jeong
>
> writepages() can be concurrently invoked for the same file by different
> threads such as a thread fsyncing the file and a kworker kernel thread.
> So, changing i_compr_blocks without protection is racy and we need to
> protect it by changing
On Wed, Sep 02, 2020 at 04:28:47PM +0100, Suzuki K Poulose wrote:
> If the specified/hinted sink is not reachable from a subset of the CPUs,
> we could end up unable to trace the event on those CPUs. This
> is the best effort we could do until we support 1:1 configurations.
> Fail gracefully in
On Thu, Sep 3, 2020 at 11:27 AM Mark Brown wrote:
>
> On Thu, Sep 03, 2020 at 10:47:38AM -0600, Rob Herring wrote:
>
> > > [2/2] ASoC: odroid: Use unevaluatedProperties
> > > commit: a57307ca6b661e16f9435a25f376ac277c3de697
>
> > This one should be reverted/dropped too. Patch 1 is fine.
>
>
Le 03/09/2020 à 17:59, Christoph Hellwig a écrit :
Christophe reported a major speedup due to avoiding the iov_iter
overhead, so just add this trivial function. Note that /dev/zero
already implements both an iter and non-iter writes so this just
makes it more symmetric.
Christophe Leroy
On Thu, Sep 3, 2020 at 7:12 AM Mohammed Gamal wrote:
>
> This patch exposes allow_smaller_maxphyaddr to the user as a module parameter.
>
> Since smaller physical address spaces are only supported on VMX, the parameter
> is only exposed in the kvm_intel module.
> Modifications to VMX page fault
Le 03/09/2020 à 18:12, Christoph Hellwig a écrit :
On Thu, Sep 03, 2020 at 01:57:39PM +0300, Andy Shevchenko wrote:
+{
+ if (!dev)
+ return (U32_MAX >> page_shift) + 1;
+ return (dma_get_seg_boundary(dev) >> page_shift) + 1;
Can it be better to do something like
On 9/3/2020 9:42 AM, Dave Hansen wrote:
On 9/3/20 9:32 AM, Andy Lutomirski wrote:
Taking the config register out of the init state is illogical, as is
writing to SSP while the config register is in its init state.
What's so special about the INIT state? It's optimized by XSAVES, but
it's just
On Thu, Sep 03, 2020 at 07:34:58PM +0200, Florian Weimer wrote:
> * Minchan Kim:
>
> > On Tue, Sep 01, 2020 at 08:46:02PM +0200, Florian Weimer wrote:
> >> * Minchan Kim:
> >>
> >> > ssize_t process_madvise(int pidfd, const struct iovec *iovec,
> >> > unsigned long vlen,
The returned value of bpf_object__open_file() should be checked with
IS_ERR() rather than NULL. This fix makes test_progs not crash when
test_global_data.o is not present.
Signed-off-by: Hao Luo
---
tools/testing/selftests/bpf/prog_tests/global_data_init.c | 2 +-
1 file changed, 1
On Thu, Sep 03, 2020 at 07:51:07PM +0200, Christophe Leroy wrote:
>
>
> Le 03/09/2020 à 17:59, Christoph Hellwig a écrit :
> > Christophe reported a major speedup due to avoiding the iov_iter
> > overhead, so just add this trivial function. Note that /dev/zero
> > already implements both an
On 03/09/20 19:57, Jim Mattson wrote:
> On Thu, Sep 3, 2020 at 7:12 AM Mohammed Gamal wrote:
>> This patch exposes allow_smaller_maxphyaddr to the user as a module
>> parameter.
>>
>> Since smaller physical address spaces are only supported on VMX, the
>> parameter
>> is only exposed in the
Correct a typo in the compatible - missing trailing 's'.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/crypto/samsung-slimsss.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/crypto/samsung-slimsss.yaml
Pass the error directly from devm_clk_get() to describe the real reason,
instead of fixed ENOENT. Do not print error messages on deferred probe.
Signed-off-by: Krzysztof Kozlowski
---
drivers/crypto/s5p-sss.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git
Add missing and fix existing kerneldoc to silence W=1 warnings:
drivers/crypto/s5p-sss.c:333: warning: Function parameter or member 'pclk'
not described in 's5p_aes_dev'
drivers/crypto/s5p-sss.c:373: warning: Function parameter or member 'sgl' not
described in 's5p_hash_reqctx'
On Thu, Sep 3, 2020 at 1:36 PM David Hildenbrand wrote:
>
> On 03.09.20 16:00, Pavel Tatashin wrote:
> > There is a race during page offline that can lead to infinite loop:
> > a page never ends up on a buddy list and __offline_pages() keeps
> > retrying infinitely or until a termination signal
On Thu, 3 Sep 2020 at 19:49, Rob Herring wrote:
>
> On Thu, Sep 3, 2020 at 11:27 AM Mark Brown wrote:
> >
> > On Thu, Sep 03, 2020 at 10:47:38AM -0600, Rob Herring wrote:
> >
> > > > [2/2] ASoC: odroid: Use unevaluatedProperties
> > > > commit: a57307ca6b661e16f9435a25f376ac277c3de697
> >
On Wed, Sep 2, 2020 at 3:47 PM Joel Fernandes wrote:
>
> On Wed, Sep 2, 2020 at 4:01 PM Nachammai Karuppiah
> wrote:
> >
> > Hi,
> >
> > This patch series adds support to store trace events in pstore.
> >
> > Storing trace entries in persistent RAM would help in understanding what
> > happened
> For performance reasons during system updates/reboots we do not erase
> memory content. The memory content is erased only on power cycle,
> which we do not do in production.
>
> Once we hot-remove the memory, we convert it back into DAXFS PMEM
> device, format it into EXT4, mount it as DAX file
On Thu, Sep 3, 2020 at 2:47 AM Eric Dumazet wrote:
> This commit might be related :
>
> commit 4e407ff5cd67ec76a1deec227b7982dc7f66
> Author: Cong Wang
> Date: Sun Aug 19 12:22:12 2018 -0700
>
> act_ife: move tcfa_lock down to where necessary
It does not look like my commit's fault.
On 9/3/20 8:36 AM, pet...@infradead.org wrote:
> On Thu, Sep 03, 2020 at 08:19:38AM -0700, Guenter Roeck wrote:
>> This doesn't compile for me - there is no "name" parameter in __DO_TRACE().
>>
>> Error log:
>> In file included from ./include/linux/rculist.h:11,
>> from
Ashok,
On Thu, Sep 03 2020 at 09:35, Ashok Raj wrote:
> On Wed, Aug 26, 2020 at 01:16:28PM +0200, Thomas Gleixner wrote:
>> This is the second version of providing a base to support device MSI (non
>> PCI based) and on top of that support for IMS (Interrupt Message Storm)
>
> s/Storm/Store
>
>
On 2020-09-03 23:08, Doug Anderson wrote:
Hi,
On Thu, Sep 3, 2020 at 9:04 AM Sai Prakash Ranjan
wrote:
Hi,
On 2020-09-03 21:24, Doug Anderson wrote:
> Hi,
>
> On Thu, Sep 3, 2020 at 8:47 AM Sai Prakash Ranjan
> wrote:
>>
>> On 2020-09-03 19:16, Doug Anderson wrote:
>> > Hi,
>> >
>> > On
Dear Linux developers,
After searching the internet for countless hours and not finding any
solution, I hope you can point me in the right direction for my
following problem:
I'm trying to install a 3-node cluster (proxmox/ceph) and experience
random freezes. The node can either be completely
Commit 78a68acf3d33 ("ARM: dts: exynos: Switch to dedicated Odroid XU3
sound card binding") added assigned clocks under sound device node.
However the dtschema expects "clocks" property if "assigned-clocks" are
used. Add reference to input clock, the parent used in
"assigned-clock-parents" to
Commit 68605101460e ("ARM: dts: exynos: Add support for audio over HDMI
for Odroid X/X2/U3") added assigned clocks under Clock Management Unit.
However the dtschema expects "clocks" property if "assigned-clocks" are
used. Add reference to input clock, the parent used in
"assigned-clock-parents"
Commit 52005dece527 ("ARM: dts: Add assigned clock parents to CMU node
for exynos3250") added assigned clocks under Clock Management Unit to
fix hangs when accessing ISP registers.
However the dtschema expects "clocks" property if "assigned-clocks" are
used. Add reference to input clock, the
On Thu, 3 Sep 2020, Valentin Schneider wrote:
>
> Hi Julia,
>
> On 03/09/20 15:09, Julia Lawall wrote:
> > Uses of SD_LOAD_BALANCE were removed in commit e669ac8ab952 (first
> > released in v5.8), with the comment:
> >
> > The SD_LOAD_BALANCE flag is set unconditionally for all domains in
> >
Emails to Beniamin Bia bounce with no such address so remove him from
maintainers. After this removal, many entries for Analog Devices Inc
IIO drivers look exactly the same so consolidate them.
Suggested-by: Andy Shevchenko
Suggested-by: Jonathan Cameron
Cc: Michael Hennerich
Cc: Jonathan
Hartmut Knaack was an active reviewer and contributor to the IIO
subsystem and drivers. However his last message on LKML is from
October 2015.
In thanks for Hartmut's effort, move him name to the Credits.
Suggested-by: Andy Shevchenko
Cc: Jonathan Cameron
Cc: linux-iio
Signed-off-by:
On 03.09.20 08:38, Michal Hocko wrote:
> On Wed 02-09-20 19:51:45, Vlastimil Babka wrote:
>> On 9/2/20 5:13 PM, Michal Hocko wrote:
>>> On Wed 02-09-20 16:55:05, Vlastimil Babka wrote:
On 9/2/20 4:26 PM, Pavel Tatashin wrote:
> On Wed, Sep 2, 2020 at 10:08 AM Michal Hocko wrote:
>>
> You're right. I wonder if there is really any need for the
> lm3554_gpio_uninit() function at all? It's basically the same as
> lm3554_gpio_init() except for the order of function calls. Probably
> we could just rename lm3554_gpio_init() to something like
> lm3554_gpio_set_default() and use
On Thu, Sep 3, 2020 at 2:20 PM David Hildenbrand wrote:
>
> On 03.09.20 08:38, Michal Hocko wrote:
> > On Wed 02-09-20 19:51:45, Vlastimil Babka wrote:
> >> On 9/2/20 5:13 PM, Michal Hocko wrote:
> >>> On Wed 02-09-20 16:55:05, Vlastimil Babka wrote:
> On 9/2/20 4:26 PM, Pavel Tatashin
The error path for lm3554_probe() contains a number of bugs, including:
* resource leaks
* jumping to error labels out of sequence
* not setting the return value appropriately
Fix it up and give the labels more memorable names.
This issue has existed since the code was originally contributed
On Tue, Sep 01, 2020 at 12:46:41PM +0200, Frederic Weisbecker wrote:
> Hi,
Hi Frederic,
Thanks for the summary! Looking forward to your comments...
> I'm currently working on making nohz_full/nohz_idle runtime toggable
> and some other people seem to be interested as well. So I've dumped
> a
On 9/3/20 1:19 AM, Ian Rogers wrote:
> On Tue, Sep 1, 2020 at 3:10 PM Kim Phillips wrote:
>> The nps1_die_to_dram event may need perf stat's --metric-no-group
>> switch if the number of available data fabric counters is less
>> than the number it uses (8).
>
> These are really excellent
On Thu, Sep 03, 2020 at 03:23:59PM -0300, Marcelo Tosatti wrote:
> On Tue, Sep 01, 2020 at 12:46:41PM +0200, Frederic Weisbecker wrote:
> > Hi,
>
> Hi Frederic,
>
> Thanks for the summary! Looking forward to your comments...
>
> > I'm currently working on making nohz_full/nohz_idle runtime
On 03.09.20 20:23, Pavel Tatashin wrote:
> On Thu, Sep 3, 2020 at 2:20 PM David Hildenbrand wrote:
>>
>> On 03.09.20 08:38, Michal Hocko wrote:
>>> On Wed 02-09-20 19:51:45, Vlastimil Babka wrote:
On 9/2/20 5:13 PM, Michal Hocko wrote:
> On Wed 02-09-20 16:55:05, Vlastimil Babka wrote:
The function lm3554_remove() checks for the return code for
lm3554_gpio_uninit() even though this is on the exit path and exits the
function, leaving the variable flash unfreed. Print a warning instead
and free flash unconditionally.
Signed-off-by: Alex Dewar
---
It is pretty easy to provide a retrigger callback for the ITS,
as it we already have the required support in terms of
irq_set_irqchip_state().
Note that this only works for device-generated LPIs, and not
the GICv4 doorbells, which should never have to be retriggered
anyway.
Signed-off-by: Marc
We don't really need to know that the LED pin reset successfully.
Signed-off-by: Alex Dewar
---
drivers/staging/media/atomisp/i2c/atomisp-lm3554.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/media/atomisp/i2c/atomisp-lm3554.c
From: Valentin Schneider
While digging around IRQCHIP_EOI_IF_HANDLED and irq/resend.c, it has come
to my attention that the IRQ resend situation seems a bit precarious for
the GIC(s).
When marking an IRQ with IRQS_PENDING, handle_fasteoi_irq() will bail out
and issue an irq_eoi(). Should the
From: Valentin Schneider
The GIC irqchips can now use a HW resend when a retrigger is invoked by
check_irq_resend(). However, should the HW resend fail, check_irq_resend()
will still attempt to trigger a SW resend, which is still a bad idea for
the GICs.
Prevent this from happening by setting
On Thu, Sep 3, 2020 at 11:03 AM Paolo Bonzini wrote:
>
> On 03/09/20 19:57, Jim Mattson wrote:
> > On Thu, Sep 3, 2020 at 7:12 AM Mohammed Gamal wrote:
> >> This patch exposes allow_smaller_maxphyaddr to the user as a module
> >> parameter.
> >>
> >> Since smaller physical address spaces are
Valentin recently pointed out that that relying on SW-based retrigger
with any of the GIC interrupt controllers is both inefficient and
slightly broken, as it messes the GIC's own state machine.
For this to work with the hierarchical irqchip model that the GIC
uses, we need check_irq_resend grow
On resending an interrupt, we only check the topmost irqchip for
a irq_retrigger callback. However, this callback could be implemented
at a lower level. Use irq_chip_retrigger_hierarchy() in this case.
Signed-off-by: Marc Zyngier
---
kernel/irq/resend.c | 15 +--
1 file changed, 13
A migrating transparent huge page has to already be unmapped. Otherwise,
the page could be modified while it is being copied to a new page and
data could be lost. The function __split_huge_pmd() checks for a PMD
migration entry before calling __split_huge_pmd_locked() leading one to
think that
On Tue, 1 Sep 2020 19:40:03 +0100
Jonathan Cameron wrote:
> On Sat, 29 Aug 2020 18:43:50 +0100
> Jonathan Cameron wrote:
>
> > On Mon, 10 Aug 2020 12:32:56 +0300
> > wrote:
> >
> > > From: Stefan Popa
> > >
> > > By default, if all three channels (x, y, z) are enabled, sample sets of
> >
On Thu, Sep 03, 2020 at 03:30:15PM -0300 Marcelo Tosatti wrote:
> On Thu, Sep 03, 2020 at 03:23:59PM -0300, Marcelo Tosatti wrote:
> > On Tue, Sep 01, 2020 at 12:46:41PM +0200, Frederic Weisbecker wrote:
> > > Hi,
> >
> > Hi Frederic,
> >
> > Thanks for the summary! Looking forward to your
Support regulator enable/disable via BD718(37/47/50) PMIC state machine.
The ROHM BD718(37/47/50) PMICs are mainly used for powering i.MX8 based
systems. On some setups the i.MX8 SoC uses a IO line to suspend the
system. These PMICs support this via PMIC internal HW state machine
which can be
The BD718(37/47/50) regulator enable states can be controlled either by SW
or by PMIC internal state machine.
On some systems mixture of SW and HW state machine controlled regulators is
needed.
Specifically, some SoCs signal SUSPEND state change to PMIC via
STBY_REQ line. Now there are setups
The BD718(37/47/50) regulator enable states can be controlled either by SW
or by PMIC internal state machine.
On some systems mixture of SW and HW state machine controlled regulators is
needed.
Specifically, some SoCs signal SUSPEND state change to PMIC via
STBY_REQ line. Now there are setups
The BD718x7 driver initialized common configs for all regulators.
Simplify initialization by moving the initialization of common configs
out of the loop.
Signed-off-by: Matti Vaittinen
---
drivers/regulator/bd718x7-regulator.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff
allyesconfig
powerpc allnoconfig
x86_64 randconfig-a004-20200903
x86_64 randconfig-a006-20200903
x86_64 randconfig-a003-20200903
x86_64 randconfig-a005-20200903
x86_64 randconfig-a001-20200903
x86_64
The BD718(37/47/50) regulator enable states can be controlled
either by SW or by PMIC internal state machine. The bd718x7
driver has not supported leaving the regulators under HW state
machine control (except for cases where this is required to
avoid boot-up problems due to critical regulators
On Thu, Sep 03, 2020 at 12:42:44PM +0530, Souptick Joarder wrote:
> We can use is_valid_gup_flags() inside ->
> get_user_pages_locked(),
> get_user_pages_unlocked(),
> pin_user_pages_locked() as well.
>
> Are you planning to add it in future patches ?
If you're looking for a new project, adding
Hi,
This patch-set extends TI PRUSS platform driver about CORECLK_MUX and
IEPCLK_MUX support. The corresponding dt-binding is updated accordingly.
This patch series depends on TI PRUSS platform driver patchset [1].
[1] https://patchwork.kernel.org/cover/11729645/
Grzegorz Jaszczyk (2):
Em Thu, Sep 03, 2020 at 10:47:39AM -0700, Ian Rogers escreveu:
> On Thu, Sep 3, 2020 at 8:25 AM Namhyung Kim wrote:
> > The new string should have enough space for the original string and
> > the back slashes IMHO.
> > Cc: John Garry
> > Cc: Kajol Jain
> > Cc: Ian Rogers
> > Signed-off-by:
ICSS/ICSSG modules have an IEP clock mux that allow selection of
internal IEP clock from 2 clock sources.
ICSSG module has a CORE clock mux that allows selection of internal CORE
clock from 2 clock sources.
Add binding information for these 2 clock muxes.
Signed-off-by: Grzegorz Jaszczyk
---
The IEPCLK_MUX is present on all SoCs whereas the CORECLK_MUX is present
only on AM65x SoCs and J721E. Add support for both these CLK muxes.
This allows the clock rates and clock parents for these to be controlled
through DT leveraging the clk infrastructure for configuring the default
parents
On Tue, 1 Sep 2020 19:46:00 +0100
Jonathan Cameron wrote:
> On Thu, 6 Aug 2020 18:44:51 +0100
> Jonathan Cameron wrote:
>
> > On Wed, 5 Aug 2020 07:57:44 +0200
> > Christian Eggers wrote:
> >
> > > Support for AMS AS73211 JENCOLOR(R) Digital XYZ Sensor.
> > >
> > > This driver has no
Hi Ian,
Please check that this is ok with you,
Thanks,
- Arnaldo
commit 0823f768b800cca2592fad3b5649766ae6bc4eba
Author: Arnaldo Carvalho de Melo
Date: Thu Sep 3 15:34:20 2020 -0300
perf parse-events: Use uintptr_t when casting numbers to pointers
To address these
Em Thu, Sep 03, 2020 at 09:01:13AM +0800, Jin Yao escreveu:
> There's a risk that outputting interval mode summaries by default
> breaks CSV consumers. It already broke pmu-tools/toplev.
>
> So now we turn off the summary by default but we create a new
> option '--summary' to enable the summary.
On Thu, Sep 3, 2020 at 11:02 AM Hao Luo wrote:
>
> The returned value of bpf_object__open_file() should be checked with
> IS_ERR() rather than NULL. This fix makes test_progs not crash when
> test_global_data.o is not present.
>
> Signed-off-by: Hao Luo
> ---
>
Em Wed, Sep 02, 2020 at 10:05:26PM +0800, YueHaibing escreveu:
> In case of error, the function perf_session__new() returns ERR_PTR()
> and never returns NULL. The NULL test in the return value check
> should be replaced with IS_ERR()
>
> Fixes: 13edc237200c ("perf bench: Add a multi-threaded
Em Thu, Sep 03, 2020 at 03:53:01PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Sep 02, 2020 at 10:05:26PM +0800, YueHaibing escreveu:
> > In case of error, the function perf_session__new() returns ERR_PTR()
> > and never returns NULL. The NULL test in the return value check
> > should be
Hi Greg,
I appreciate your comments and working to address them.
On 8/27/2020 11:12 PM, Greg KH wrote:
As for "matching names", why does that matter? Who sees both names at
the same time?
> >
> > endian issues?
> >
> > If not, why are these bit fields?
> This matches the definition on the
Em Thu, Sep 03, 2020 at 03:54:51PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Sep 03, 2020 at 03:53:01PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Wed, Sep 02, 2020 at 10:05:26PM +0800, YueHaibing escreveu:
> > > In case of error, the function perf_session__new() returns ERR_PTR()
Em Tue, Sep 01, 2020 at 04:58:53PM -0500, Kim Phillips escreveu:
> Event modifiers are not mentioned in the perf record or perf stat
> manpages. Add them to orient new users more effectively by pointing
> them to the perf list manpage for details.
Thanks, applied.
- Arnaldo
> Signed-off-by:
Em Thu, Aug 27, 2020 at 10:53:36AM +0200, Jesper Dangaard Brouer escreveu:
> The system for "Auto-detecting system features" located under
> tools/build/ are (currently) used by perf, libbpf and bpftool. It can
> contain stalled feature detection files, which are not cleaned up by
> libbpf and
Em Wed, Aug 26, 2020 at 11:30:17PM +0200, Jiri Olsa escreveu:
> When validating kcore modules the do_validate_kcore_modules
> function checks on every kernel module dso against modules
> record. The __map__is_kmodule check is used to get only
> kernel module dso objects through.
>
> Currently the
Hello,
syzbot found the following issue on:
HEAD commit:1127b219 Merge tag 'fallthrough-fixes-5.9-rc3' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=136d098e90
kernel config: https://syzkaller.appspot.com/x/.config?x=978db74cb30aa994
Add common properties appearing in DTSes (assigned-clock-parents,
assigned-clocks) to fix dtbs_check warnings like:
arch/arm64/boot/dts/exynos/exynos5433-tm2.dt.yaml: system-controller@105c:
'assigned-clock-parents', 'assigned-clocks' do not match any of the
regexes: 'pinctrl-[0-9]+'
The Exynos Multi Core Timer driver requires two clocks. This was never
documented in the binding. Add it to fix dtschema warnings like:
arch/arm64/boot/dts/exynos/exynos5433-tm2.dt.yaml: timer@101c:
'clock-names', 'clocks' do not match any of the regexes: 'pinctrl-[0-9]+'
Add common properties appearing in DTSes (controller-data,
wakeup-source) to partially fix dtbs_check warnings like:
arch/arm/boot/dts/exynos5250-snow.dt.yaml: embedded-controller@1e:
'keyboard-controller', 'wakeup-source' do not match any of the regexes:
'pinctrl-[0-9]+'
On Thu, Sep 03, 2020 at 08:08:51PM +0200, Krzysztof Kozlowski wrote:
> On Thu, 3 Sep 2020 at 19:49, Rob Herring wrote:
> > Just 1 other you picked up. See "ASoC: samsung-i2s: Use
> > unevaluatedProperties". Patches adding the missing properties (and
> > restoring 'additionalProperties' on these
Add common properties appearing in DTSes (opp-table) to fix dtbs_check
warnings like:
arch/arm/boot/dts/exynos4210-i9100.dt.yaml: gpu@1300:
'opp-table' does not match any of the regexes: 'pinctrl-[0-9]+'
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. Add properties
Add common properties appearing in DTSes (iommus, power-domains) to fix
dtbs_check warnings like:
arch/arm/boot/dts/exynos4210-i9100.dt.yaml: rotator@1281:
'iommus', 'power-domains' do not match any of the regexes: 'pinctrl-[0-9]+'
Signed-off-by: Krzysztof Kozlowski
---
Changes
Add common properties appearing in DTSes (opp-table) to fix dtbs_check
warnings like:
arch/arm64/boot/dts/exynos/exynos5433-tm2.dt.yaml: gpu@14ac:
'opp-table' does not match any of the regexes: 'pinctrl-[0-9]+'
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. Add
Device tree nodes should have hyphens instead of underscores. This is
also expected by the bindings.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. New patch
---
arch/arm/boot/dts/exynos4412.dtsi | 16
arch/arm/boot/dts/exynos5250.dtsi | 2 +-
2 files changed,
Device tree nodes should have hyphens instead of underscores. This is
also expected by the bindings.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. New patch
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Update the address of Maxime Ripard as one in @free-electrons.com does
not work.
Cc: Maxime Ripard
Signed-off-by: Krzysztof Kozlowski
Acked-by: Maxime Ripard
---
Changes since v1:
1. Add Ack
---
Documentation/devicetree/bindings/gpu/arm,mali-utgard.yaml | 2 +-
1 file changed, 1
Hi Arnaldo,
On 9/3/20 9:03 PM, Arnaldo Carvalho de Melo wrote:
Em Thu, Aug 27, 2020 at 10:53:36AM +0200, Jesper Dangaard Brouer escreveu:
The system for "Auto-detecting system features" located under
tools/build/ are (currently) used by perf, libbpf and bpftool. It can
contain stalled feature
On Thu, 03 Sep 2020 16:59:30 +0100
Marc Zyngier wrote:
> On 2020-09-03 15:35, Rob Herring wrote:
> > On Thu, Sep 3, 2020 at 3:19 AM Lorenzo Pieralisi
> > wrote:
> >>
> >> Ok I think I understand what the problem is.
> >>
> >> Can you give this patch a shot please ? I think we are
> >>
Add generic qcom interconnect bindings that are common across platforms. In
particular, these include QCOM_ICC_TAG_* macros that clients can use when
calling icc_set_tag().
Signed-off-by: Mike Tipton
Acked-by: Rob Herring
---
drivers/interconnect/qcom/icc-rpmh.h| 18 ++
Add "qcom,tcs-wait" property to set which TCS should wait for completion
when triggering.
Signed-off-by: Mike Tipton
Reviewed-by: Rob Herring
---
.../bindings/interconnect/qcom,bcm-voter.yaml | 20 +++
1 file changed, 20 insertions(+)
diff --git
Currently, all bcm-voters set tcs_cmd::wait=true for the last VCD
command in each TCS (AMC, WAKE, and SLEEP). However, some bcm-voters
don't need the completion and instead need to optimize for latency. For
instance, disabling wait-for-completion in the WAKE set can decrease
resume latency and
Change the default TCS wait behavior to only wait for completion in AMC
and WAKE. Waiting isn't necessary in the SLEEP TCS, since votes are only
being removed in this case. Resources can be safely disabled
asynchronously in parallel with the rest of the power collapse sequence.
This reduces the
These changes are mostly unrelated, but there are some dependencies
between them.
v4:
- Reorder series such that the fix comes first
- Collect reviewed/acked-by from v3
v3:
- Improve qcom,tcs-wait property description
- Stop using #define in property `default` doc
v2:
- New patch for generic
Currently, bcm-voter always assumes requests are made in KBps and that
BCM HW always wants them in Bps, so it always scales the requests by
1000. However, certain use cases and BCMs may use different units.
Thus, add support for BCM-specific scaling factors.
Signed-off-by: Mike Tipton
---
Small BW votes that translate to less than a single BCM unit are
currently truncated to zero. Ensure that non-zero BW requests always
result in at least a vote of 1 to BCM.
Fixes: 976daac4a1c5 ("interconnect: qcom: Consolidate interconnect RPMh
support")
Signed-off-by: Mike Tipton
---
Hi
There's a bug when you run strace from dax-based filesystem.
-- create real or emulated persistent memory device (/dev/pmem0)
mkfs.ext2 /dev/pmem0
-- mount it
mount -t ext2 -o dax /dev/pmem0 /mnt/test
-- copy the system to it (well, you can copy just a few files that are
needed for
Em Thu, Sep 03, 2020 at 09:20:35PM +0200, Daniel Borkmann escreveu:
> Hi Arnaldo,
>
> On 9/3/20 9:03 PM, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Aug 27, 2020 at 10:53:36AM +0200, Jesper Dangaard Brouer escreveu:
> > > The system for "Auto-detecting system features" located under
> > >
> +::
> +
> + /* KVM_EXIT_X86_RDMSR / KVM_EXIT_X86_WRMSR */
> + struct {
> + __u8 error; /* user -> kernel */
> + __u8 pad[3];
> + __u32 reason; /* kernel -> user */
> + __u32 index;
On 2020-08-19 11:20 a.m., John Garry wrote:
Hi all,
Here is v8 of the patchset.
In this version of the series, we keep the shared sbitmap for driver tags,
and introduce changes to fix up the tag budgeting across request queues.
We also have a change to count requests per-hctx for when an
No problem! Let me update and resend.
On Thu, Sep 3, 2020 at 11:50 AM Andrii Nakryiko
wrote:
>
> On Thu, Sep 3, 2020 at 11:02 AM Hao Luo wrote:
> >
> > The returned value of bpf_object__open_file() should be checked with
> > IS_ERR() rather than NULL. This fix makes test_progs not crash when
>
On Thu, Sep 03, 2020 at 11:55:16AM -0700, Iouri Tarassov wrote:
> Hi Greg,
>
> I appreciate your comments and working to address them.
>
> On 8/27/2020 11:12 PM, Greg KH wrote:
> > As for "matching names", why does that matter? Who sees both names at
> > the same time?
> >
> > > > > > endian
On Thu, Sep 03, 2020 at 07:01:13PM +0800, Xiongfeng Wang wrote:
> When I cat ipmi_msghandler parameter 'panic_op' by sysfs, it displays as
> follows. It's better to add a newline for easy reading.
>
> root@(none):/# cat /sys/module/ipmi_msghandler/parameters/panic_op
> noneroot@(none):/#
Thanks,
1 - 100 of 1286 matches
Mail list logo
