Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Please enable FB_SSD1307 in default configs #969

Closed
kad opened this issue May 18, 2015 · 2 comments
Closed

Please enable FB_SSD1307 in default configs #969

kad opened this issue May 18, 2015 · 2 comments

Comments

@kad
Copy link

kad commented May 18, 2015

Please enable option FB_SSD1307 in default configs.
This would allow to use very widely available small i2c connected screens to work without big effort.
popcornmix added a commit to raspberrypi/firmware that referenced this issue May 18, 2015
@popcornmix
kernel: Adding bcm2835-sdhost driver, and an overlay to enable it
c0bb9f7 
See: #397

kernel: bcm2835-sdhost: Adding overclocking option
kernel: bcm2835-mmc: Adding overclocking option
See: http://forum.kodi.tv/showthread.php?tid=224025&pid=2005396#pid2005396

kernel: config: Add CONFIG_CIFS_UPCALL
See: raspberrypi/linux#968

kernel: config: Add CONFIG_FB_SSD1307=m
See: raspberrypi/linux#969

firmware: di_adv: Fix memory leak of converted buffers
See: #429

firmware: arm_display: Fix initialisation of framebuffer struct when framebuffer base is passed in

firmware: hdmi: Tweak hdmi_mai_thresh for 192kHz audio
See: https://discourse.osmc.tv/t/rp2-multichannel-flac-playback/2627/28

firmware: vcsm: Update to header from kernel side
popcornmix added a commit to Hexxeh/rpi-firmware that referenced this issue May 18, 2015
@popcornmix
kernel: Adding bcm2835-sdhost driver, and an overlay to enable it
5656958 
See: raspberrypi/firmware#397

kernel: bcm2835-sdhost: Adding overclocking option
kernel: bcm2835-mmc: Adding overclocking option
See: http://forum.kodi.tv/showthread.php?tid=224025&pid=2005396#pid2005396

kernel: config: Add CONFIG_CIFS_UPCALL
See: raspberrypi/linux#968

kernel: config: Add CONFIG_FB_SSD1307=m
See: raspberrypi/linux#969

firmware: di_adv: Fix memory leak of converted buffers
See: raspberrypi/firmware#429

firmware: arm_display: Fix initialisation of framebuffer struct when framebuffer base is passed in

firmware: hdmi: Tweak hdmi_mai_thresh for 192kHz audio
See: https://discourse.osmc.tv/t/rp2-multichannel-flac-playback/2627/28

firmware: vcsm: Update to header from kernel side
@popcornmix
Copy link
Collaborator

Added in latest rpi-update firmware. Please test.

@kad
Copy link
Author

kad commented May 19, 2015

Thanks. Module appeared and can be loaded. Device detected but no framebuffer device node created for my type of LCD, but that's separate issue that needed to be looked at driver itself.

@kad kad closed this as completed May 19, 2015
neuschaefer pushed a commit to neuschaefer/raspi-binary-firmware that referenced this issue Feb 27, 2017
@popcornmix
kernel: Adding bcm2835-sdhost driver, and an overlay to enable it
6763988 
See: raspberrypi#397

kernel: bcm2835-sdhost: Adding overclocking option
kernel: bcm2835-mmc: Adding overclocking option
See: http://forum.kodi.tv/showthread.php?tid=224025&pid=2005396#pid2005396

kernel: config: Add CONFIG_CIFS_UPCALL
See: raspberrypi/linux#968

kernel: config: Add CONFIG_FB_SSD1307=m
See: raspberrypi/linux#969

firmware: di_adv: Fix memory leak of converted buffers
See: raspberrypi#429

firmware: arm_display: Fix initialisation of framebuffer struct when framebuffer base is passed in

firmware: hdmi: Tweak hdmi_mai_thresh for 192kHz audio
See: https://discourse.osmc.tv/t/rp2-multichannel-flac-playback/2627/28

firmware: vcsm: Update to header from kernel side
popcornmix pushed a commit that referenced this issue Oct 19, 2021
@Srinivas-Kandagatla @gregkh
misc: fastrpc: Add missing lock before accessing find_vma()
f9a470d 
fastrpc driver is using find_vma() without any protection, as a
result we see below warning due to recent patch 5b78ed2
("mm/pagemap: add mmap_assert_locked() annotations to find_vma*()")
which added mmap_assert_locked() in find_vma() function.

This bug went un-noticed in previous versions. Fix this issue by adding
required protection while calling find_vma().

CPU: 0 PID: 209746 Comm: benchmark_model Not tainted 5.15.0-rc2-00445-ge14fe2bf817a-dirty #969
Hardware name: Qualcomm Technologies, Inc. Robotics RB5 (DT)
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : find_vma+0x64/0xd0
lr : find_vma+0x60/0xd0
sp : ffff8000158ebc40
...

Call trace:
 find_vma+0x64/0xd0
 fastrpc_internal_invoke+0x570/0xda8
 fastrpc_device_ioctl+0x3e0/0x928
 __arm64_sys_ioctl+0xac/0xf0
 invoke_syscall+0x44/0x100
 el0_svc_common.constprop.3+0x70/0xf8
 do_el0_svc+0x24/0x88
 el0_svc+0x3c/0x138
 el0t_64_sync_handler+0x90/0xb8
 el0t_64_sync+0x180/0x184

Fixes: 80f3afd ("misc: fastrpc: consider address offset before sending to DSP")
Cc: stable@vger.kernel.org
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Link: https://lore.kernel.org/r/20210922154326.8927-1-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
popcornmix pushed a commit that referenced this issue Oct 22, 2021
@Srinivas-Kandagatla @gregkh
misc: fastrpc: Add missing lock before accessing find_vma()
d22592f 
commit f9a470d upstream.

fastrpc driver is using find_vma() without any protection, as a
result we see below warning due to recent patch 5b78ed2
("mm/pagemap: add mmap_assert_locked() annotations to find_vma*()")
which added mmap_assert_locked() in find_vma() function.

This bug went un-noticed in previous versions. Fix this issue by adding
required protection while calling find_vma().

CPU: 0 PID: 209746 Comm: benchmark_model Not tainted 5.15.0-rc2-00445-ge14fe2bf817a-dirty #969
Hardware name: Qualcomm Technologies, Inc. Robotics RB5 (DT)
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : find_vma+0x64/0xd0
lr : find_vma+0x60/0xd0
sp : ffff8000158ebc40
...

Call trace:
 find_vma+0x64/0xd0
 fastrpc_internal_invoke+0x570/0xda8
 fastrpc_device_ioctl+0x3e0/0x928
 __arm64_sys_ioctl+0xac/0xf0
 invoke_syscall+0x44/0x100
 el0_svc_common.constprop.3+0x70/0xf8
 do_el0_svc+0x24/0x88
 el0_svc+0x3c/0x138
 el0t_64_sync_handler+0x90/0xb8
 el0t_64_sync+0x180/0x184

Fixes: 80f3afd ("misc: fastrpc: consider address offset before sending to DSP")
Cc: stable@vger.kernel.org
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Link: https://lore.kernel.org/r/20210922154326.8927-1-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
popcornmix pushed a commit that referenced this issue Oct 25, 2021
@Srinivas-Kandagatla @gregkh
misc: fastrpc: Add missing lock before accessing find_vma()
86e3ad8 
commit f9a470d upstream.

fastrpc driver is using find_vma() without any protection, as a
result we see below warning due to recent patch 5b78ed2
("mm/pagemap: add mmap_assert_locked() annotations to find_vma*()")
which added mmap_assert_locked() in find_vma() function.

This bug went un-noticed in previous versions. Fix this issue by adding
required protection while calling find_vma().

CPU: 0 PID: 209746 Comm: benchmark_model Not tainted 5.15.0-rc2-00445-ge14fe2bf817a-dirty #969
Hardware name: Qualcomm Technologies, Inc. Robotics RB5 (DT)
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : find_vma+0x64/0xd0
lr : find_vma+0x60/0xd0
sp : ffff8000158ebc40
...

Call trace:
 find_vma+0x64/0xd0
 fastrpc_internal_invoke+0x570/0xda8
 fastrpc_device_ioctl+0x3e0/0x928
 __arm64_sys_ioctl+0xac/0xf0
 invoke_syscall+0x44/0x100
 el0_svc_common.constprop.3+0x70/0xf8
 do_el0_svc+0x24/0x88
 el0_svc+0x3c/0x138
 el0t_64_sync_handler+0x90/0xb8
 el0t_64_sync+0x180/0x184

Fixes: 80f3afd ("misc: fastrpc: consider address offset before sending to DSP")
Cc: stable@vger.kernel.org
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Link: https://lore.kernel.org/r/20210922154326.8927-1-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kad @popcornmix