Rename goto labels in device_init it will be easier to maintain.
Reviewed-by: Alyssa Rosenzweig
Signed-off-by: Clément Péron
---
drivers/gpu/drm/panfrost/panfrost_device.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/panfrost/panfr
Introduce a proper panfrost_devfreq to deal with devfreq variables.
Reviewed-by: Steven Price
Reviewed-by: Alyssa Rosenzweig
Signed-off-by: Clément Péron
---
drivers/gpu/drm/panfrost/panfrost_devfreq.c | 76 -
drivers/gpu/drm/panfrost/panfrost_devfreq.h | 20 +-
drivers
Don't include not required headers and sort them.
Reviewed-by: Steven Price
Reviewed-by: Alyssa Rosenzweig
Signed-off-by: Clément Péron
---
drivers/gpu/drm/panfrost/panfrost_devfreq.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/panfrost/panfrost_
Convert busy_count to a simple int protected by spinlock.
Reviewed-by: Steven Price
Reviewed-by: Alyssa Rosenzweig
Signed-off-by: Clément Péron
---
drivers/gpu/drm/panfrost/panfrost_devfreq.c | 43 +++--
drivers/gpu/drm/panfrost/panfrost_devfreq.h | 9 -
2 files changed, 4
This declaration can be avoided so change it.
Reviewed-by: Steven Price
Reviewed-by: Alyssa Rosenzweig
Signed-off-by: Clément Péron
---
drivers/gpu/drm/panfrost/panfrost_devfreq.c | 38 ++---
1 file changed, 18 insertions(+), 20 deletions(-)
diff --git a/drivers/gpu/drm/panfro
Later we will introduce devfreq probing regulator if they
are present. As regulator should be probe only one time we
need to get this logic in the device_init().
panfrost_device is already taking care of devfreq_resume()
and devfreq_suspend(), so it's not totally illogic to move
the devfreq_init()
On Thu, Jul 09, 2020 at 04:06:12AM +, Chu Lin wrote:
> Issue:
> When PEC is enabled, binding adm1272 to the adm1275 would
> fail due to PEC error. See below:
> adm1275: probe of failed with error -74
>
> Diagnosis:
> Per the datasheet of adm1272, adm1278, adm1293 and amd1294,
> PMON_CONFI
On 7/9/20 8:00 AM, Christoph Hellwig wrote:
> On Thu, Jul 09, 2020 at 07:58:04AM -0600, Jens Axboe wrote:
>>> We don't actually need any new field at all. By the time the write
>>> returned ki_pos contains the offset after the write, and the res
>>> argument to ->ki_complete contains the amount of
This adds fan_target entries to the corsair-cpro driver.
Reading the attribute from the device does not seem possible, so
it returns the last set value. (same as pwm)
send_usb_cmd now has one more argument, which is needed for the
fan_target command.
Signed-off-by: Marius Zachmann
---
Change f
Hi Qian Cai,
On Thu, Jul 09, 2020 at 09:40:40AM -0400, Qian Cai wrote:
> > > > Can we change the batch firstly, then sync the global counter, finally
> > > > change the overcommit policy?
> > >
> > > These reorderings are really head scratching :)
> > >
> > > I've thought about this before when
Hi,
On Thu, 9 Jul 2020 at 16:03, Clément Péron wrote:
>
> Hi,
>
> This serie cleans and adds regulator support to Panfrost devfreq.
> This is mostly based on comment for the freshly introduced lima
> devfreq.
>
> We need to add regulator support because on Allwinner the GPU OPP
> table defines bo
On 7/9/2020 3:07 PM, Rajendra Nayak wrote:
When using the geni-serial as console, its important to be
able to hit the lowest possible power state in suspend,
even with no_console_suspend.
The only thing that prevents it today on platforms like the sc7180
is the interconnect BW votes, which we c
On Thu, 9 Jul 2020 07:16:31 +
"Liu, Yi L" wrote:
> Hi Alex,
>
> After more thinking, looks like adding a r-b tree is still not enough to
> solve the potential problem for free a range of PASID in one ioctl. If
> caller gives [0, MAX_UNIT] in the free request, kernel anyhow should
> loop all
On Wed 08 Jul 19:22 PDT 2020, Steev Klimaszewski wrote:
>
> On 7/2/20 3:46 PM, Sibi Sankar wrote:
> > Add OPP tables required to scale DDR/L3 per freq-domain on SDM845 SoCs.
> >
> > Signed-off-by: Sibi Sankar
> > ---
>
>
> Hi Sibi,
>
>
> Bjorn asked me to give this patch a whirl, and I have
On Tue, 7 Jul 2020, Pekka Enberg wrote:
> On Fri, Jul 3, 2020 at 12:38 PM xunlei wrote:
> >
> > On 2020/7/2 PM 7:59, Pekka Enberg wrote:
> > > On Thu, Jul 2, 2020 at 11:32 AM Xunlei Pang
> > > wrote:
> > >> The node list_lock in count_partial() spend long time iterating
> > >> in case of large
On Thu, Jul 09, 2020 at 12:59:06PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 09, 2020 at 01:48:18PM +0300, Dan Carpenter wrote:
> > The __per_cpu_offset[] array has "nr_cpu_ids" elements so change the >
> > >= to prevent a read one element beyond the end of the array.
> >
> > Fixes: 0504bc41a62c
Check for errors instead of silently not using icc if the msm driver
probes before the interconnect driver.
Allow ENODATA for ocmem path, as it is optional and this error
is returned when "gfx-mem" path is provided but not "ocmem".
Remove the WARN_ON in msm_gpu_cleanup because INIT_LIST_HEAD won'
Hi,
On Thu, Jul 9, 2020 at 12:30 AM Akash Asthana wrote:
>
> Hi Doug,
>
> >
> > @@ -670,7 +674,13 @@ static int __maybe_unused
> > spi_geni_runtime_resume(struct device *dev)
> > if (ret)
> > return ret;
> >
> > - return geni_se_resources_on(&mas->se);
> > + ret = gen
On Thu, Jul 09, 2020 at 01:49:00PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-07-09 12:59:06 [+0200], Peter Zijlstra wrote:
> > On Thu, Jul 09, 2020 at 01:48:18PM +0300, Dan Carpenter wrote:
> > > The __per_cpu_offset[] array has "nr_cpu_ids" elements so change the >
> > > >= to prevent a re
On 03. 07. 20 15:54, Raviteja Narayanam wrote:
> This patch series clears the HOLD bit at right time.
>
> Raviteja Narayanam (2):
> Revert "i2c: cadence: Fix the hold bit setting"
> i2c: cadence: Clear HOLD bit at correct time in Rx path
>
> drivers/i2c/busses/i2c-cadence.c | 28 +
Kalle Valo wrote:
> Viktor Jägersküpper writes:
>
>> Kalle Valo writes:
>>> Roman Mamedov writes:
>>>
On Sat, 4 Apr 2020 12:18:38 +0800
Qiujun Huang wrote:
> In ath9k_hif_usb_rx_cb interface number is assumed to be 0.
> usb_ifnum_to_if(urb->dev, 0)
> But it isn't alw
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0bddd227f3dc55975e2b8dfa7fc6f959b062a2c7
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 3 weeks ago
config: microblaze-randconfig-s032-20200709
On Thu 2020-07-09 22:07:58, Sergey Senozhatsky wrote:
> On (20/07/09 14:25), Petr Mladek wrote:
> > On Thu 2020-07-09 13:23:07, John Ogness wrote:
> > > On 2020-07-09, Petr Mladek wrote:
> > > > I though more about it. IMHO, it will be better to modify
> > > > prb_first_seq() to do the same cycle
In the patch ("spi: spi-geni-qcom: Avoid clock setting if not needed")
we avoid a whole pile of clock code. As part of that, we should have
restored the clock at runtime resume. Do that.
It turns out that, at least with today's configurations, this doesn't
actually matter. That's because none o
On 2020-07-09 19:59, Bjorn Andersson wrote:
On Wed 08 Jul 19:22 PDT 2020, Steev Klimaszewski wrote:
On 7/2/20 3:46 PM, Sibi Sankar wrote:
> Add OPP tables required to scale DDR/L3 per freq-domain on SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
> ---
Hi Sibi,
Bjorn asked me to give this pat
On Thu, Jul 09, 2020 at 05:07:12PM +0900, Masami Hiramatsu wrote:
> Fix a wrong "variable not found" warning when the probe point is
> not found in the debuginfo.
> Since the debuginfo__find_probes() can return 0 even if it does not
> find given probe point in the debuginfo, fill_empty_trace_arg()
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index 1e95a336862c..671176d39569 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -379,6 +379,11 @@ static int find_alternative_probe_point(struct debuginfo
> *dinfo,
>
On Thu, Jul 09, 2020 at 02:22:08PM +0200, Pali Rohár wrote:
> On Thursday 09 July 2020 12:35:09 Lorenzo Pieralisi wrote:
> > On Thu, Jul 02, 2020 at 10:30:36AM +0200, Pali Rohár wrote:
> > > When there is no PCIe card connected and advk_pcie_rd_conf() or
> > > advk_pcie_wr_conf() is called for PCI
On Thu 02 Jul 13:46 PDT 2020, Sibi Sankar wrote:
> Add OPP tables required to scale DDR/L3 per freq-domain on SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
Tested-by: Bjorn Andersson
and applied.
Thanks,
Bjorn
> ---
>
> v2:
> * Drop interconnect tags
> * Add all possible cpu opps from supp
On Thu, 9 Jul 2020 12:51:58 +0200
Pierre Morel wrote:
> >> +int arch_validate_virtio_features(struct virtio_device *dev)
> >> +{
> >> + if (!is_prot_virt_guest())
> >> + return 0;
> >> +
> >> + if (!virtio_has_feature(dev, VIRTIO_F_VERSION_1)) {
> >> + dev_warn(&dev->dev, "dev
- return (NULL);
+ return NULL;
This is the ACPICA coding standard, and it does not affect anything.
Bob
-Original Message-
From: Xu Wang
Sent: Thursday, July 09, 2020 1:08 AM
To: Moore, Robert ; Kaneda, Erik
; Wysocki, Rafael J ;
l...@kernel.org; vu...@isc
Hi,
On Thu, Jul 9, 2020 at 1:55 AM Rajendra Nayak wrote:
>
>
> On 7/9/2020 5:09 AM, Douglas Anderson wrote:
> > In the patch ("spi: spi-geni-qcom: Avoid clock setting if not needed")
> > we avoid a whole pile of clock code. As part of that, we should have
> > restored the clock at runtime resume
On 2020-07-09 16:47, Halil Pasic wrote:
On Thu, 9 Jul 2020 12:51:58 +0200
Pierre Morel wrote:
+int arch_validate_virtio_features(struct virtio_device *dev)
+{
+ if (!is_prot_virt_guest())
+ return 0;
+
+ if (!virtio_has_feature(dev, VIRTIO_F_VERSION_1)) {
+
As per recent changes to the spi-qcom-qspi, now when we set the clock
we'll call into the interconnect framework and also call the OPP API.
Those are expensive operations. Let's avoid calling them if possible.
This has a big impact on getting transfer rates back up to where they
were (or maybe sli
Not to be confused with the similar series I posed for the _other_
Qualcomm SPI controller (spi-geni-qcom) [1], this one avoids the
overhead on the Quad SPI controller.
It's based atop the current Qualcomm tree including Rajendra's ("spi:
spi-qcom-qspi: Use OPP API to set clk/perf state"). As d
In commit cff80645d6d3 ("spi: spi-qcom-qspi: Add interconnect support")
the spi_geni_runtime_suspend() and spi_geni_runtime_resume()
became a bit slower. Measuring on my hardware I see numbers in the
hundreds of microseconds now.
Let's use autosuspend to help avoid some of the overhead. Now if
w
This is a successor of "[PATCH v2 0/3] KVM: nSVM: fix #TF from CR3 switch
when entering guest" and "[PATCH] KVM: x86: drop erroneous mmu_check_root()
from fast_pgd_switch()".
The snowball is growing fast! It all started with an intention to fix
the particular 'tripple fault' issue (now fixed by PA
Now as kvm_init_shadow_npt_mmu() is separated from kvm_init_shadow_mmu()
we always know the MMU context we need to use so there is no need to
dereference vcpu->arch.mmu pointer.
Suggested-by: Paolo Bonzini
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/mmu/mmu.c | 15 +++
1 file c
kvm_mmu_new_pgd() refers to arch.mmu and at this point it still references
arch.guest_mmu while arch.root_mmu is expected.
Note, the change is effectively a nop: when !npt_enabled,
nested_svm_uninit_mmu_context() does nothing (as we don't do
nested_svm_init_mmu_context()) and with npt_enabled we d
The mmu_check_root() check in fast_pgd_switch() seems to be
superfluous: when GPA is outside of the visible range
cached_root_available() will fail for non-direct roots
(as we can't have a matching one on the list) and we don't
seem to care for direct ones.
Also, raising #TF immediately when a non
As a preparatory change for moving kvm_mmu_new_pgd() from
nested_prepare_vmcb_save() to nested_svm_init_mmu_context() split
kvm_init_shadow_npt_mmu() from kvm_init_shadow_mmu(). This also makes
the code look more like nVMX (kvm_init_shadow_ept_mmu()).
No functional change intended.
Signed-off-by:
Make nSVM code resemble nVMX where nested_vmx_load_cr3() is used on
both guest->host and host->guest transitions. Also, we can now
eliminate unconditional kvm_mmu_reset_context() and speed things up.
Note, nVMX has two different paths: load_vmcs12_host_state() and
nested_vmx_restore_host_state() a
Undesired triple fault gets injected to L1 guest on SVM when L2 is
launched with certain CR3 values. #TF is raised by mmu_check_root()
check in fast_pgd_switch() and the root cause is that when
kvm_set_cr3() is called from nested_prepare_vmcb_save() with NPT
enabled CR3 points to a nGPA so we can't
As a preparatory change for implementing nested specifig PGD switch for
nSVM (following nVMX' nested_vmx_load_cr3()) instead of relying on
kvm_set_cr3() introduce nested_svm_load_cr3().
The only intended functional change for now is that errors from
kvm_set_cr3() are propagated.
Signed-off-by: Vi
WARN_ON_ONCE(svm->nested.nested_run_pending) in nested_svm_vmexit()
will fire if nested_run_pending remains '1' but it doesn't really
need to, we are already failing and not going to run nested guest.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/svm/nested.c | 2 ++
1 file changed, 2 inserti
Some operations in enter_svm_guest_mode() may fail, e.g. currently
we suppress kvm_set_cr3() return value. Prepare the code to proparate
errors.
No functional change intended.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/svm/nested.c | 26 --
arch/x86/kvm/svm/svm.c
As a part of UV1 platform removal, delete the efi=old_map option,
which should no longer be needed.
Signed-off-by: Steve Wahl
---
arch/x86/platform/uv/bios_uv.c | 14 --
1 file changed, 14 deletions(-)
--- linux.orig/arch/x86/platform/uv/bios_uv.c 2020-07-07 10:49:50.117510557
arch/x86/platform/uv/uv_tlb.c: remove UV1 support
Include removing unused timeout_base_ns as reported by l...@intel.com.
Signed-off-by: Steve Wahl
Reported-by: kernel test robot
---
arch/x86/platform/uv/tlb_uv.c | 237 +-
1 file changed, 31 insertions(+)
On Thursday 09 July 2020 01:53 AM, Dmitry Osipenko wrote:
External email: Use caution opening links or attachments
The MAX77620_GPIO_NR enum value represents the total number of GPIOs,
let's use it instead of a raw value in order to improve the code's
readability a tad.
Reviewed-by: Andy Sh
arch/x86/include/asm/uv/uv.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux.orig/arch/x86/include/asm/uv/uv.h 2020-07-07 10:49:50.189510470
-0500
+++ linux/arch/x86/include/asm/uv/uv.h 2020-
As a part of UV1 platform removal, don't try to recognize the platform
through DMI to set the EFI_UV1_MEMMAP bit.
Signed-off-by: Steve Wahl
---
arch/x86/platform/efi/quirks.c | 23 ---
1 file changed, 23 deletions(-)
--- linux.orig/arch/x86/platform/efi/quirks.c 2020-07-
arch/x86/include/asm/uv/uv_bau.h: Remove UV1 support
arch/x86/platform/uv/tlb_uv.c: follow structure name change in uv_bau.h
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_bau.h | 118 ++-
arch/x86/platform/uv/tlb_uv.c|4 -
2 files changed,
arch/x86/include/asm/uv/uv_mmrs.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_mmrs.h | 712 --
1 file changed, 712 deletions(-)
--- linux.orig/arch/x86/include/asm/uv/uv_mmrs.h2020-07-07
10:49:50.301510334 -0500
+++
arch/x86/include/asm/uv/uv_hub.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_hub.h | 34 +++---
1 file changed, 3 insertions(+), 31 deletions(-)
--- linux.orig/arch/x86/include/asm/uv/uv_hub.h 2020-07-07 10:49:50.229510422
-0500
++
In removing UV1 support, efi_have_uv1_memmap is no longer used.
Signed-off-by: Steve Wahl
---
arch/x86/kernel/kexec-bzimage64.c |9 -
arch/x86/platform/efi/efi.c | 14 +++---
arch/x86/platform/efi/efi_64.c| 38 +++---
arch/x86/pla
With UV1 removed, EFI_UV1_MEMMAP is not used. Remove code used by it
in arch/x86/platform/uv/bios_uv.c and turn off code in
arch/x86/platform/efi/efi.c that referenced this code.
Signed-off-by: Steve Wahl
---
arch/x86/platform/efi/efi.c|2
arch/x86/platform/uv/bios_uv.c | 159
arch/x86/platform/uv/uv_time.c: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/platform/uv/uv_time.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
--- linux.orig/arch/x86/platform/uv/uv_time.c 2020-07-07 10:49:50.565510013
-0500
+++ linux/arch/x86/platf
arch/x86/include/asm/uv/bios.h: remove UV1 reference
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/bios.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux.orig/arch/x86/include/asm/uv/bios.h 2020-07-07 10:49:50.153510515
-0500
+++ linux/arch/x86/include/asm/uv/bios.
With UV1 support removed, EFI_UV1_MEMMAP is no longer used.
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/efi.h | 20 ++--
1 file changed, 2 insertions(+), 18 deletions(-)
--- linux.orig/arch/x86/include/asm/efi.h 2020-07-07 10:49:49.753511000
-0500
+++ linux/arch/
arch/x86/kernel/apic/x2apic_uv_x.c: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/kernel/apic/x2apic_uv_x.c | 122 +++--
1 file changed, 26 insertions(+), 96 deletions(-)
--- linux.orig/arch/x86/kernel/apic/x2apic_uv_x.c 2020-07-07
10:49:50.39
This series of patches removes support for the UV1 platform and the
efi=old_map kernel command line option.
The documentation for efi=old_map in
Documentation/admin-guide/kernel-parameters.txt was recently touched
and differs between linux-next and the mainline tree. I will send a
separate patc
On Thursday 09 July 2020 01:53 AM, Dmitry Osipenko wrote:
External email: Use caution opening links or attachments
The requested interrupt is never released by the driver. Fix this by
using the resource-managed variant of request_threaded_irq().
Fixes: ab3dd9cc24d4 ("gpio: max77620: Fix int
On Tuesday, July 7, 2020 3:59:32 AM CEST Dan Williams wrote:
> The runtime firmware activation capability of Intel NVDIMM devices
> requires memory transactions to be disabled for 100s of microseconds.
> This timeout is large enough to cause in-flight DMA to fail and other
> application detectable
On Thursday 09 July 2020 01:53 AM, Dmitry Osipenko wrote:
External email: Use caution opening links or attachments
The gpiochip_add_data() takes care of setting the of_node to the parent's
device of_node, hence there is no need to do it manually in the driver's
code. This patch corrects the
On Mon, Jul 06, 2020 at 06:59:32PM -0700, Dan Williams wrote:
> The runtime firmware activation capability of Intel NVDIMM devices
> requires memory transactions to be disabled for 100s of microseconds.
> This timeout is large enough to cause in-flight DMA to fail and other
> application detectable
On Wed 08 Jul 14:16 PDT 2020, Douglas Anderson wrote:
> As per Qualcomm, there is a PDC hardware issue (with the specific IP
> rev that exists on sc7180) that causes the PDC not to work properly
> when configured to handle dual edges.
>
> Let's work around this by emulating only ever letting our
On Thursday 09 July 2020 01:53 AM, Dmitry Osipenko wrote:
External email: Use caution opening links or attachments
The platform_get_irq() returns a positive interrupt number on success and
negative error code on failure (zero shouldn't ever happen in practice, it
would produce a noisy warnin
On Thursday 09 July 2020 01:53 AM, Dmitry Osipenko wrote:
External email: Use caution opening links or attachments
This change addresses one of the GPIO-core TODOs for the MAX77620 driver
which requires modern drivers to use the irqchip template. Instead of
using the GPIO's irqchip-helpers f
On Thursday 09 July 2020 01:53 AM, Dmitry Osipenko wrote:
External email: Use caution opening links or attachments
I noticed on Nexus 7 that after rebooting from downstream kernel to
upstream, the GPIO interrupt is triggering non-stop despite interrupts
being disabled for all of GPIOs. This
On Thu, 9 Jul 2020 16:51:04 +0200
Pierre Morel wrote:
>
>
> On 2020-07-09 16:47, Halil Pasic wrote:
> > On Thu, 9 Jul 2020 12:51:58 +0200
> > Pierre Morel wrote:
> >
> +int arch_validate_virtio_features(struct virtio_device *dev)
> +{
> +if (!is_prot_virt_guest())
> >>>
On Thursday 09 July 2020 15:47:01 Lorenzo Pieralisi wrote:
> On Thu, Jul 09, 2020 at 02:22:08PM +0200, Pali Rohár wrote:
> > On Thursday 09 July 2020 12:35:09 Lorenzo Pieralisi wrote:
> > > On Thu, Jul 02, 2020 at 10:30:36AM +0200, Pali Rohár wrote:
> > > > When there is no PCIe card connected and
Current minimum required version of binutils is 2.23,
which supports PSHUFB, PCLMULQDQ, PEXTRD, AESKEYGENASSIST,
AESIMC, AESENC, AESENCLAST, AESDEC, AESDECLAST and MOVQ
instruction mnemonics.
Substitute macros from include/asm/inst.h with a proper
instruction mnemonics in various assmbly files fro
Hi Kirill & Matthew,
In the func call chain, from split_huge_page() to lru_add_page_tail(),
Seems tail pages are added to lru list at line 963, but in this scenario
the head page has no lru bit and isn't set the bit later. Why we do this?
or do I miss sth?
Many Thanks
Alex
938 void lru_add_page
On Thu, Jul 9, 2020 at 7:35 AM Jonathan Marek wrote:
>
> Check for errors instead of silently not using icc if the msm driver
> probes before the interconnect driver.
>
> Allow ENODATA for ocmem path, as it is optional and this error
> is returned when "gfx-mem" path is provided but not "ocmem".
>
- On Jul 9, 2020, at 8:49 AM, Christian Brauner
christian.brau...@ubuntu.com wrote:
> On Wed, Jul 08, 2020 at 01:34:48PM -0400, Mathieu Desnoyers wrote:
>> - On Jul 8, 2020, at 12:22 PM, Christian Brauner
>> christian.brau...@ubuntu.com wrote:
>> [...]
>> > I've been following this a litt
Just like the NFS and CIFS root code this better lives with the
driver it is tightly integrated with.
Signed-off-by: Christoph Hellwig
---
drivers/md/Makefile | 3 +++
init/do_mounts_md.c => drivers/md/md-autodetect.c | 15 +--
include/linux/raid/detect
The only caller of the bstat function becomes cleaner and simpler when
open coding the function.
Signed-off-by: Christoph Hellwig
---
init/do_mounts.h| 10 --
init/do_mounts_md.c | 8
2 files changed, 4 insertions(+), 14 deletions(-)
diff --git a/init/do_mounts.h b/init/do
If initrd support is not enable just print the warning directly instead
of hiding the fact that we just failed behind two stub functions.
Signed-off-by: Christoph Hellwig
---
init/initramfs.c | 15 ---
1 file changed, 4 insertions(+), 11 deletions(-)
diff --git a/init/initramfs.c b/
There is no good reason to mess with file descriptors from in-kernel
code, switch the initramfs unpacking to struct file based write
instead. As we don't have nice helper for chmod or chown on a struct
file or struct path use the pathname based ones instead there. This
causes additional (cached)
The classic initial ramdisk has been replaced by the much more
flexible and efficient initramfs a long time. Warn about it being
removed soon.
Signed-off-by: Christoph Hellwig
---
init/do_mounts_initrd.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/init/do_mounts_initrd.c b/init/do_mou
Just use d_genocide instead of iterating through the root directory with
cumbersome userspace-like APIs. This also ensures we actually remove files
that are not direct children of the root entry, which the old code failed
to do.
Fixes: df52092f3c97 ("fastboot: remove duplicate unpack_to_rootfs()"
Signed-off-by: Christoph Hellwig
---
init/do_mounts_initrd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/do_mounts_initrd.c b/init/do_mounts_initrd.c
index e4f88e9e1c0839..57ad5b2da8f5f5 100644
--- a/init/do_mounts_initrd.c
+++ b/init/do_mounts_initrd.c
@@ -56,7 +56,7
Don't rely on the implicit set_fs(KERNEL_DS) for ksys_open to work, but
instead open a struct file for /dev/console and then install it as FD
0/1/2 manually.
Signed-off-by: Christoph Hellwig
---
fs/file.c| 7 +--
include/linux/syscalls.h | 1 -
init/main.c | 16
kmem_cache_destroy can correctly handle null pointer parameter,
so there is no need to check if the parameter is null before
calling kmem_cache_destroy.
Signed-off-by: Xianting Tian
---
drivers/scsi/virtio_scsi.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/s
BLKFLSBUF used to be overloaded for the ramdisk driver to free the whole
ramdisk, which was completely different behavior compared to all other
drivers. But this magic overload got removed in commit ff26956875c2
("brd: remove support for BLKFLSBUF"), so this call is entirely
pointless now.
Signed
Move the loop over the possible arrays into the caller to remove a level
of indentation for the whole function.
Signed-off-by: Christoph Hellwig
---
drivers/md/md-autodetect.c | 203 ++---
1 file changed, 101 insertions(+), 102 deletions(-)
diff --git a/drivers/m
Just open code it in the two callers.
Signed-off-by: Christoph Hellwig
---
fs/open.c| 11 ---
include/linux/syscalls.h | 11 ---
2 files changed, 8 insertions(+), 14 deletions(-)
diff --git a/fs/open.c b/fs/open.c
index 6348173532e663..4375a5a8e726ea 100644
--- a
Instead of using a spcial RAID_AUTORUN ioctl that only exists for
non-modular builds and is only called from the early init code, just
call the actual function directly.
Signed-off-by: Christoph Hellwig
---
drivers/md/md-autodetect.c | 10 ++
drivers/md/md.c| 14 +
On Thu, Jul 09, 2020 at 04:14:13PM +0200, Marius Zachmann wrote:
> This adds fan_target entries to the corsair-cpro driver.
> Reading the attribute from the device does not seem possible, so
> it returns the last set value. (same as pwm)
>
> send_usb_cmd now has one more argument, which is needed
Remove the special handling for multiple floppies in the initrd code.
No one should be using floppies for booting these days. (famous last
words..)
Signed-off-by: Christoph Hellwig
---
arch/arm/kernel/atags_parse.c | 2 -
arch/sh/kernel/setup.c| 2 -
arch/sparc/kernel/setup_32.c | 2
There is no good reason to mess with file descriptors from in-kernel
code, switch the initrd loading to struct file based read and writes
instead.
Signed-off-by: Christoph Hellwig
---
fs/read_write.c | 2 +-
include/linux/syscalls.h | 1 -
init/do_mounts_rd.c | 82 +++
devfs is long gone, and autoscan works just fine without this these days.
Signed-off-by: Christoph Hellwig
---
drivers/md/md-autodetect.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/md/md-autodetect.c b/drivers/md/md-autodetect.c
index 0eb746211ed53c..6bc9b734eee6ff 10
md_setup_drive knows it works with md devices, so it is rather pointless
to open a file descriptor and issue ioctls. Just call directly into the
relevant low-level md routines after getting a handle to the device using
blkdev_get_by_dev instead.
Signed-off-by: Christoph Hellwig
---
drivers/md/m
mdp_major can just move to drivers/md/md.h.
Signed-off-by: Christoph Hellwig
---
drivers/md/md.h | 1 +
include/linux/raid/md_u.h | 13 -
2 files changed, 1 insertion(+), 13 deletions(-)
delete mode 100644 include/linux/raid/md_u.h
diff --git a/drivers/md/md.h b/drivers/
Hi all,
this series starts to move the early init code away from requiring
KERNEL_DS to be implicitly set during early startup. It does so by
first removing legacy unused cruft, and the switches away the code
from struct file based APIs to our more usual in-kernel APIs.
There is no really good t
Convert the textual documentation of Device Tree bindings for the
Ingenic JZ47xx SoCs ADC controller to YAML.
The `interrupts` property is now explicitly listed and marked as
required. While missing from the previous textual documentation, this
property has been used with all the boards which prob
Provide an of_xlate callback in order to retrieve the correct channel
specifier index from the IIO channels array.
Signed-off-by: Artur Rojek
Tested-by: Paul Cercueil
---
Changes:
v2-v8: no change
drivers/iio/adc/ingenic-adc.c | 16
1 file changed, 16 insertions(+)
diff -
As of the patch ("ath10k: Keep track of which interrupts fired, don't
poll them") we now have no users of this hardware parameter. Remove
it.
Suggested-by: Brian Norris
Signed-off-by: Douglas Anderson
---
Changes in v2:
- Patch ("ath10k: Get rid of "per_ce_irq" hw param") new for v2.
drivers
Introduce support for touchscreen channels found in JZ47xx SoCs.
Signed-off-by: Artur Rojek
Tested-by: Paul Cercueil
---
Changes:
v2-v7: no change
v8: add XN/YN and XD/YD channels
include/dt-bindings/iio/adc/ingenic,adc.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/
Hi,
On Wed, Jul 8, 2020 at 4:40 PM Brian Norris wrote:
>
> On Wed, Jul 8, 2020 at 4:14 PM Doug Anderson wrote:
> > On Wed, Jul 8, 2020 at 4:03 PM Brian Norris
> > wrote:
> > > If I'm reading correctly, you're removing the only remaining use of
> > > 'per_ce_irq'. Should we kill the field entir
501 - 600 of 1335 matches
Mail list logo
