From: Konrad Rzeszutek Wilk
The git commit a945928ea2709bc0e8e8165d33aed855a0110279
('xen: Do not enable spinlocks before jump_label_init() has executed')
was added to deal with the jump machinery. Earlier the code
that turned on the jump label was only called by Xen specific
function
From: Konrad Rzeszutek Wilk
When Xen migrates an HVM guest, by default its shared_info can
only hold up to 32 CPUs. As such the hypercall
VCPUOP_register_vcpu_info was introduced which allowed us to
setup per-page areas for VCPUs. This means we can boot PVHVM
guest with more than 32 VCPUs
From: Konrad Rzeszutek Wilk
When we migrate an HVM guest, by default our shared_info can
only hold up to 32 CPUs. As such the hypercall
VCPUOP_register_vcpu_info was introduced which allowed us to
setup per-page areas for VCPUs. This means we can boot PVHVM
guest with more than 32 VCPUs. During
These two patches (one for Linux, one for Xen) allow PVHVM guests to use
the per-cpu VCPU mechanism after migration. Currently when an PVHVM guest
migrates all the per-cpu information is lost and we fallback on the
shared_info structure. This is regardless if the HVM guest has 2 or 128 CPUs.
Since
From: Konrad Rzeszutek Wilk
By default when CONFIG_XEN and CONFIG_XEN_PVHVM kernels are
run, they will enable the PV extensions (drivers, interrupts, timers,
etc) - which is the best option for the majority of
use cases.
However, in some cases (kexec not fully working, benchmarking)
we want to
From: Konrad Rzeszutek Wilk
We had been printing it only if the device was built with
debug enabled. But this information is useful in the field
to troubleshoot.
Reviewed-by: David Vrabel
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciback/xenbus.c |2 +-
1 files changed, 1
From: Konrad Rzeszutek Wilk
As commit 0a9fd0152929db372ff61b0d6c280fdd34ae8bdb
'xen/pciback: Document the entry points for 'pcistub_put_pci_dev''
explained there are four entry points in this function.
Two of them are when the user fiddles in the SysFS to
unbind a device whic
From: Konrad Rzeszutek Wilk
A little cleanup. No functional difference.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciback/pci_stub.c | 20 +++-
1 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/drivers/xen/xen-pciback/pci_stub.c
b/drivers/xen
From: Konrad Rzeszutek Wilk
Cleanup the function a bit - also include the id of the
domain that is using the device.
Reviewed-by: David Vrabel
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciback/pci_stub.c | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
diff
From: Konrad Rzeszutek Wilk
Which hadn't been done with the initial commit.
Signed-off-by: Konrad Rzeszutek Wilk
---
v2: Dropped the parameters and one that is unlikeable.
---
Documentation/ABI/testing/sysfs-driver-pciback | 25
1 files changed, 25 insertions(
Please see this set of patches which are fixes to Xen pciback
for 3.17. They are also located at:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
devel/pciback-3.17.v4
These patches do not include the PCI bus reset/slot code as we are still
discussing that.
Konrad Rzeszutek Wilk
From: Konrad Rzeszutek Wilk
We had been printing it only if the device was built with
debug enabled. But this information is usuable in the field
to troubleshoot.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciback/xenbus.c |2 +-
1 files changed, 1 insertions(+), 1 deletions
From: Konrad Rzeszutek Wilk
A little cleanup. No functional difference.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciback/pci_stub.c | 20 +++-
1 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/drivers/xen/xen-pciback/pci_stub.c
b/drivers/xen
From: Konrad Rzeszutek Wilk
The life-cycle of a PCI device in Xen pciback is complex
and is constrained by the PCI generic locking mechanism.
It starts with the device being binded to us - for which
we do a device function reset (and done via SysFS
so the PCI lock is held)
If the device is
From: Konrad Rzeszutek Wilk
Which hadn't been done with the initial commit.
Signed-off-by: Konrad Rzeszutek Wilk
---
Documentation/ABI/testing/sysfs-driver-pciback | 84
1 files changed, 84 insertions(+), 0 deletions(-)
create mode 100644 Documentation/ABI/te
From: Konrad Rzeszutek Wilk
Cleanup the function a bit - also include the id of the
domain that is using the device.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciback/pci_stub.c | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/xen/xen
From: Konrad Rzeszutek Wilk
As commit 0a9fd0152929db372ff61b0d6c280fdd34ae8bdb
'xen/pciback: Document the entry points for 'pcistub_put_pci_dev''
explained there are four entry points in this function.
Two of them are when the user fiddles in the SysFS to
unbind a device whic
From: Konrad Rzeszutek Wilk
Moving the bulk of the code its own function to aid
in making the 'xen/pciback: implement PCI reset slot
or bus with 'do_flr' SysFS attribute' easier.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciba
++
drivers/xen/xen-pciback/pci_stub.c | 163 +++-
drivers/xen/xen-pciback/xenbus.c |2 +-
3 files changed, 224 insertions(+), 36 deletions(-)
Konrad Rzeszutek Wilk (7):
xen-pciback: Document the various parameters and attributes in SysFS
From: Konrad Rzeszutek Wilk
By default when CONFIG_XEN and CONFIG_XEN_PVHVM kernels are
run, they will enable the PV extensions (drivers, interrupts, timers,
etc) - which is perfect.
However, in some cases (kexec not fully wokring, benchmarking)
we want to disable Xen PV extensions. As such
On 2/25/2013 12:00 PM, Roger Pau Monné wrote:
On 25/02/13 17:49, Konrad Rzeszutek Wilk wrote:
On Fri, Feb 15, 2013 at 08:12:52PM +0100, Roger Pau Monné wrote:
On 15/02/13 19:56, Konrad Rzeszutek Wilk wrote:
Should be backported to 3.8 stable.
Lets do one thing at a time.
The patch I have
seems to me that some people
have lost their common sense
Konrad
On 3/11/13, Josh Triplett wrote:
> On Sun, Mar 10, 2013 at 04:14:27PM +0100, Konrad Vrba wrote:
>> Dear list,
>> I have noticed that CONFIG_EXPERT=n makes the following options in the
>> kernel
/initiator/index: 0
For full details of the IBFT structure please take a look at:
ftp://ftp.software.ibm.com/systems/support/system_x_pdf/ibm_iscsi_boot_firmware_table_v1.02.pdf
Signed-off-by: Konrad Rzeszutek <[EMAIL PROTECTED]>
Cc: Mike Christie <[EMAIL PROTECTED]>
Cc: Peter J
> That being said, I don't think there's any reason to expect the table to
> show up on anything but i386 and x86_64, and maybe ia64.
I've posted a new patch (http://lkml.org/lkml/2008/1/30/531) that includes
that dependency in the Kconfig (i386, x86_64, ia64)
--
To unsubscribe from this list
> > + if (hdr->id == id_nic) {
> > + pci_dev = pci_get_bus_and_slot((nic->pci_bdf & 0xff00) >>
> > 8, + (nic->pci_bdf & 0xff));
> pci_get_bus_and_slot fails in the presence of PCI domains, which are
> getting to be fairly common even
/initiator/index: 0
For full details of the IBFT structure please take a look at:
ftp://ftp.software.ibm.com/systems/support/system_x_pdf/ibm_iscsi_boot_firmware_table_v1.02.pdf
Signed-off-by: Konrad Rzeszutek <[EMAIL PROTECTED]>
Cc: Mike Christie <[EMAIL PROTECTED]>
Cc: Peter Jones
Hello,
I have following error while compiling new stable kernel 3.10:
CC kernel/fork.o
CC kernel/exec_domain.o
CC kernel/panic.o
CC kernel/printk.o
CC kernel/cpu.o
CC kernel/exit.o
CC kernel/itimer.o
make[1]: *** No rule to make target `kernel/timec
On 7/11/13, Borislav Petkov wrote:
> On Thu, Jul 11, 2013 at 12:28:20PM +0200, Konrad Vrba wrote:
>> Hello,
>> I have following error while compiling new stable kernel 3.10:
>>
>> CC kernel/fork.o
>> CC kernel/exec_domain.o
>> CC kern
On 7/11/13, Geert Uytterhoeven wrote:
> On Thu, Jul 11, 2013 at 12:49 PM, Konrad Vrba
> wrote:
>> On 7/11/13, Borislav Petkov wrote:
>>> On Thu, Jul 11, 2013 at 12:28:20PM +0200, Konrad Vrba wrote:
>>>> Hello,
>>>> I have following error while com
On 7/11/13, Borislav Petkov wrote:
> On Thu, Jul 11, 2013 at 02:56:46PM +0200, Konrad Vrba wrote:
>> .config is attached
>
> Your config builds just fine here.
>
> And you must be having some garbage lying around because 3.10 doesn't
> have timeconst.pl:
>
>
On 7/11/13, Borislav Petkov wrote:
> On Thu, Jul 11, 2013 at 03:47:36PM +0200, Konrad Vrba wrote:
>> You are right.
>> I have now tried compiling on another machine, and that works fine.
>> But I am using the same config and same kernel tar.xz
>> that does not make sen
On 9/6/2013 11:09 AM, Stefano Stabellini wrote:
On Fri, 6 Sep 2013, Boris Ostrovsky wrote:
m2p_remove_override() calls get_balloon_scratch_page() in
MULTI_update_va_mapping() even though it already has pointer to this page from
the earlier call (in scratch_page). This second call doesn't have a
On 6/11/2013 5:00 AM, George Dunlap wrote:
On 06/11/2013 08:29 AM, Jan Beulich wrote:
On 10.06.13 at 23:06, Konrad Rzeszutek Wilk
wrote:
There are two tool-stack that can instruct the Xen PCI frontend
and backend to change states: 'xm' (Python code with a daemon),
and 'xl
On 6/11/2013 3:42 AM, Jan Beulich wrote:
On 10.06.13 at 18:43, Konrad Rzeszutek Wilk wrote:
On Mon, Jun 10, 2013 at 04:52:35PM +0100, Jan Beulich wrote:
On 07.06.13 at 22:11, Konrad Rzeszutek Wilk wrote:
On Tue, Jun 04, 2013 at 03:57:06PM -0400, Konrad Rzeszutek Wilk wrote:
+ /* N.B
On 6/11/2013 11:36 AM, George Dunlap wrote:
On 06/10/2013 10:06 PM, Konrad Rzeszutek Wilk wrote:
There are two tool-stack that can instruct the Xen PCI frontend
and backend to change states: 'xm' (Python code with a daemon),
and 'xl' (C library - does not keep state cha
On 6/11/2013 12:17 PM, George Dunlap wrote:
On 06/11/2013 05:08 PM, konrad wilk wrote:
On 6/11/2013 11:36 AM, George Dunlap wrote:
On 06/10/2013 10:06 PM, Konrad Rzeszutek Wilk wrote:
There are two tool-stack that can instruct the Xen PCI frontend
and backend to change states: 'xm
On 6/27/2013 9:28 AM, Stefano Stabellini wrote:
xen_hvm_post_suspend, xen_pre_suspend, xen_post_suspend are only used if
CONFIG_HIBERNATE_CALLBACKS is defined, resulting in:
drivers/xen/manage.c:46:13: warning: ‘xen_hvm_post_suspend’ defined but not
used [-Wunused-function]
drivers/xen/manage.
> David Vrabel (1): xen/events: avoid race with raising an event in
unmask_evtchn()
Unless I am looking in the wrong place, this patch is still the same one
that breaks PV on HVM and Xen ARM guests, see:
http://marc.info/?l=xen-devel&m=136377731913034
David is aware of the issue and I think is
On 8/21/2013 9:48 AM, David Vrabel wrote:
All,
179ef71c (mm: save soft-dirty bits on swapped pages) introduces a new
PTE bit on x86 _PTE_SWP_SOFT_DIRTY which has the same value as _PTE_PSE
and _PTE_PAT.
With a Xen PV guest, the use of the _PTE_PAT will result in the page
having unexpected cach
On 7/25/2013 10:51 PM, Zheng, Lv wrote:
From: Konrad Rzeszutek Wilk [mailto:konrad.w...@oracle.com]
Sent: Thursday, July 25, 2013 8:04 PM
CC-ing some of the tboot maintainers.
As what I've said, it's up to the others to determine if the patch is OK.
I just need to make my concerns
- ying...@kernel.org wrote:
> Prepare to put page table on local nodes.
>
> Move calling of init_mem_mapping to early_initmem_init.
>
> Rework alloc_low_pages to alloc page table in following order:
> BRK, local node, low range
>
> Still only load_cr3 one time, otherwise we would bre
impossible to compile a kernel with
CONFIG_FW_LOADER=n
CONFIG_DEBUG_KERNEL=n
at the same time
I am not a kernel developer, but I can see no logical reason why that
should be so.
Could somebody please comment on this? I hope my question makes sense.
Cheers,
Konrad
--
To unsubscribe from this list
Sorry about top-posting, using an webemail client.
This looks like you are using PV PCI passthrough? If so, did you
remember to use 'iommu=soft' to enable the Xen-SWIOTLB in your guest?
And are you booting with more than 4GB? Or is less than 3GB (so that you have
a nice gap in E820).
- Origin
/initiator/index: 0
For full details of the IBFT structure please take a look at:
ftp://ftp.software.ibm.com/systems/support/system_x_pdf/ibm_iscsi_boot_firmware_table_v1.02.pdf
Signed-off-by: Konrad Rzeszutek <[EMAIL PROTECTED]>
Cc: Mike Christie <[EMAIL PROTECTED]>
Cc: Peter Jones
On Friday 01 February 2008 19:18:09 James Bottomley wrote:
> On Wed, 2008-01-30 at 17:37 -0400, Konrad Rzeszutek wrote:
> > This patch (v0.4.6) adds
> Some pieces of the patch are obviously wrong: find_ibft() shouldn't be
> in ibft_init ... if ibft_phys was zero, it means the
/index: 0
For full details of the IBFT structure please take a look at:
ftp://ftp.software.ibm.com/systems/support/system_x_pdf/ibm_iscsi_boot_firmware_table_v1.02.pdf
Signed-off-by: Konrad Rzeszutek <[EMAIL PROTECTED]>
Cc: Mike Christie <[EMAIL PROTECTED]>
Cc: Peter Jones <[
On 1/17/2013 8:05 AM, Jan Beulich wrote:
On 17.01.13 at 13:22, Matt Wilson wrote:
On Wed, Jan 16, 2013 at 04:22:49PM -0500, Konrad Rzeszutek Wilk wrote:
We have the framework to use v2, but there are no backends that
actually use it. The end result is that on PV we use v2 grants
and on
t Linux detects DMA for all devices (see
dmesg).
What could I do? Try the 2.4.2-ac12 kernel?
cu Konrad
PS: Please excuse my BAD English - I'm only a 14-year-old schoolboy ;-)
--
Konrad Stopsack - [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe lin
r it's a bug or a feature?
I'm really waiting for your answer - else I might get crazy with this problem
:-((
I attached both dmesg and /proc/ide/via, and my old posting.
cu Konrad
boot messages of 2.4.2-ac12:
Linux version 2.4.2-ac12 (root@Stopsack) (gcc version 2.95.2 199910
Vojtech Pavlik wrote:
> On Thu, Mar 08, 2001 at 09:01:15AM +0100, Konrad Stopsack wrote:
>
> > Do you mean the Power Supply Unit? Or the Program Storage Unit? ;-)
>
> Power Supply Unit, yes.
>
> > To answer to your questions:
> > - I haven't tried to
Vojtech Pavlik wrote:
> On Thu, Mar 08, 2001 at 09:51:43AM +0100, Konrad Stopsack wrote:
>
> > > I don't see any other way how the ZIP could have impact on the IDE
HDD
> > > on a different IDE interface.
> > The 82c586b can be a chip with locked-together IDE
Vojtech Pavlik wrote:
> On Thu, Mar 08, 2001 at 10:06:57AM +0100, Konrad Stopsack wrote:
> > Vojtech Pavlik wrote:
> > > On Thu, Mar 08, 2001 at 09:51:43AM +0100, Konrad Stopsack wrote:
> > >
> > > > > I don't see any other way how the ZIP could ha
Hello!
I have a notebook with this sis 7001 usb-controller and sis 630
chipset.(shared memory 8mb), motherboard uniwill 340s2.
Kernel 2.2.x 2.4.1 -2.4.5
X-winows 3.x -4x.
Many low-cost notebooks have this chipset.
All works fine, like my usb-webcam, usb-scanner and my usb-zip-drive with
usb
> and you don't need to call kobject_del() right before kobject_put().
> Hm, that last one was always true, so that wasn't needed before...
>
> Do you want me to add this to my driver/ tree and fix up the kobject
> issues there so it all builds properly, and it gets sent to Linu
/ibm_iscsi_boot_firmware_table_v1.02.pdf
Please note that this patch depends on the Greg KH patches tree
kobject changes.
Signed-off-by: Konrad Rzeszutek <[EMAIL PROTECTED]>
diff --git a/Documentation/ABI/testing/sysfs-ibft
b/Documentation/ABI/testing/sysfs-ibft
new file mode 100644
index 000..4898740
--- /de
Signed-off-by: Konrad Rzeszutek <[EMAIL PROTECTED]>
Signed-off-by: Peter Jones <[EMAIL PROTECTED]>
diff --git a/Documentation/ABI/testing/sysfs-ibft
b/Documentation/ABI/testing/sysfs-ibft
new file mode 100644
index 000..941ad9f
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-
On Thu, Nov 29, 2007 at 11:36:21AM -0400, [EMAIL PROTECTED] wrote:
> > >
> > > /sys/firmware/ibft/ethernet0/pci-bdf
> > > 5:1:0
> >
> > shouldn't this somehow also have a symlink to the kernels ethX view of
> > ethernet devices?
> > (and if so.. how much of the info is duplicated..)
>
> That NIC
On Tue, Dec 04, 2007 at 09:12:11PM -0600, Doug Maxey wrote:
> Overall, looks nice. Good work.
Thank you.
>
> comments inline below...
>
.. snip ..
> > +#include
>
> Is the current include from open-iscsi being duplicated? If not, why
> not consolidate in one file?
The include files that com
On Tue, Dec 04, 2007 at 09:12:11PM -0600, Doug Maxey wrote:
> Overall, looks nice. Good work.
Thank you.
>
> comments inline below...
>
> On Tue, 04 Dec 2007 20:44:19 -0400, [EMAIL PROTECTED] wrote:
> > On Wed, Nov 28, 2007 at 07:34:22PM -0400, Konrad Rzeszutek wrote:
&
On Wed, Dec 05, 2007 at 02:26:40PM -0600, Doug Maxey wrote:
>
> On Wed, 05 Dec 2007 13:41:21 -0400, Konrad Rzeszutek wrote:
> > > Is the current include from open-iscsi being duplicated? If not, why
> > > not consolidate in one file?
> >
> > The include file
On Wed, Dec 05, 2007 at 03:02:56PM -0600, Doug Maxey wrote:
> [added cc: to mikec]
>
> On Wed, 05 Dec 2007 16:40:46 -0400, Konrad Rzeszutek wrote:
> > On Wed, Dec 05, 2007 at 02:26:40PM -0600, Doug Maxey wrote:
> > >
> > > On Wed, 05 Dec 2007 13:41:21 -0400, Kon
at:
ftp://ftp.software.ibm.com/systems/support/system_x_pdf/ibm_iscsi_boot_firmware_table_v1.02.pdf
Signed-off-by: Konrad Rzeszutek <[EMAIL PROTECTED]>
Signed-off-by: Peter Jones <[EMAIL PROTECTED]>
diff --git a/arch/x86/kernel/setup_32.c b/arch/x86/kernel/setup_32.c
index e1e18c3..e3
On Monday 26 November 2007 22:31:38 Greg KH wrote:
> On Mon, Nov 26, 2007 at 06:56:42PM -0400, Konrad Rzeszutek wrote:
> > +/*
> > + * Routines for reading of the iBFT data in a human readable fashion.
> > + */
> > +ssize_t ibft_attr_show_initiator
.. snip..
> > +#else
> > +static void __init reserve_ibft_region(void) { };
>
> No ending ; above.
Fixed.
>
..snip..
> > +static void __init reserve_ibft_region(void) { };
>
> Ditto.
Fixed.
.. snip..
> > +#include
> > +
>
> No blank line here, please.
Why that creeps back in the code I am not
> >
> > sysfs files have ONE VALUE PER FILE, not a whole bunch of different
> > things in a single file. Please fix this.
>
> The subparameters _are_ actually part of a single value, that value being
> associated with the initiator instance.
>
> Konrad is tryin
/ibm_iscsi_boot_firmware_table_v1.02.pdf
Please note that this patch depends on the Greg KH patches tree
kobject changes.
Signed-off-by: Konrad Rzeszutek <[EMAIL PROTECTED]>
diff --git a/Documentation/ABI/testing/sysfs-ibft
b/Documentation/ABI/testing/sysfs-ibft
new file mode 100644
index 000..4898740
--- /de
For full details of the IBFT structure please take a look at:
ftp://ftp.software.ibm.com/systems/support/system_x_pdf/ibm_iscsi_boot_firmware_table_v1.02.pdf
Signed-off-by: Konrad Rzeszutek <[EMAIL PROTECTED]>
diff --git a/Documentation/ABI/testing/sysfs-ibft
b/Documentation/ABI/testing
On Sunday 27 January 2008 01:01:23 you wrote:
> > On Fri, 25 Jan 2008 18:06:29 -0400 Konrad Rzeszutek <[EMAIL PROTECTED]>
> > wrote: Hey Andrew,
> >
> > Please add this patch along with Greg KH's kobject fixes.
>
> erm, OK. But I don't think I'
> iBFT is not platform-independent; it only makes sense on platforms with
> ACPI (and even then, just barely; ACPI is a poor fit for it and it was
> probably "integrated" with ACPI for political reasons.)
The spec just mentions that iBFT table has to be "compatible with an ACPI
table format" and
/initiator/index: 0
For full details of the IBFT structure please take a look at:
ftp://ftp.software.ibm.com/systems/support/system_x_pdf/ibm_iscsi_boot_firmware_table_v1.02.pdf
Please note that this patch depends on the Greg KH patches tree
kobject changes.
Signed-off-by: Konrad Rzeszutek <[EM
On Tuesday 29 January 2008 14:15:15 Mike Christie wrote:
> Konrad Rzeszutek wrote:
> > +/*
> > + * Helper functions to parse data properly.
> > + */
> > +static ssize_t sprintf_ipaddr(char *buf, u8 *ip)
> > +{
> > + if (ip[0] == 0 && ip[1] == 0
thing is really needed? printk_address() is pretty
> slow and touch_nmi_watchdog is _reasonably_ fast. It could be made heaps
> faster by:
>
> From: Andrew Morton <[EMAIL PROTECTED]>
>
> Avoid dirtying remote cpu's memory if it already has the correct va
On large memory configuration with not so fast CPUs the NMI watchdog
is triggered when memory addresses are being gathered and printed.
The code paths for Alt-SysRq-t are sprinkled with touch_nmi_watchdog
in various places but not in this routine (or in the loop that utilizes
this function). The
This patch touches the NMI watchdog every MAX_ORDER_NR_PAGES
to inhibit the machine from triggering an NMI while the CPUs
are locked. This situation is happening on boxes with more
than 64CPUs and 128GB of RAM when Alt-SysRq-m is performed.
It has been succesfully tested for regression on uni, 2,
This patch fixes the checkpoint.pl warning:
WARNING: Prefer printk_ratelimited or pr__ratelimited to
printk_ratelimit
Signed-off-by: Konrad Malkowski
---
drivers/staging/lustre/lnet/libcfs/tracefile.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers
> [#2] SMP
>
> Fixes: eee9602ad649 ("arm64: dts: qcom: qcm6490: Add device-tree for
> Fairphone 5")
> Signed-off-by: Luca Weiss
> ---
Reviewed-by: Konrad Dybcio
Konrad
o that said resource can be enabled, but
slightly later :/
Konrad
type = "passive";
I don't fancy burnt fingers for dinner!
Konrad
On 1/10/24 16:21, Luca Weiss wrote:
Specify the file name for the squashed/non-split firmware with the .mbn
extension instead of the split .mdt. The kernel can load both but the
squashed version is preferred in dts nowadays.
Signed-off-by: Luca Weiss
---
Thanks!
Reviewed-by: Konrad
ric;
+ qcom,hw-settle-time-us = <200>;
My ocd would rather see the boolean property at the end
anyway
Reviewed-by: Konrad Dybcio
Konrad
On 1/9/24 12:24, Luca Weiss wrote:
On Tue Jan 9, 2024 at 11:09 AM CET, Konrad Dybcio wrote:
On 1/5/24 15:54, Luca Weiss wrote:
Configure the thermals for the PA_THERM1, MSM_THERM, PA_THERM0,
RFC_CAM_THERM, CAM_FLASH_THERM and QUIET_THERM thermistors connected to
PM6150L.
Due to hardware
t dynamic rmtfs alloc, which should be possible
on some (most?) boards after 9265bc6bce6919c771970e5a425a66551a1c78a0?
Konrad
this one though, did you confirm that MDSS goes off
when you assert it?
Konrad
On 1/23/24 22:03, Luca Weiss wrote:
From: Vladimir Lypak
With this reset we can avoid situations like IRQ storms from DSI host
before it even started probing (because boot-loader left DSI IRQs on).
Signed-off-by: Vladimir Lypak
Signed-off-by: Luca Weiss
---
Reviewed-by: Konrad Dybcio
y = <0>;
+
+ thermal-sensors = <&tsens0 7>;
cpuss0-thermal and cpuss1-thermal are very likely the sensors for
cluster0/1, can you test that out, perhaps with corepinning+stress?
You can then assign multiple cpu cooling devices.
LGTM otherwise!
Konrad
On 1/21/24 11:09, Luca Weiss wrote:
This device has a vibrator attached to the CAMSS_GP0_CLK, use clk-pwm
and pwm-vibrator to make the vibrator work.
Signed-off-by: Luca Weiss
---
now your mainlined smartwatch can wake you up!
Reviewed-by: Konrad Dybcio
Konrad
m8953-iommu", "qcom,msm-iommu-v2";
+ ranges = <0 0x01c48000 0x8000>;
+
+ clocks = <&gcc GCC_OXILI_AHB_CLK>,
+ <&gcc GCC_BIMC_GFX_CLK>;
And align these
Konrad
gpu_opp_table: opp-table {
+ compatible = "operating-points-v2";
+
+ opp-1920 {
+ opp-hz = /bits/ 64 <1920>;
+ opp-supported-hw = <0xff>;
+ required-opps = <&rpmpd_opp_min_svs>;
+ };
If you remove all OPPs but this one, can the GPU still spit out pixels?
Konrad
On 27.01.2024 18:24, Luca Weiss wrote:
> On Freitag, 26. Jänner 2024 00:49:55 CET Konrad Dybcio wrote:
>> On 1/25/24 23:24, Dmitry Baryshkov wrote:
>>> On 25/01/2024 23:56, Luca Weiss wrote:
>>>> From: Vladimir Lypak
>>>>
>>>> Add the IOMM
On 27.01.2024 18:32, Luca Weiss wrote:
> On Freitag, 26. Jänner 2024 00:50:43 CET Konrad Dybcio wrote:
>> On 1/25/24 22:56, Luca Weiss wrote:
>>> From: Vladimir Lypak
>>>
>>> Add the GPU node for the Adreno 506 found on this family of SoCs. The
>>> clo
RPMPD_SMPB,
+ .res_id = 4,
+ .key = KEY_CORNER,
+};
I don't see a s4b_ao downstream.. Though it's very unfortunate we
didn't choose to add power-domain-cells or sth and set the bucket
through that..
Konrad
On 2/10/24 15:12, Luca Weiss wrote:
Add the power domains CX & GFX found on MSM8974 devices that use PMA8084
instead of the standard PM8841+PM8941 combo.
Signed-off-by: Luca Weiss
---
Same comment as p2, gfx_ao may not make much sense on this
platform
Konrad
On 2/10/24 17:38, Luca Weiss wrote:
Add the power domains CX & GFX found on devices with MSM8974 and PM8841.
Signed-off-by: Luca Weiss
---
Reviewed-by: Konrad Dybcio
Konrad
On 2/10/24 17:38, Luca Weiss wrote:
Add the power domains CX & GFX found on MSM8974 devices that use PMA8084
instead of the standard PM8841+PM8941 combo.
Signed-off-by: Luca Weiss
---
Reviewed-by: Konrad Dybcio
Konrad
On 2/10/24 17:28, Luca Weiss wrote:
From: Ivaylo Ivanov
Add CPU and SAW/ACC nodes to enable SMP on MSM8226.
Signed-off-by: Ivaylo Ivanov
[luca: update some nodes to fix dtbs_check errors, reorder, cleanup]
Signed-off-by: Luca Weiss
---
Reviewed-by: Konrad Dybcio
Konrad
Signed-off-by: Matti Lehtimäki
[luca: add more text to commit message]
Acked-by: Konrad Dybcio
Signed-off-by: Luca Weiss
---
Due to the nature of this change, it's hard to thoroughly review,
but nothing screams nuclear breakage, so:
Acked-by: Konrad Dybcio
Konrad
igned-off-by: Craig Tatlor
> Signed-off-by: Luca Weiss
> ---
Reviewed-by: Konrad Dybcio
Konrad
On 16.02.2024 14:11, Luca Weiss wrote:
> Add the definition for the interconnect used in the display subsystem.
>
> Signed-off-by: Luca Weiss
> ---
Reviewed-by: Konrad Dybcio
Konrad
a Weiss
---
https://3dmodels.org/360-view/?id=82800
Doesn't look like!
Reviewed-by: Konrad Dybcio
Konrad
On 3/6/24 00:18, Luca Weiss wrote:
Clean up some easy things do prepare the dts for further changes.
* Move pinctrl-names below pinctrl-*
* Move status as last property
* Remove default linux,input-type value
Signed-off-by: Luca Weiss
---
Reviewed-by: Konrad Dybcio
Konrad
1 - 100 of 2858 matches
Mail list logo
