One-element arrays are deprecated, and we are replacing them with
flexible array members instead. So, replace one-element array with
flexible-array member in structs _ATOM_CONNECTOR_DEVICE_TAG_RECORD,
_ATOM_OBJECT_GPIO_CNTL_RECORD, _ATOM_BRACKET_LAYOUT_RECORD,
_ATOM_BRACKET_LAYOUT_RECORD,
On Tue, 8 Nov 2022 at 22:28, Jason Gunthorpe wrote:
>
> On Tue, Nov 08, 2022 at 06:33:23AM +1000, Dave Airlie wrote:
>
> > At plumbers we decided a direction, I think the direction is good, if
> > there is refactoring to be done, I'd rather it was done in tree with a
> > clear direction.
> >
> >
> From: Jason Gunthorpe
> Sent: Wednesday, November 9, 2022 9:05 AM
>
> On Tue, Nov 08, 2022 at 03:55:20PM -0700, Alex Williamson wrote:
>
> > > > So why exactly isn't this an issue for VDPA? Are we just burying our
> > > > head in the sand that such platforms exists and can still be useful
>
On Fri, 4 Nov 2022 at 21:33, Maxime Ripard wrote:
>
> The Spreadtrum composite clocks implements a mux with a set_parent
> hook, but doesn't provide a determine_rate implementation.
>
> This is a bit odd, since set_parent() is there to, as its name implies,
> change the parent of a clock.
On Tue, Nov 08, 2022 at 11:50:04AM -0500, Felix Kuehling wrote:
> While you're making the pmu list per-device, I'd suggest removing adev from
> the pmu entry because it is now redundant. The device is implied by the list
> that the entry is on. Instead, add an adev parameter to
>
Hi Maxime,
I ran your v7 patchset on my Pi with Xorg, and the mode switching, as well as
the preferred mode handling, all work really well now!
I just noted that the downstream version of the vc4 driver still has inaccurate
field delays in vc4_crtc.c, which causes vertical lines to appear jagged
On Tue, Nov 08, 2022 at 03:55:20PM -0700, Alex Williamson wrote:
> > > So why exactly isn't this an issue for VDPA? Are we just burying our
> > > head in the sand that such platforms exists and can still be useful
> > > given the appropriate risk vs reward trade-off?
> >
> > Simply that
On Tue, Nov 08, 2022 at 03:28:31PM -0700, Alex Williamson wrote:
> Perhaps this should have been obvious, but I'm realizing that
> vfio-noiommu mode is completely missing without VFIO_CONTAINER, which
> seems a barrier to deprecating VFIO_CONTAINER and perhaps makes it a
Yes, it is the same as
From: Nathan Huckleberry
The mode_valid field in drm_bridge_helper_funcs is expected to be of
type
enum drm_mode_status (* mode_valid) (struct drm_bridge *bridge,
struct drm_display_mode *mode);
The mismatched return type breaks forward edge kCFI since the
DG2 has been very usable for a while now, and all of the uapi changes
related to fundamental platform usage have been finalized. Recent CI
results have also been healthy, so we're ready to drop the force_probe
requirement and enable the platform by default.
Cc: Rodrigo Vivi
Cc: Tvrtko Ursulin
On Mon, 7 Nov 2022 14:45:59 -0400
Jason Gunthorpe wrote:
> On Mon, Nov 07, 2022 at 11:05:08AM -0700, Alex Williamson wrote:
>
> > After further consideration... I don't think the option on vfio-main
> > makes sense, basically for the same reason that the original option
> > existed on the IOMMU
On Mon, 7 Nov 2022 20:52:54 -0400
Jason Gunthorpe wrote:
> Add a kconfig CONFIG_VFIO_CONTAINER that controls compiling the container
> code. If 'n' then only iommufd will provide the container service. All the
> support for vfio iommu drivers, including type1, will not be built.
>
> This
Hi Lukas, Maxime and everyone,
W dniu 8.11.2022 o 14:17, Lukas Satin pisze:
> They are important for retrogaming and connecting TV out to CRT TV or using
> emulator.
>
> I have PS1 that is using PAL-60 for example.
>
> Can you add 240p and 288p non-interlaced modes for NTSC and PAL, please?
To
On Tue, Nov 8, 2022 at 10:54 AM Daniel Vetter wrote:
>
> On Mon, Nov 07, 2022 at 09:25:38PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Repost of the stragglers from
> > https://patchwork.freedesktop.org/series/100393/
> >
> > Note that I didn't rerun the cocci stuff, nor have I
On Tue, Nov 8, 2022 at 7:51 PM Simon Ser wrote:
>
> cc'ing Pekka and wayland-devel for userspace devs feedback on the new uAPI.
>
> On Saturday, October 29th, 2022 at 14:08, Dmitry Baryshkov
> wrote:
>
> > On 29/10/2022 01:59, Jessica Zhang wrote:
> > > Add support for COLOR_FILL and
Hi Lukas,
W dniu 8.11.2022 o 14:28, Lukas Satin pisze:
> Hi, your statement:
>
> "However, analog display usually have fairly loose timings requirements,
> the only discrete parameters being the total number of lines and pixel
> clock frequency."
>
> Please do not make it as a rule. You said
Hi Noralf,
W dniu 8.11.2022 o 10:38, Noralf Trønnes pisze:
>
> Den 07.11.2022 19.03, skrev Noralf Trønnes:
>>
>> Den 07.11.2022 15.16, skrev Maxime Ripard:
>>> Now that we can easily extend the named modes list, let's add a few more
>>> analog TV modes that were used in the wild, and some unit
On 08/11/2022 00:56, Bryan O'Donoghue wrote:
> Each compatible has a different set of clocks which are associated with it.
> Add in the list of clocks for each compatible.
>
> Cc: Rob Clark
> Cc: Abhinav Kumar
> Cc: Dmitry Baryshkov
> Cc: Sean Paul
> Cc: David Airlie
> Cc: Daniel Vetter
>
On 08/11/2022 13:46, Dmitry Baryshkov wrote:
> On 08/11/2022 02:56, Bryan O'Donoghue wrote:
>> Currently we do not differentiate between the various users of the
>> qcom,mdss-dsi-ctrl. The driver is flexible enough to operate from one
>> compatible string but, the hardware does have some
On 08/11/2022 00:56, Bryan O'Donoghue wrote:
> Sort the order of the compatible strings alphanumerically.
>
> Cc: Rob Clark
> Cc: Abhinav Kumar
> Cc: Dmitry Baryshkov
> Cc: Sean Paul
> Cc: David Airlie
> Cc: Daniel Vetter
> Cc: Rob Herring
> Cc: Krzysztof Kozlowski
> Cc:
On 08/11/2022 00:56, Bryan O'Donoghue wrote:
> There's a typo in describing the core clock as an 'escape' clock. The
> accurate description is 'core'.
>
> Fixes: 4dbe55c97741 ("dt-bindings: msm: dsi: add yaml schemas for DSI
> bindings")
> Cc: Rob Clark
Acked-by: Krzysztof Kozlowski
Best
On 08/11/2022 00:56, Bryan O'Donoghue wrote:
> When converting from .txt to .yaml we didn't include descriptions for the
> existing regulator supplies.
>
> - vdd
> - vdda
> - vddio
>
> Add those descriptions into the yaml now as they were prior to the
> conversion. Mark the supplies as required
On 08/11/2022 00:56, Bryan O'Donoghue wrote:
> power-domain is required for the sc7180 dispcc GDSC but not every qcom SoC
> has a similar dependency for example the aqp8064.
>
> Most Qcom SoC's using mdss-dsi-ctrl seem to have the ability to
> power-collapse the MDP without collapsing DSI.
>
>
Hi Thomas.
> drm/nouveau/kms: switch to drm fbdev helpers
Noticed this little gem between all the other goodies in this pull
request. Just in case it is interesting and you missed it.
Sam
On 11/8/2022 01:01, Tvrtko Ursulin wrote:
On 07/11/2022 19:14, John Harrison wrote:
On 11/7/2022 08:17, Tvrtko Ursulin wrote:
On 07/11/2022 09:33, Tvrtko Ursulin wrote:
On 05/11/2022 01:03, Ceraolo Spurio, Daniele wrote:
On 11/4/2022 10:25 AM, john.c.harri...@intel.com wrote:
From: John
Hi Liviu,
The only issue that I'm seeing that is not critical is that at reboot/shutdown
time
I'm getting an "Unexpected global fault, this could be serious" from the smmu:
[ 6893.467910] arm-smmu 7fb3.iommu: disabling translation
[ 6893.473550] ohci-platform 7ffb.usb: Removing from
On 11/8/2022 04:26, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Convert some usages of legacy DRM logging macros into versions which tell
us on which device have the events occurred.
v2:
* Don't have struct drm_device as local. (Jani, Ville)
Signed-off-by: Tvrtko Ursulin
Cc: Jani Nikula
On 11/7/22 09:37, Carlos Bilbao wrote:
> Correct descriptions of two last fields of enum pipe_split_policy, updating
> comments with proper field names.
>
> Signed-off-by: Carlos Bilbao
Reviewed-by: Harry Wentland
Harry
> ---
> drivers/gpu/drm/amd/display/dc/dc.h | 9 +
> 1 file
On Tue, Nov 08, 2022 at 06:37:19PM +0100, Matthias Brugger wrote:
>
>
> On 07/11/2022 08:22, Nancy.Lin wrote:
> > Simplify code for update mmsys reg.
> >
> > Signed-off-by: Nancy.Lin
> > Reviewed-by: AngeloGioacchino Del Regno
> >
> > Reviewed-by: CK Hu
> > Tested-by: AngeloGioacchino Del
On 11/8/2022 01:08, Tvrtko Ursulin wrote:
On 07/11/2022 19:45, John Harrison wrote:
On 11/7/2022 06:09, Tvrtko Ursulin wrote:
On 04/11/2022 17:45, John Harrison wrote:
On 11/4/2022 03:01, Tvrtko Ursulin wrote:
On 03/11/2022 19:16, John Harrison wrote:
On 11/3/2022 02:38, Tvrtko Ursulin
On Tue, Nov 08, 2022 at 06:46:54PM +0100, Matthias Brugger wrote:
> On 07/11/2022 08:22, Nancy.Lin wrote:
[..]
> > --- a/drivers/soc/mediatek/mtk-mmsys.c
> > +++ b/drivers/soc/mediatek/mtk-mmsys.c
> > @@ -80,6 +80,12 @@ static const struct mtk_mmsys_driver_data
> > mt8195_vdosys0_driver_data = {
cc'ing Pekka and wayland-devel for userspace devs feedback on the new uAPI.
On Saturday, October 29th, 2022 at 14:08, Dmitry Baryshkov
wrote:
> On 29/10/2022 01:59, Jessica Zhang wrote:
> > Add support for COLOR_FILL and COLOR_FILL_FORMAT properties for
> > drm_plane. In addition, add support
Create a symlink pointing to USB Type-C connector for DRM connectors
when they are created. The link will be created only if the firmware is
able to describe the connection beween the two connectors.
Currently, even if a display uses a USB Type-C port, there is no way for
the userspace to find
If drm_sysfs_minor_alloc() fail in drm_minor_alloc() we can end up
freeing invalid minor->kdev pointer and drm_minor_alloc_release()
will crash like below:
RIP: 0010:kobject_put+0x19/0x1c0
RSP: 0018:bc7001637c38 EFLAGS: 00010282
RAX: a8d6deb0 RBX: RCX:
Many dual-GPU notebook systems are equipped with a multiplexer ("mux")
to switch the signal source for the internal display panel between the
discrete and integrated GPUs. The vga-switcheroo infrastructure in the
Linux kernel can expose mux switch functionality to userspace via a
simple debugfs
Hi Xinlei,
Somehow b4 broke with your thread but I was able to apply patch 1 and 2 by hand.
Thanks
Matthias
On 24/10/2022 04:04, xinlei@mediatek.com wrote:
From: Xinlei Lee
Base on the branch of linus/master v6.1 rc1.
Change since v12:
1. Add MT8186_ prefix to variables added in
On Saturday, October 29th, 2022 at 13:23, Dmitry Baryshkov
wrote:
> On 29/10/2022 01:59, Jessica Zhang wrote:
>
> > Add support for COLOR_FILL and COLOR_FILL_FORMAT properties for
> > drm_plane. In addition, add support for setting and getting the values
> > of these properties.
> >
> >
https://bugzilla.kernel.org/show_bug.cgi?id=203033
Murph (mu...@clurictec.com) changed:
What|Removed |Added
CC||mu...@clurictec.com
---
On 08/11/2022 19:11, Matthias Brugger wrote:
Hi Xinlei,
Can you please fix the threading of this patches. I can see that this 1/3 but
I'm not able to find 3/3 in the series. The first two look good, the third, I
don't know.
Nevermind this message, the problem was on my side.
Regards,
Hi Xinlei,
Can you please fix the threading of this patches. I can see that this 1/3 but
I'm not able to find 3/3 in the series. The first two look good, the third, I
don't know.
Regards,
Matthias
On 24/10/2022 04:04, xinlei@mediatek.com wrote:
From: Xinlei Lee
The difference between
v3d_perfmon_open_file() instantiates a mutex for a particular file
instance, but it never destroys it by calling mutex_destroy() in
v3d_perfmon_close_file().
Similarly, v3d_perfmon_create_ioctl() instantiates a mutex for a
particular perfmon, but it never destroys it by calling mutex_destroy()
in
mutex_init is supposed to be balanced by a call to mutex_destroy, but
this is not currently happening on the v3d driver.
Considering the introduction of a DRM-managed mutex_init variant, switch
to the drmm_mutex_init.
Signed-off-by: Maíra Canal
Reviewed-by: Daniel Vetter
---
This series introduces some changes to assure the correct resource release on
the V3D driver, especially the mutex. Currently, the V3D has no mutex_destroy()
calls, which means that a mutex is being instantiated, but it is not being
released by the end of its use.
So, use the DRM-managed
On Tue, Nov 08, 2022 at 03:41:25PM +0800, Yi Liu wrote:
> On 2022/11/8 14:10, Nicolin Chen wrote:
> > On Mon, Nov 07, 2022 at 08:52:51PM -0400, Jason Gunthorpe wrote:
> >
> > > @@ -795,6 +800,10 @@ static int vfio_device_first_open(struct vfio_device
> > > *device)
> > > ret =
On Mon, Nov 07, 2022 at 10:10:59PM -0800, Nicolin Chen wrote:
> > @@ -812,6 +821,7 @@ static int vfio_device_first_open(struct vfio_device
> > *device)
> > device->kvm = NULL;
> > if (device->group->container)
> > vfio_group_unuse_container(device->group);
> > +
On 07/11/2022 08:22, Nancy.Lin wrote:
Add vdosys1 mmsys compatible for MT8195 platform.
For MT8195, VDOSYS0 and VDOSYS1 are 2 display HW pipelines binding to
2 different power domains, different clock drivers and different
mediatek-drm drivers.
Signed-off-by: Nancy.Lin
Reviewed-by: Nícolas
On 07/11/2022 08:22, Nancy.Lin wrote:
Add mt8195 vdosys1 routing table to the driver data of mtk-mmsys.
Signed-off-by: Nancy.Lin
Reviewed-by: AngeloGioacchino Del Regno
Reviewed-by: Rex-BC Chen
Reviewed-by: CK Hu
Tested-by: AngeloGioacchino Del Regno
Tested-by: Bo-Chen Chen
---
On 07/11/2022 08:22, Nancy.Lin wrote:
Add four mmsys config APIs. The config APIs are used for config
mmsys reg. Some mmsys regs need to be set according to the
HW engine binding to the mmsys simultaneously.
1. mtk_mmsys_merge_async_config: config merge async width/height.
async is used
On 11/8/22 20:06, Robin Murphy wrote:
> Although we don't use 1GB block mappings, we still need to split
> map/unmap requests at 1GB boundaries to match what io-pgtable expects.
> Fix that, and add some explanation to make sense of it all.
>
> Fixes: 3740b081795a ("drm/panfrost: Update io-pgtable
On 07/11/2022 08:22, Nancy.Lin wrote:
Simplify code for update mmsys reg.
Signed-off-by: Nancy.Lin
Reviewed-by: AngeloGioacchino Del Regno
Reviewed-by: CK Hu
Tested-by: AngeloGioacchino Del Regno
Tested-by: Bo-Chen Chen
Reviewed-by: Nícolas F. R. A. Prado
---
Jadard JD9365DA-H3 is WXGA MIPI DSI panel and it support TFT
dot matrix LCD with 800RGBx1280 dots at maximum.
Add support for it.
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Jagan Teki
---
Changes for v4:
- add delay explictly
- update init sequence
Changes for v3:
- updatd to WXGA
- use
Jadard JD9365DA-H3 is WXGA MIPI DSI panel and it support TFT
dot matrix LCD with 800RGBx1280 dots at maximum.
Document it.
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Jagan Teki
Reviewed-by: Krzysztof Kozlowski
---
Changes for v4:
- none
Changes for v3:
- updated title
- collect
Jadard Technology Inc. manufactures and distributes chips
from Shenzhen.
Add vendor prefix for it.
Signed-off-by: Jagan Teki
Acked-by: Krzysztof Kozlowski
---
Changes for v4, v3, v2:
- none
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff
Chongzhou is a professional is a manufacturer of LCD panels
from Shenzhen.
Add vendor prefix for it.
Acked-by: Krzysztof Kozlowski
Signed-off-by: Jagan Teki
---
Changes for v4, v3, v2:
- none
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff
https://bugzilla.kernel.org/show_bug.cgi?id=216673
--- Comment #1 from Stanislav Modrak (stanislav.mod...@gmail.com) ---
Seems similar to
[https://gitlab.freedesktop.org/drm/amd/-/issues/2113](https://gitlab.freedesktop.org/drm/amd/-/issues/2113)
--
You may reply to this email to add a comment.
https://bugzilla.kernel.org/show_bug.cgi?id=216673
Bug ID: 216673
Summary: Recurring amdgpu freeze on kernel 6.0.6 only
Product: Drivers
Version: 2.5
Kernel Version: 6.0.6-060006-generic
Hardware: AMD
OS: Linux
Although we don't use 1GB block mappings, we still need to split
map/unmap requests at 1GB boundaries to match what io-pgtable expects.
Fix that, and add some explanation to make sense of it all.
Fixes: 3740b081795a ("drm/panfrost: Update io-pgtable API")
Reported-by: Dmitry Osipenko
On Tue, 8 Nov 2022 at 17:42, Bryan O'Donoghue
wrote:
>
> On 08/11/2022 12:59, Dmitry Baryshkov wrote:
> >>
> >> Warnings about missing regulators can be resolved by updating the
> >> relevant
> >> dtsi files to point to fixed always-on regulators where appropriate.
> >
> > Ugh. Are they missing
On 2022-10-28 18:48, Brian Norris wrote:
If there are multiple amdgpu devices, this list processing can be racy.
We're really treating this like a per-device list, so make that explicit
and remove the global list.
I agree with the problem and the solution. See one comment inline.
On Tue, 08 Nov 2022, Sandor Yu wrote:
> Run get_maintainer.pl for patch 1,
> Your email address is list as follow,
> Jani Nikula (commit_signer:2/8=25%)
>
> And I add the email address that comment as "commit_signer" into Cc list.
Please don't do that.
get_maintainer.pl gives you no less than
On Tue, 8 Nov 2022 at 20:33, Linus Walleij wrote:
>
> On Tue, Nov 8, 2022 at 3:53 PM Jagan Teki wrote:
> > On Tue, 8 Nov 2022 at 20:18, Linus Walleij wrote:
> > > On Tue, Nov 8, 2022 at 3:12 PM Jagan Teki wrote:
> > > > On Tue, 8 Nov 2022 at 19:31, Linus Walleij
> > > > wrote:
> > > > >
> >
On Mon, Nov 7, 2022 at 9:37 AM Carlos Bilbao wrote:
>
> Correct descriptions of two last fields of enum pipe_split_policy, updating
> comments with proper field names.
>
> Signed-off-by: Carlos Bilbao
Acked-by: Alex Deucher
> ---
> drivers/gpu/drm/amd/display/dc/dc.h | 9 +
> 1 file
On Mon, Nov 07, 2022 at 05:56:36PM +0200, Ville Syrjälä wrote:
> On Mon, Nov 07, 2022 at 04:40:41PM +0100, Stanislaw Gruszka wrote:
> > On Mon, Nov 07, 2022 at 05:10:48PM +0200, Ville Syrjälä wrote:
> > > On Mon, Nov 07, 2022 at 03:45:00PM +0100, Stanislaw Gruszka wrote:
> > > > index
On Tue, Nov 8, 2022 at 3:13 PM Tvrtko Ursulin
wrote:
>
>
> On 06/11/2022 21:02, Oded Gabbay wrote:
> > The accelerator devices are exposed to user-space using a dedicated
> > major. In addition, they are represented in /dev with new, dedicated
> > device char names: /dev/accel/accel*. This is
On Fri, Oct 28, 2022 at 6:48 PM Brian Norris wrote:
>
> If there are multiple amdgpu devices, this list processing can be racy.
>
> We're really treating this like a per-device list, so make that explicit
> and remove the global list.
>
> Signed-off-by: Brian Norris
@Kuehling, Felix @Kim,
On Tue, Nov 08, 2022 at 11:16:01PM +0800, Wei Li wrote:
> When doing "cat /proc/interrupts" after qxl.ko is unloaded, an oops occurs:
>
> BUG: unable to handle page fault for address: c0274769
> PGD 2a0d067 P4D 2a0d067 PUD 2a0f067 PMD 103f39067 PTE 0
> Oops: [#1] PREEMPT SMP PTI
>
On Mon, Nov 07, 2022 at 07:46:56PM -0300, Maíra Canal wrote:
> v3d_perfmon_open_file() instantiates a mutex for a particular file
> instance, but it never destroys it by calling mutex_destroy() in
> v3d_perfmon_close_file().
>
> Similarly, v3d_perfmon_create_ioctl() instantiates a mutex for a
>
Applied. Thanks!
Alex
On Mon, Nov 7, 2022 at 4:33 AM Paulo Miguel Almeida
wrote:
>
> One-element arrays are deprecated, and we are replacing them with
> flexible array members instead. So, replace one-element array with
> flexible-array member in structs _ATOM_GPIO_PIN_ASSIGNMENT,
>
On Mon, Nov 07, 2022 at 07:46:55PM -0300, Maíra Canal wrote:
> mutex_init() is supposed to be balanced by a call to mutex_destroy(), but
> this is not currently happening on the v3d driver.
>
> Considering the introduction of a DRM-managed mutex_init variant, switch
> to drmm_mutex_init.
>
>
On Mon, Nov 07, 2022 at 09:25:38PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Repost of the stragglers from
> https://patchwork.freedesktop.org/series/100393/
>
> Note that I didn't rerun the cocci stuff, nor have I had
> time to come up with something to inluce the cocci scripts
>
On Mon, Nov 07, 2022 at 05:39:34PM -0800, Zanoni, Paulo R wrote:
On Mon, 2022-11-07 at 00:52 -0800, Niranjana Vishwanathapura wrote:
Asynchronously unbind the vma upon vm_unbind call.
Fall back to synchronous unbind if backend doesn't support
async unbind or if async unbind fails.
No need for
I didn't test the patch yet. I will do. But even without testing I can
tell you that it will work (It will not crash).
Currently when the crash occurs, all screens remain black after resume.
I'm not able to login with ssh neither. And logs end before the
suspend. So the crash seems to be some
Applied. Thanks
On Fri, Nov 4, 2022 at 6:05 AM Hanjun Guo wrote:
>
> When the radeon driver reads the bios information from ACPI
> table in radeon_acpi_vfct_bios(), it misses to call acpi_put_table()
> to release the ACPI memory after the init, so add acpi_put_table()
> properly to fix the
On 08.11.2022 13:26, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Convert some usages of legacy DRM logging macros into versions which tell
us on which device have the events occurred.
v2:
* Don't have struct drm_device as local. (Jani, Ville)
Signed-off-by: Tvrtko Ursulin
Cc: Jani Nikula
On 2022/11/8 17:19, Nicolin Chen wrote:
On Mon, Nov 07, 2022 at 08:52:44PM -0400, Jason Gunthorpe wrote:
This is on github: https://github.com/jgunthorpe/linux/commits/vfio_iommufd
[...]
v2:
- Rebase to v6.1-rc3, v4 iommufd series
- Fixup comments and commit messages from list remarks
When doing "cat /proc/interrupts" after qxl.ko is unloaded, an oops occurs:
BUG: unable to handle page fault for address: c0274769
PGD 2a0d067 P4D 2a0d067 PUD 2a0f067 PMD 103f39067 PTE 0
Oops: [#1] PREEMPT SMP PTI
CPU: 6 PID: 246 Comm: cat Not tainted 6.1.0-rc2 #24
Hardware name:
Thanks. Merged with fixes for the following warnings.
66ba1150c07e (HEAD -> drm-misc-next) drm/fb-helper: Fix missing
kerneldoc include
-:6: ERROR:GIT_COMMIT_ID: Please use git commit description style
'commit <12+ chars of sha1> ("")' - ie: 'commit 8ab59da26bc0
("drm/fb-helper: Move generic
a-b: danvet via irc
Am 07.11.22 um 13:53 schrieb Thomas Zimmermann:
Cleaning up the fbdev code produced a number of simple build
errors. Fix them.
Thomas Zimmermann (3):
drm/fbdev: Include
drm/hisilicon/hibmc: Include for readl() and writel()
drm/fb-helper: Document struct
On Tue, Nov 8, 2022 at 3:53 PM Jagan Teki wrote:
> On Tue, 8 Nov 2022 at 20:18, Linus Walleij wrote:
> > On Tue, Nov 8, 2022 at 3:12 PM Jagan Teki wrote:
> > > On Tue, 8 Nov 2022 at 19:31, Linus Walleij
> > > wrote:
> > > >
> > > > On Thu, Nov 3, 2022 at 3:12 PM Jagan Teki wrote:
> > > >
> >
On Tue, 8 Nov 2022 at 20:18, Linus Walleij wrote:
>
> On Tue, Nov 8, 2022 at 3:12 PM Jagan Teki wrote:
> > On Tue, 8 Nov 2022 at 19:31, Linus Walleij wrote:
> > >
> > > On Thu, Nov 3, 2022 at 3:12 PM Jagan Teki wrote:
> > >
> > > > Jadard JD9365DA-H3 is WXGA MIPI DSI panel and it support TFT
>
Hi,
On Tue, Nov 08, 2022 at 03:14:20PM +0100, Philipp Zabel wrote:
> ipu_src_rect_width() was introduced to support odd screen resolutions
> such as 1366x768 by internally rounding up primary plane width to a
> multiple of 8 and compensating with reduced horizontal blanking.
> This also caused
On Tue, Nov 8, 2022 at 3:12 PM Jagan Teki wrote:
> On Tue, 8 Nov 2022 at 19:31, Linus Walleij wrote:
> >
> > On Thu, Nov 3, 2022 at 3:12 PM Jagan Teki wrote:
> >
> > > Jadard JD9365DA-H3 is WXGA MIPI DSI panel and it support TFT
> > > dot matrix LCD with 800RGBx1280 dots at maximum.
> > >
> > >
On 08/11/2022 12:59, Dmitry Baryshkov wrote:
Warnings about missing regulators can be resolved by updating the
relevant
dtsi files to point to fixed always-on regulators where appropriate.
Ugh. Are they missing or are they optional/not used on these platforms?
Some platforms either don't
ipu_src_rect_width() was introduced to support odd screen resolutions
such as 1366x768 by internally rounding up primary plane width to a
multiple of 8 and compensating with reduced horizontal blanking.
This also caused overlay plane width to be rounded up, which was not
intended. Fix overlay
On Tue, 8 Nov 2022 at 19:31, Linus Walleij wrote:
>
> On Thu, Nov 3, 2022 at 3:12 PM Jagan Teki wrote:
>
> > Jadard JD9365DA-H3 is WXGA MIPI DSI panel and it support TFT
> > dot matrix LCD with 800RGBx1280 dots at maximum.
> >
> > Add support for it.
> >
> > Cc: dri-devel@lists.freedesktop.org
>
On 11/7/22 19:50, Robin Murphy wrote:
> On 2022-11-04 20:48, Dmitry Osipenko wrote:
>> On 11/4/22 23:37, Robin Murphy wrote:
>>> On 2022-11-04 20:11, Dmitry Osipenko wrote:
On 8/23/22 01:01, Robin Murphy wrote:
> Convert to io-pgtable's bulk {map,unmap}_pages() APIs, to help the old
>
On Thu, Nov 3, 2022 at 3:12 PM Jagan Teki wrote:
> Jadard JD9365DA-H3 is WXGA MIPI DSI panel and it support TFT
> dot matrix LCD with 800RGBx1280 dots at maximum.
>
> Add support for it.
>
> Cc: dri-devel@lists.freedesktop.org
> Signed-off-by: Jagan Teki
> ---
> Changes for v3:
> - updatd to
Run get_maintainer.pl for patch 1,
Your email address is list as follow,
Jani Nikula (commit_signer:2/8=25%)
And I add the email address that comment as "commit_signer" into Cc list.
B.R
Sandor
> -Original Message-
> From: Jani Nikula
> Sent: 2022年11月8日 21:16
> To: Sandor Yu ;
Hi Lukas,
On Tue, Nov 8, 2022 at 2:20 PM Lukas Satin wrote:
> One can switch from NTSC to PAL now using (on vc4)
>
> modetest -M vc4 -s 53:720x480i -w 53:'TV mode':1 # NTSC
> modetest -M vc4 -s 53:720x576i -w 53:'TV mode':4 # PAL
>
> NTSC should be 640x480i, not 720. It will probably work on
On Fri, Nov 4, 2022 at 2:32 PM Maxime Ripard wrote:
> The UX500 sysctrl "set_parent" clocks implement a mux with a set_parent
> hook, but doesn't provide a determine_rate implementation.
>
> This is a bit odd, since set_parent() is there to, as its name implies,
> change the parent of a clock.
On Fri, Nov 4, 2022 at 2:32 PM Maxime Ripard wrote:
> The UX500 PRCMU "clkout" clock implements a mux with a set_parent hook,
> but doesn't provide a determine_rate implementation.
>
> This is a bit odd, since set_parent() is there to, as its name implies,
> change the parent of a clock.
Hello,
thanks for working on this and the updated version.
Am Freitag, 4. November 2022, 07:44:56 CET schrieb Sandor Yu:
> Add a new DRM HDMI bridge driver for Candence MHDP used in i.MX8MQ
> SOC. MHDP IP could support HDMI or DisplayPort standards according
> embedded Firmware running in the
On Tue, 08 Nov 2022, Sandor Yu wrote:
> The patch set initial support for Cadence MHDP(HDMI/DP) DRM bridge
> drivers and Cadence HDP-TX PHY(HDMI/DP) drivers for iMX8MQ.
Has some get_maintainer.pl guidance changed recently or something, or
why am I increasingly being Cc'd on patches that are
On 06/11/2022 21:02, Oded Gabbay wrote:
The accelerator devices are exposed to user-space using a dedicated
major. In addition, they are represented in /dev with new, dedicated
device char names: /dev/accel/accel*. This is done to make sure any
user-space software that tries to open a graphic
On Tue, Nov 8, 2022 at 12:48 PM wrote:
>
> return is not a function, parentheses are not required
>
> Signed-off-by: KaiLong Wang
ACPICA material is to be submitted to the upstream project at GitHub
(please see MAINTAINERS for the link).
You may notice, however, that your changes do not align
Add Cadence HDP-TX HDMI PHY driver.
Cadence HDP-TX PHY could be put in either DP mode or
HDMI mode base on the configuration chosen.
HDMI PHY mode is configurated in the driver.
Signed-off-by: Sandor Yu
---
drivers/phy/cadence/Kconfig | 8 +
drivers/phy/cadence/Makefile
Add bindings for Cadence HDP-TX HDMI PHY.
Signed-off-by: Sandor Yu
---
.../bindings/phy/cdns,hdptx-hdmi-phy.yaml | 50 +++
1 file changed, 50 insertions(+)
create mode 100644
Documentation/devicetree/bindings/phy/cdns,hdptx-hdmi-phy.yaml
diff --git
1 - 100 of 155 matches
Mail list logo
