>From reading the #defines it seems like we should shout if we ever see
one of these error bits. Let's do so. This doesn't do anything
functional except print a yell in the log if the error bits are seen.
Signed-off-by: Douglas Anderson
---
Changes in v3:
- ("spi: spi-geni-qcom: Check for
If you added a bit of a delay (like a trace_printk) into the ISR for
the spi-geni-qcom driver, you would suddenly start seeing some errors
spit out. The problem was that, though the ISR itself held a lock,
other parts of the driver didn't always grab the lock.
One example race was this:
a)
The geni hardware has a FIFO that can hold up to 64 bytes (it has 16
entries that can hold 4 bytes each), at least on the two SoCs I tested
(sdm845 and sc7180). We configured our RX Watermark to 0, which
basically meant we got an interrupt as soon as the first 4 bytes
showed up in the FIFO.
The driver locks its locks in two places.
In the first usage of the lock the function doing the locking already
has a sleeping call and thus we know we can't be called from interrupt
context. That means we can use the "spin_lock_irq" variant of the
function.
In the second usage of the lock the
On Tue, Jun 16, 2020 at 12:40:32PM +0200, Peter Zijlstra wrote:
> On Tue, Jun 16, 2020 at 12:33:13PM +0200, Christoph Hellwig wrote:
> > sorry, s/ftrace/kprobes/. See my updated branch here:
> >
> > http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/module_alloc-cleanup
>
> Ah the
Hello,
syzbot found the following crash on:
HEAD commit:7ae77150 Merge tag 'powerpc-5.8-1' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15f8334610
kernel config: https://syzkaller.appspot.com/x/.config?x=d195fe572fb15312
> Subject: RE: [PATCH V5 1/9] pinctrl: imx: Support building SCU pinctrl driver
> as
> module
>
> > From: Anson Huang
> > Sent: Thursday, June 11, 2020 7:35 PM
> >
> > To support building i.MX SCU pinctrl driver as module, below things
> > need to be
> > changed:
> >
> > - Export SCU
I am also unable to reproduce the issue so far.
I wanted to point to a few things in case this helps:
- Commit 42fc541404f2 was bisected as the cause. This commit changes
walk_page_range_novma() to use mmap_assert_locked() instead of
lockdep_assert_held()
- mmap_assert_locked() checks
On 29/05/2020 09.43, Like Xu wrote:
> When the full-width writes capability is set, use the alternative MSR
> range to write larger sign counter values (up to GP counter width).
>
> Signed-off-by: Like Xu
> ---
> lib/x86/msr.h | 1 +
> x86/pmu.c | 125
On 06/16/2020 01:59 PM, kernel test robot wrote:
> Hi Anshuman,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on arm64/for-next/core]
> [also build test WARNING on soc/for-next v5.8-rc1 next-20200616]
> [cannot apply to arm/for-ne
On Fri 2020-06-12 14:53:58, Merlijn Wajer wrote:
> This event code represents the state of a removable cover of a device.
> Value 0 means that the cover is open or removed, value 1 means that the
> cover is closed.
>
> Reviewed-by: Sebastian Reichel Acked-by:
> Tony Lindgren
> Signed-off-by:
On Fri 2020-06-12 14:53:57, Merlijn Wajer wrote:
> this series adds the sw_machine_cover key, and changes the nokia n900 dts to
> expose the key via gpio-keys.
>
> before, this gpio was used as card detect gpio, causing the card not to show
> up
> if the phone was booted without cover, see this
Christoph Hellwig writes:
> On Tue, Jun 16, 2020 at 11:55:49AM +0200, Christoph Hellwig wrote:
>> Actually, what do you think of this one:
>
I see Peter has some concerns but if vmalloc_exec() used to work then
open-coding it with the right flags should do. I've also tested your
patch with
> > Having said that, I hit one stumbling block:
> > "Further, at this time there are no presentation integration. "
> >
> > If we upstream this driver as-is into some hyperv specific place, and
> > you decide to add presentation integration this is more than likely
> > going to mean you will want
Hi!
> Thanks for the discussion. I may not be able to immediately answer all of
> your questions, but I'll do my best .
>
Could you do something with your email settings? Because this is not how you
should use
email on lkml. "[EXTERNAL]" in the subject, top-posting, unwrapped lines...
Hi!
> > The driver creates the /dev/dxg device, which can be opened by user mode
> > application and handles their ioctls. The IOCTL interface to the driver
> > is defined in dxgkmthk.h (Dxgkrnl Graphics Port Driver ioctl
> > definitions). The interface matches the D3DKMT interface on Windows.
>
On Tue, Jun 16, 2020 at 12:42:30PM +0200, Christoph Hellwig wrote:
> On Tue, Jun 16, 2020 at 12:40:32PM +0200, Peter Zijlstra wrote:
> > On Tue, Jun 16, 2020 at 12:33:13PM +0200, Christoph Hellwig wrote:
> > > sorry, s/ftrace/kprobes/. See my updated branch here:
> > >
> > >
On 2020-06-16 11:52, Halil Pasic wrote:
On Mon, 15 Jun 2020 14:39:24 +0200
Pierre Morel wrote:
I find the subject (commit short) sub optimal. The 'arch' is already
accepting devices 'without IOMMU feature'. What you are introducing is
the ability to reject.
An architecture protecting the
On Tue 2020-05-26 21:24:39, Andrew F. Davis wrote:
> On 5/25/20 10:11 AM, Krzysztof Kozlowski wrote:
> > All battery related data could be important for user-space. For example
> > time-to-full could be shown to user on the screen or health could be
> > monitored for any issues. Instead of
Hi!
> Certain resources modeled as a generic power domain in linux kernel can be
> used to warm up the SoC (mx power domain on sdm845) if the temperature
> falls below certain threshold. These power domains can be considered as
> thermal warming devices. (opposite of thermal cooling devices).
Hi!
> +static ssize_t multi_intensity_show(struct device *dev,
> + struct device_attribute *intensity_attr,
> + char *buf)
> +{
> + struct led_classdev *led_cdev = dev_get_drvdata(dev);
> + struct led_classdev_mc *mcled_cdev =
On Mon, Jun 15, 2020 at 06:15:08PM +0200, Amelie Delaunay wrote:
> This patch adds a function that converts power operation mode string into
> power operation mode value.
>
> It is useful to configure power operation mode through device tree
> property, as power capabilities may be linked to
From: Leon Romanovsky
>From Yishai,
This series introduce KABIs to query existing UCONTEXT, PD and MR for their
properties.
By those KABIs a user space application which owns the command FD of the device
can retrieve and rebuild the above objects despite that it wasn't their creator.
As of
On Tue, Jun 16, 2020 at 12:55:40AM -0700, Andrei Vagin wrote:
> This is required to support time namespaces where a time namespace data
> page is different for each namespace.
Can you please give a bit more of an introduction to the changes here?
As-is, this doesn't give reviewers the necessary
On Thu, Jun 11, 2020 at 02:09:54PM +0200, Geert Uytterhoeven wrote:
> On Thu, Jun 11, 2020 at 10:50 AM Mark Brown wrote:
> > I'm not sure it's a particular concern, especially since you'll be
> > sending this stuff in the same series as a bindings update and an extra
> > patch in a series makes
Ok, i will modify it in v2 patch.
On 2020/6/16 14:50, Christian König wrote:
Probably better to remove the duplication of result and r here and
then use "goto err".
On 06/11/20 11:58, Qais Yousef wrote:
[...]
>
> nouclam nouclamp
> uclam uclamp uclamp.disable
> uclamp uclamp uclamp
>
Hi all,
In commit
912f25eca000 ("pinctrl: qcom: ipq6018 Add missing pins in qpic pin group")
Fixes tag
Fixes: ef1ea54 (pinctrl: qcom: Add ipq6018 pinctrl driver)
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or
On Mon, Jun 15, 2020 at 03:46:00PM -0700, Andy Lutomirski wrote:
> In some sense, #UD and #PF are fundamentally different. #PF wants to
> be able to schedule in the kernel. #UD wants to be as minimal as
> possible in the kernel but probably still wants to do the nmi_enter()
> dance in case it's
Quoting Tanmay Shah (2020-06-11 18:50:26)
> diff --git a/Documentation/devicetree/bindings/display/msm/dp-sc7180.yaml
> b/Documentation/devicetree/bindings/display/msm/dp-sc7180.yaml
> new file mode 100644
> index ..5fdb9153df00
> --- /dev/null
> +++
Reviewed-by: Aurelien Aptel
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
Hi Greg,
On 6/15/20 3:03 PM, Greg KH wrote:
> On Mon, Jun 15, 2020 at 12:55:29PM +0300, Stanimir Varbanov wrote:
>> Hi Greg,
>>
>> On 6/14/20 9:37 AM, Greg KH wrote:
>>> On Sun, Jun 14, 2020 at 01:39:18AM +0300, Stanimir Varbanov wrote:
if (slot == -1) {
-
> On Jun 16, 2020, at 18:05, Aaron Ma wrote:
>
> After commit "e1000e: disable s0ix entry and exit flows for ME systems",
> some ThinkPads always failed to disable ulp by ME.
> commit "e1000e: Warn if disabling ULP failed" break out of init phy:
>
> error log:
> [ 42.364753] e1000e
> Fix memory leak in amdgpu_debugfs_gpr_read not freeing data when
> pm_runtime_get_sync failed.
* Would you like to improve the exception handling any more for this software
module?
* How do you think about calling the function “pm_runtime_put_noidle”?
Regards,
Markus
On Tue, Jun 16, 2020 at 12:52:00PM +0200, Christoph Hellwig wrote:
> I think something like this should solve the issue:
>
> --
> diff --git a/arch/x86/include/asm/module.h b/arch/x86/include/asm/module.h
> index e988bac0a4a1c3..716e4de44a8e78 100644
> --- a/arch/x86/include/asm/module.h
> +++
On Tue, Jun 16, 2020 at 12:55:41AM -0700, Andrei Vagin wrote:
> The VVAR page layout depends on whether a task belongs to the root or
> non-root time namespace.
Please be more explicit as to what you mean by `layout` here, as that seems to
be an overloaded term. For example, the comment above
16.06.2020 00:47, Emil Velikov пишет:
> Hi all,
>
> Perhaps a silly question:
>
> On Mon, 15 Jun 2020 at 08:28, Dmitry Osipenko wrote:
>>
>> Combining horizontal and vertical reflections gives us 180 degrees of
>> rotation.
>>
>> Signed-off-by: Dmitry Osipenko
>> ---
>>
On 6/16/20 7:23 PM, Kai-Heng Feng wrote:
>
>
>> On Jun 16, 2020, at 18:05, Aaron Ma wrote:
>>
>> After commit "e1000e: disable s0ix entry and exit flows for ME systems",
>> some ThinkPads always failed to disable ulp by ME.
>> commit "e1000e: Warn if disabling ULP failed" break out of init
On Tue, 2 Jun 2020 at 19:31, Corey Gao wrote:
>
> If __mmc_start_req(host, mrq) fails with error, the mrq->cmd->mrq will
> be NULL. This will cause kernel panic in the following
> mmc_wait_for_req_done(host, mrq). Add error check to cancle unnecessary
> mmc_wait_for_req_done(host, mrq) if
From: Gene Chen
Add devicetree binding document support Mediatek MT6360 PMIC
Signed-off-by: Gene Chen
---
Documentation/devicetree/bindings/mfd/mt6360.txt | 53
1 file changed, 53 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/mt6360.txt
diff
There are two problems with kernel messages in fatal mode that were found
during testing of guests and userspace programs.
The first is that no kernel message is output when the split lock detector
is triggered with a userspace program. As a result the userspace process
dies from receiving
This was sent in error.
Sorry,
P.
On 6/16/20 7:27 AM, Prarit Bhargava wrote:
> There are two problems with kernel messages in fatal mode that were found
> during testing of guests and userspace programs.
>
> The first is that no kernel message is output when the split lock detector
> is
From: Patrice Chotard
In case of -EPROBE_DEFER, stm32_qspi_release() was called
in any case which unregistered driver from pm_runtime framework
even if it has not been registered yet to it. This leads to:
stm32-qspi 58003000.spi: can't setup spi0.0, status -13
spi_master spi0: spi_device
Hi,
On 6/15/20 10:49 PM, Federico Ricchiuto wrote:
The Mediacom FlexBook edge13 uses the SIPODEV SP1064 touchpad, which does
not supply descriptors, so it has to be added to the override list.
Signed-off-by: Federico Ricchiuto
It looks like you copied and pasted part of the commit message
Hi,
On 6/16/2020 11:43 AM, John Stultz wrote:
Allows qcom-pdc driver to be loaded as a permenent module
typo: permanent
Also, due to the fact that IRQCHIP_DECLARE becomes a no-op when
building as a module, we have to add the platform driver hooks
explicitly.
Thanks to Saravana for his help
In mobile, a co-processor is used when using USB audio
to improve power consumption.
hooking is required for sync-up when operating
the co-processor. So register call-back function.
The main operation of the call-back function is as follows:
- Initialize the co-processor by transmitting data
On Tue, Jun 16, 2020 at 11:13 AM Stefano Garzarella wrote:
> On Mon, Jun 15, 2020 at 11:00:25AM -0600, Jens Axboe wrote:
> > On 6/15/20 7:33 AM, Stefano Garzarella wrote:
> > > On Mon, Jun 15, 2020 at 11:04:06AM +0200, Jann Horn wrote:
> > >> +Kees, Christian, Sargun, Aleksa, kernel-hardening for
On Tue, 9 Jun 2020 at 10:38, Pradeep P V K wrote:
>
> Interconnect bandwidth scaling support is now added as a
> part of OPP. So, make sure interconnect driver is ready
> before handling interconnect scaling.
>
> Signed-off-by: Pradeep P V K
> Reviewed-by: Sibi Sankar
Applied for next, thanks!
On Fri, 5 Jun 2020 at 05:04, Sowjanya Komatineni wrote:
>
> This patch adds comments about NVQUIRKS HAS_PADCALIB and NEEDS_PAD_CONTROL.
>
> Signed-off-by: Sowjanya Komatineni
Applied for next, thanks!
Kind regards
Uffe
> ---
> drivers/mmc/host/sdhci-tegra.c | 9 +
> 1 file changed,
On Mon, 8 Jun 2020 at 10:45, Neil Armstrong wrote:
>
> The actual max_segs computation leads to failure while using the broadcom
> sdio brcmfmac/bcmsdh driver, since the driver tries to make usage of scatter
> gather.
>
> But with the dram-access-quirk we use a 1,5K SRAM bounce buffer, and the
>
There are two problems with kernel messages in fatal mode that were found
during testing of guests and userspace programs.
The first is that no kernel message is output when the split lock detector
is triggered with a userspace program. As a result the userspace process
dies from receiving
On Tue, 9 Jun 2020 at 10:38, Pradeep P V K wrote:
>
> Add interconnect bandwidth scaling supported strings for qcom-sdhci
> controller.
>
> Signed-off-by: Pradeep P V K
> Acked-by: Rob Herring
> Reviewed-by: Bjorn Andersson
Applied for next, thanks!
Kind regards
Uffe
> ---
>
On Tue, 9 Jun 2020 at 12:20, Lars Povlsen wrote:
>
> This adds the eMMC driver for the Sparx5 SoC. It is based upon the
> designware IP, but requires some extra initialization and quirks.
I need a signed-off-by tag to apply this, and I would also appreciate
an ack from Adrian.
Kind regards
Uffe
On Thu, 11 Jun 2020 at 15:28, Ludovic Barre wrote:
>
> This patch adds datactrl_mask_sdio for sdmmc revisions.
> sdmmc revisions used same bit of previous ST variant.
>
> Signed-off-by: Ludovic Barre
Applied for next, thanks!
Kind regards
Uffe
> ---
> drivers/mmc/host/mmci.c | 2 ++
> 1
On Mon, 8 Jun 2020 at 18:22, Chuhong Yuan wrote:
>
> These functions do not check the return value of devm_clk_register():
> - sdhci_arasan_register_sdcardclk()
> - sdhci_arasan_register_sampleclk()
>
> Therefore, add the missed checks to fix them.
>
> Fixes: c390f2110adf1 ("mmc:
On Mon 2020-06-15 23:47:26, jim.cro...@gmail.com wrote:
> On Mon, Jun 15, 2020 at 9:14 AM Petr Mladek wrote:
> >
> > On Sat 2020-06-13 09:57:27, Jim Cromie wrote:
> > > combine flags & mask into a struct, and replace those 2 parameters in
> > > 3 functions: ddebug_change, ddebug_parse_flags,
On Tue, 16 Jun 2020 10:53:48 +0800, Shengjiu Wang wrote:
> For mono channel, SSI will switch to Normal mode.
>
> In Normal mode and Network mode, the Word Length Control bits
> control the word length divider in clock generator, which is
> different with I2S Master mode (the word length is fixed
16.06.2020 01:26, Emil Velikov пишет:
> Hi Dmitry,
>
> On Mon, 15 Jun 2020 at 08:28, Dmitry Osipenko wrote:
>>
>> Hello!
>>
>> This series adds 180° display plane rotation support to the NVIDIA Tegra
>> DRM driver which is needed for devices that have display panel physically
>> mounted
On Sat 2020-06-13 09:57:31, Jim Cromie wrote:
> 1. Add a user-flag [u] which works like the [pfmlt] flags, but has no
> effect on callsite behavior; it allows incremental marking of
> arbitrary sets of callsites.
>
> 2. Add [PFMLTU] flags, which negate their counterparts; P===!p etc.
> And in
From: Colin Ian King
Currently there is no null check for a failed memory allocation
on the dsb object and without this a null pointer dereference
error can occur. Fix this by adding a null check.
Note: added a drm_err message in keeping with the error message style
in the function.
On 6/3/20 2:54 PM, Benjamin Gaignard wrote:
> This series add low power timer as boadcast clockevent device.
> Low power timer could runs even when CPUs are in idle mode and
> could wakeup them.
>
> Lee has acked the MFD part.
> Clocksource driver still need to be reviewed by maintainers.
> Add
On Sat 2020-06-13 09:57:32, Jim Cromie wrote:
> Extend flags modifications to allow [PFMLTU] negating flags.
> This allows control-queries like:
>
> #> Q () { echo file inode.c $* > control } # to type less
> #> Q -P # same as +p
> #> Q +U # same as -u
> #> Q u-P# same as u+p
From: Colin Ian King
Currently the expression (nand_ctrl | BAM_MODE_EN) is always true no
matter the value of nand_ctrl because the incorrect masking operator
is being used. Fix this by using bit-wise & instead of |.
Addresses-Coverity: ("Wrong operator used")
Fixes: dd0c1fc8de12 ("mtd:
Especially with memory hotplug, we can have offline sections (with a
garbage memmap) and overlapping zones. We have to make sure to only
touch initialized memmaps (online sections managed by the buddy) and that
the zone matches, to not move pages between zones.
To test if this can actually
Commit e900a918b098 ("mm: shuffle initial free memory to improve
memory-side-cache utilization") promised "autodetection of a
memory-side-cache (to be added in a follow-on patch)" over a year ago.
The original series included patches [1], however, they were dropped
during review [2] to be
Fix typo: "TRIGER" --> "TRIGGER"
Signed-off-by: Flavio Suligoi
---
drivers/media/pci/dt3155/dt3155.c | 2 +-
drivers/media/pci/dt3155/dt3155.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/pci/dt3155/dt3155.c
b/drivers/media/pci/dt3155/dt3155.c
index
Commit e900a918b098 ("mm: shuffle initial free memory to improve
memory-side-cache utilization") introduced shuffling of free pages
during system boot and whenever we online memory blocks.
However, whenever we online memory blocks, all pages that will be
exposed to the buddy end up getting freed
Patch #1 is a fix for overlapping zones and offline sections. Patch #2
stops shuffling the complete zone when onlining a memory block. Patch #3
removes dynamic reconfiguration which is currently dead code (and it's
unclear if this will be needed in the near future).
David Hildenbrand (3):
On 2020/5/29 17:48, Paolo Bonzini wrote:
On 27/05/20 08:24, Tianjia Zhang wrote:
Hi Huacai,
These two patches(6/7 and 7/7) should be merged into the tree of the
mips architecture separately. At present, there seems to be no good way
to merge the whole architecture patchs.
For this
On 16/06/2020 12:54, Dan Carpenter wrote:
> On Tue, Jun 16, 2020 at 12:42:21PM +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> Currently there is no null check for a failed memory allocation
>> on the dsb object and without this a null pointer dereference
>> error can occur. Fix this by
On Tue, Jun 16, 2020 at 12:42:21PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Currently there is no null check for a failed memory allocation
> on the dsb object and without this a null pointer dereference
> error can occur. Fix this by adding a null check.
>
> Note: added a drm_err
Hi Andy,
>-Original Message-
>From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
>ow...@vger.kernel.org] On Behalf Of Andy Shevchenko
>Sent: 16 June 2020 10:31
>To: Shiju Jose
>Cc: linux-a...@vger.kernel.org; linux-...@vger.kernel.org; linux-
>ker...@vger.kernel.org;
On Sat 2020-06-13 09:57:33, Jim Cromie wrote:
> Current code expects "keyword" "arg" as 2 space separated words.
> Change to also accept "keyword:arg" and "keyword=arg" forms as well,
> and drop !(nwords%2) requirement.
>
> Then in rest of function, use new keyword,arg variables instead of
>
On Tue, 16 Jun 2020 12:52:50 +0200
Pierre Morel wrote:
> >> int virtio_finalize_features(struct virtio_device *dev)
> >> {
> >>int ret = dev->config->finalize_features(dev);
> >> @@ -179,6 +184,10 @@ int virtio_finalize_features(struct virtio_device
> >> *dev)
> >>if
On Tue, Jun 16, 2020 at 12:52:24PM +0200, Pavel Machek wrote:
> On Tue 2020-05-26 21:24:39, Andrew F. Davis wrote:
> > On 5/25/20 10:11 AM, Krzysztof Kozlowski wrote:
> > > All battery related data could be important for user-space. For example
> > > time-to-full could be shown to user on the
Στις 2020-06-16 10:45, Zong Li έγραψε:
Add System RAM to /proc/iomem, various tools expect it such as kdump.
It is also needed for page_is_ram API which checks the specified
address
whether registered as System RAM in iomem_resource list.
Signed-off-by: Zong Li
---
arch/riscv/mm/init.c | 22
Quoting Maulik Shah (2020-06-01 04:38:25)
> On 5/31/2020 12:56 AM, Stephen Boyd wrote:
> > Quoting Maulik Shah (2020-05-29 02:20:32)
> >> On 5/27/2020 3:45 PM, Stephen Boyd wrote:
> >>> Quoting Maulik Shah (2020-05-23 10:11:13)
> @@ -118,6 +120,7 @@ static void qcom_pdc_gic_unmask(struct
On Tue, Jun 16, 2020 at 10:31:54AM +0200, Linus Walleij wrote:
> On Mon, Jun 8, 2020 at 2:51 PM Drew Fustini wrote:
>
> > This patch causes pcs_parse_pinconf() to return -ENOTSUPP when no
> > pinctrl_map is added. The current behavior is to return 0 when
> > !PCS_HAS_PINCONF or !nconfs. Thus
16.06.2020 01:26, Emil Velikov пишет:
...
> Although I see that this series, alike Derek's, has a couple of issues:
> - only a single panel driver is updated
I'll separate this series into two patchsets.
One will add orientation support to the panel drivers and I'll include
the Derek's
Define a default set of CPU OPPs for the HiFive Unleashed with the
FU540-C000 SoC. This allows CPUFreq to be enabled for this board.
The FU540-C000 SoC PVT corners haven't been characterized separately
from the HiFive Unleashed board. Thus the OPPs are added to the board
DT file, rather than the
The patch series adds the support for dynamic CPU frequency switching
for FU540-C000 SoC on the HiFive Unleashed board. All the patches are
based on Paul Walmsley's work.
This series is based on Linux v5.7 and tested on HiFive unleashed board.
Yash Shah (3):
riscv: defconfig, Kconfig: enable
Enable CPUFreq and CPUIdle for RISC-V systems to be configured with
Kconfig, and compile the kernel code to support it by default. This
will be used to support dynamic CPU frequency switching for the HiFive
Unleashed board, along with any future RISC-V boards that support
CPU power management.
Declare that each hart defined in the FU540 DT data is clocked by the
COREPLL. This is in preparation for enabling CPUFreq for the
FU540-C000 SoC on the HiFive Unleashed board.
Signed-off-by: Yash Shah
---
arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 5 +
1 file changed, 5 insertions(+)
On Tue, Jun 16, 2020 at 12:19 PM Maciej Żenczykowski wrote:
>
> > Nit, your From: line of your email does not match your signed-off-by:
> > line :(
That's hard to notice while being on the sending end, thanks for
pointing that out!
I'll look into this.
> This is *probably* a matter of
Hi Jason,
Somehow this got stuck somewhere in the mail queues, only popped up just
now ...
On Thu, Jun 11, 2020 at 11:15:15AM -0300, Jason Gunthorpe wrote:
> On Thu, Jun 11, 2020 at 10:34:30AM +0200, Daniel Vetter wrote:
> > > I still have my doubts about allowing fence waiting from within
On 15/06/20 21:07, Bird, Tim wrote:
>> Note: making the plan line required differs from TAP13 and TAP14. I
>> think it's the right choice, but we should be clear.
As an aside, where is TAP14?
> With regards to making it optional or not, I don't have a strong
> preference. The extra info seems
On Sun, Jun 14, 2020 at 04:46:55PM +0300, Laurent Pinchart wrote:
> Hi Aditya,
>
> (CC'ing Rafael)
>
> Thank you for the patch.
>
> On Sat, Jun 13, 2020 at 09:40:05PM -0500, Aditya Pakki wrote:
> > On calling pm_runtime_get_sync() the reference count of the device
> > is incremented. In case of
On Mon, Jun 15, 2020 at 09:58:09AM +0200, Wolfram Sang wrote:
> I want to remove the above API this cycle, and just a few patches have
> not made it into 5.8-rc1. They have been reviewed and most had been
> promised to get into linux-next, but well, things happen. So, I hope it
> is okay for
On Mon, Jun 15, 2020 at 09:11:51PM +0900, Masanari Iida wrote:
> This patch fix a spelling typo in test-drm_mm.c
>
> Signed-off-by: Masanari Iida
Applied, thanks for your patch.
-Daniel
> ---
> drivers/gpu/drm/selftests/test-drm_mm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
On Tue, Jun 16, 2020 at 9:49 AM Kees Cook wrote:
> One of the most common pain points with seccomp filters has been dealing
> with the overhead of processing the filters, especially for "always allow"
> or "always reject" cases. While BPF is extremely fast[1], it will always
> have overhead
> > +KBUILD_CFLAGS+= -ftrivial-auto-var-init=zero
> > -enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang
> > +endif
>
> Gotta love the name...
This is basically the reason why we've been hesitating to add it to
the kernel from the very beginning.
> Anyway, if this
Hi Nicolas,
On Mon, Jun 15, 2020 at 06:26:19PM +0200, Nicolas Saenz Julienne wrote:
> On Thu, 2020-06-11 at 11:23 +0200, Maxime Ripard wrote:
> > Now that we have a driver for the DVP, let's add its DT node.
> >
> > Signed-off-by: Maxime Ripard
> > ---
>
> I can take this patch, but I guess
This patch set adds initial support for MStar/Sigmastar's
Armv7 based SoCs. There is just enough here to get to a shell
with an initramfs but support for a lot of the hardware is
in progress and will follow.
MStar also shipped chips with MIPS cores and ARM9 etc which
are incompatible so I've
Add prefix for 70mai Co., Ltd
Signed-off-by: Daniel Palmer
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b/Documentation/devicetree/bindings/vendor-prefixes.yaml
index
Add prefix for MStar Semiconductor, Inc.
Signed-off-by: Daniel Palmer
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b/Documentation/devicetree/bindings/vendor-prefixes.yaml
Add prefix for Xiamen Xingchen Technology Co., Ltd
Signed-off-by: Daniel Palmer
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
Adds initial dtsi for the base MStar/Sigmastar Armv7 SoCs.
These SoCs have very similar memory maps and this will avoid
duplicating nodes across multiple dtsis.
Signed-off-by: Daniel Palmer
---
MAINTAINERS | 1 +
arch/arm/boot/dts/mstar-v7.dtsi | 83
Adds initial support for the 70mai midrive d08 dash camera.
Signed-off-by: Daniel Palmer
---
arch/arm/boot/dts/Makefile| 3 ++-
.../boot/dts/mercury5-ssc8336n-midrived08.dts | 25 +++
2 files changed, 27 insertions(+), 1 deletion(-)
create mode 100644
This adds a YAML description of the l3bridge node needed by the
platform code for the MStar/SigmaStar Armv7 SoCs.
Signed-off-by: Daniel Palmer
---
.../bindings/misc/mstar,l3bridge.yaml | 44 +++
1 file changed, 44 insertions(+)
create mode 100644
This adds two family level dtsis for the infinity and infinity3
and then adds a chip level dtsi each for a chip in those families.
infinity3.dtsi includes infinity.dtsi as these SoCs share most of
their memory map and we would have a lot of duplication otherwise.
Signed-off-by: Daniel Palmer
1 - 100 of 1769 matches
Mail list logo
