On 21/06/2022 11:49, conor.doo...@microchip.com wrote:
> On 20/06/2022 01:25, Damien Le Moal wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
>> content is safe
>>
>> On 6/20/22 08:54, conor.doo...@microchip.com wrote:
>>> On 20/06/2022 00:38, Damien Le Moal wro
From: allen chen
add read max-lane and max-pixel-clock from dt property
Signed-off-by: Allen Chen
Signed-off-by: Pin-yen Lin
---
drivers/gpu/drm/bridge/ite-it6505.c | 35 ++---
1 file changed, 32 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/bridge/ite-it
On Fri, Jun 24, 2022 at 04:53:25PM +0200, Paul Kocialkowski wrote:
> Hello Dan,
>
> On Tue 14 Jun 22, 15:07, Dan Carpenter wrote:
> > Hello Paul Kocialkowski,
> >
> > The patch efeeaefe9be5: "drm: Add support for the LogiCVC display
> > controller" from May 20, 2022, leads to the following Smatch
On 2022-06-24 14:38:50, Chery, Nanley G wrote:
> +Jordan (FYI)
>
> I think the commit message has an extra "color" next to "CC".
> With or without that dropped,
>
> Reviewed-by: Nanley Chery
Reviewed-by: Jordan Justen
-base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/intel-lab-lkp/linux/commits/Venkateshwar-Rao-Gannavarapu/Add-Xilinx-DSI-Tx-subsystem-DRM-driver/20220616-222008
base: git://anongit.freedesktop.org/drm/drm drm-next
config: mips-randconfig-c00
On Fri, Jun 17, 2022 at 9:27 AM Neil Armstrong wrote:
>
> This adds an encoder bridge designed to drive a MIPI-DSI display
> by using the ENCL encoder through the internal MIPI DSI transceiver
> connected to the output of the ENCL pixel encoder.
>
> Signed-off-by: Neil Armstrong
> Reviewed-by: Ja
Hi Neil,
On Fri, Jun 17, 2022 at 9:27 AM Neil Armstrong wrote:
> +/* [31:16] RW intr_stat/clr. Default 0.
> + * For each bit, read as this interrupt level status,
> + * write 1 to clear.
Do you know if an interrupt line from GIC is routed to the MIPI-DSI
transceiver? If so
On Fri, Jun 17, 2022 at 01:52:04AM -0700, Lucas De Marchi wrote:
Like was done for read, provide the equivalent for write. Even if
current users are not in the hot path, this should future-proof it.
v2:
- Remove default from _Generic() - callers wanting to write more
than u64 should use iosy
On Fri, Jun 24, 2022 at 02:03:27PM -0700, Matt Roper wrote:
XEHPSDV_FLAT_CCS_BASE_ADDR, GEN8_L3_LRA_1_GPGPU, and MMCD_MISC_CTRL were
duplicated between i915_reg.h and intel_gt_regs.h. These are all GT
registers, so we should drop the copy from i915_reg.h.
XEHPSDV_TILE0_ADDR_RANGE was defined in
So this has been going on for a while, and it's quite annoying.
At bootup, my main desktop (Threadripper 3970X with radeon graphics)
now complains about
resource sanity check: requesting [mem 0xd000-0xdfff], which
spans more than BOOTFB [mem 0xd000-0xd02f]
and then gives me a n
Fix alignment of this line of code with the previous parenthesis, as
suggested by checkpatch.pl:
$ ./scripts/checkpatch.pl -f drivers/staging/fbtft/fb_tinylcd.c
CHECK: Alignment should match open parenthesis
#41: FILE: drivers/staging/fbtft/fb_tinylcd.c:41:
+ write_reg(par, 0xE0, 0x0
Reviewed-by: Caz Yokoyama
-caz
On Fri, Jun 24, 2022 at 2:04 PM Matt Roper
wrote:
> We've been introducing new registers with a mix of "XEHP_"
> (architecture) and "XEHPSDV_" (platform) prefixes. For consistency,
> let's settle on "XEHP_" as the preferred form.
>
> XEHPSDV_RP_STATE_CAP stays
Joe Perches writes:
> On Sat, 2022-06-25 at 19:00 -0700, David Reaver wrote:
>> Fix alignment of this line of code with the previous parenthesis, as
>> suggested by checkpatch.pl:
> []
>> diff --git a/drivers/staging/fbtft/fb_tinylcd.c
>> b/drivers/staging/fbtft/fb_tinylcd.c
> []
>> @@ -38,7 +
The pull request you sent on Sun, 26 Jun 2022 17:01:24 +0200:
> http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git
> tags/for-5.19/fbdev-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/be129fab66f284c239251ec5b6e30c6e903d8881
Thank you!
--
Deet-
Emails to Joonyoung Shim bounce ("550 5.1.1 Recipient address rejected:
User unknown"), so move him to credits file.
Signed-off-by: Krzysztof Kozlowski
---
CREDITS | 4
MAINTAINERS | 1 -
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/CREDITS b/CREDITS
index 7e85a53b6a88.
Emails to Joonyoung Shim bounce ("550 5.1.1 Recipient address rejected:
User unknown"), so remove him from maintainers of DT bindings (display,
phy).
Signed-off-by: Krzysztof Kozlowski
---
.../bindings/display/samsung/samsung,exynos-hdmi-ddc.yaml| 1 -
.../devicetree/bindings/display/sam
The following changes since commit a111daf0c53ae91e71fd2bfe7497862d14132e3e:
Linux 5.19-rc3 (2022-06-19 15:06:47 -0500)
are available in the Git repository at:
http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git
tags/for-5.19/fbdev-2
for you to fetch changes up to cb51773
sparse reports
drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dcn32/irq_service_dcn32.c:39:20:
warning: symbol 'to_dal_irq_source_dcn32' was not declared. Should it be static?
to_dal_irq_source_dnc32() is only referenced in irq_service_dnc32.c, so change
its
storage class specifier to static.
Fix
sparse reports
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:3885:6: warning:
symbol 'FORCE_RATE' was not declared. Should it be static?
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:3886:10: warning:
symbol 'FORCE_LANE_COUNT' was not declared. Should it be static?
Neit
https://bugzilla.kernel.org/show_bug.cgi?id=216175
--- Comment #4 from nobutarounos...@gmail.com ---
Created attachment 301280
--> https://bugzilla.kernel.org/attachment.cgi?id=301280&action=edit
.config for my kernel build.
--
You may reply to this email to add a comment.
You are receiving t
https://bugzilla.kernel.org/show_bug.cgi?id=216175
--- Comment #3 from nobutarounos...@gmail.com ---
Next, I add the Rx 6400 and change display output via Ryzen 3 PRO 4350G. The
run goes to reboot automatically. The journal is Attachment-B.
Finally, the run after the automatic reboot works. The j
https://bugzilla.kernel.org/show_bug.cgi?id=216175
nobutarounos...@gmail.com changed:
What|Removed |Added
Attachment #301279|attachment-C|Journal: attachment-C
https://bugzilla.kernel.org/show_bug.cgi?id=216175
nobutarounos...@gmail.com changed:
What|Removed |Added
Attachment #301278|Attachment-B|Journal: Attachment-B
https://bugzilla.kernel.org/show_bug.cgi?id=216175
nobutarounos...@gmail.com changed:
What|Removed |Added
Attachment #301277|Attachment-A|Journal: Attachment-A
https://bugzilla.kernel.org/show_bug.cgi?id=216175
--- Comment #2 from nobutarounos...@gmail.com ---
Created attachment 301279
--> https://bugzilla.kernel.org/attachment.cgi?id=301279&action=edit
attachment-C
--
You may reply to this email to add a comment.
You are receiving this mail because
https://bugzilla.kernel.org/show_bug.cgi?id=216175
--- Comment #1 from nobutarounos...@gmail.com ---
Created attachment 301278
--> https://bugzilla.kernel.org/attachment.cgi?id=301278&action=edit
Attachment-B
--
You may reply to this email to add a comment.
You are receiving this mail because
https://bugzilla.kernel.org/show_bug.cgi?id=216175
Bug ID: 216175
Summary: PowerColor Radeon Rx 6400 ITX does not work.
Product: Drivers
Version: 2.5
Kernel Version: 5.19-rc3
Hardware: AMD
OS: Linux
Tree: Main
Prevent that users set a font size which is bigger than the physical screen.
It's unlikely this may happen (because screens are usually much larger than the
fonts and each font char is limited to 32x32 pixels), but it may happen on
smaller screens/LCD displays.
Signed-off-by: Helge Deller
Reviewe
Prevent that drivers or the user sets the virtual screen resolution
smaller than the physical screen resolution. This is important, because
otherwise we may access memory outside of the graphics memory area.
Signed-off-by: Helge Deller
Reviewed-by: Daniel Vetter
Cc: sta...@vger.kernel.org # v5.
Use the fbcon_info_from_console() wrapper which was added to kernel
v5.19 with commit 409d6c95f9c6 ("fbcon: Introduce wrapper for console->fb_info
lookup").
Signed-off-by: Helge Deller
Reviewed-by: Daniel Vetter
---
drivers/video/fbdev/core/fbcon.c | 2 +-
1 file changed, 1 insertion(+), 1 del
We need to prevent that users configure a screen size which is smaller than the
currently selected font size. Otherwise rendering chars on the screen will
access memory outside the graphics memory region.
This patch adds a new function fbcon_modechange_possible() which
implements this check and wh
This series fixes possible out-of-bound memory accesses when users trigger
screen resolutions changes with invalid input parameters, e.g. reconfigures
screen which is smaller than the current font size, or if the virtual screen
size is smaller than the physical screen size.
v6:
- final version
- a
On Sun, Jun 26, 2022 at 10:56:15AM +0200, Helge Deller wrote:
> Use the fbcon_info_from_console() wrapper which was added to kernel
> v5.19 with commit 409d6c95f9c6 ("fbcon: Introduce wrapper for
> console->fb_info lookup").
>
> Signed-off-by: Helge Deller
Reviewed-by: Daniel Vetter
> ---
>
On Sun, Jun 26, 2022 at 10:56:14AM +0200, Helge Deller wrote:
> We need to prevent that users configure a screen size which is smaller than
> the
> currently selected font size. Otherwise rendering chars on the screen will
> access memory outside the graphics memory region.
>
> This patch adds a
On 6/26/22 10:49, Daniel Vetter wrote:
> On Sun, Jun 26, 2022 at 01:56:18AM +0200, Helge Deller wrote:
>> On 6/26/22 01:12, Helge Deller wrote:
>>> On 6/26/22 00:37, Daniel Vetter wrote:
On Sun, Jun 26, 2022 at 12:33:53AM +0200, Daniel Vetter wrote:
> On Sun, Jun 26, 2022 at 12:06:29AM +02
On 6/26/22 10:50, Daniel Vetter wrote:
> On Sun, Jun 26, 2022 at 01:27:02AM +0200, Helge Deller wrote:
>> We need to prevent that users configure a screen size which is smaller than
>> the
>> currently selected font size. Otherwise rendering chars on the screen will
>> access memory outside the gr
This series fixes possible out-of-bound memory accesses when users trigger
screen resolutions changes with invalid input parameters, e.g. reconfigures
screen which is smaller than the current font size, or if the virtual screen
size is smaller than the physical screen size.
Major change in this ve
Prevent that drivers or the user sets the virtual screen resolution
smaller than the physical screen resolution. This is important, because
otherwise we may access memory outside of the graphics memory area.
Signed-off-by: Helge Deller
Reviewed-by: Daniel Vetter
Cc: sta...@vger.kernel.org # v5.
Use the fbcon_info_from_console() wrapper which was added to kernel
v5.19 with commit 409d6c95f9c6 ("fbcon: Introduce wrapper for console->fb_info
lookup").
Signed-off-by: Helge Deller
---
drivers/video/fbdev/core/fbcon.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drive
Prevent that users set a font size which is bigger than the physical screen.
It's unlikely this may happen (because screens are usually much larger than the
fonts and each font char is limited to 32x32 pixels), but it may happen on
smaller screens/LCD displays.
Signed-off-by: Helge Deller
Reviewe
We need to prevent that users configure a screen size which is smaller than the
currently selected font size. Otherwise rendering chars on the screen will
access memory outside the graphics memory region.
This patch adds a new function fbcon_modechange_possible() which
implements this check and wh
On Sun, Jun 26, 2022 at 01:27:02AM +0200, Helge Deller wrote:
> We need to prevent that users configure a screen size which is smaller than
> the
> currently selected font size. Otherwise rendering chars on the screen will
> access memory outside the graphics memory region.
>
> This patch adds a
On Sun, Jun 26, 2022 at 01:56:18AM +0200, Helge Deller wrote:
> On 6/26/22 01:12, Helge Deller wrote:
> > On 6/26/22 00:37, Daniel Vetter wrote:
> >> On Sun, Jun 26, 2022 at 12:33:53AM +0200, Daniel Vetter wrote:
> >>> On Sun, Jun 26, 2022 at 12:06:29AM +0200, Helge Deller wrote:
> Enhance the
Hi Kevin,
On Sat, Jun 25, 2022 at 09:56:40PM -0500, Kevin Brace wrote:
> From: Kevin Brace
>
> This patch is a supplemental patch to delete VIA DRM so that the proposed
> OpenChrome DRM module can be compiled against drm-next-2022-06-03-1 tag of
> drm-next branch.
> Apply this patch first before
44 matches
Mail list logo
