Hi bridge maintainers!
On 06/09/2023 09:50, Tomi Valkeinen wrote:
This series contains various fixes and cleanups for TC358768. The target
of this work is to get TC358768 working on Toradex's AM62 based board,
which has the following display pipeline:
AM62 DPI -> TC358768 -> LT8912B -> HDMI
On 12.09.2023 13:44, manikanda...@microchip.com wrote:
> On 09/09/23 9:50 pm, claudiu beznea wrote:
>> [You don't often get email from claudiu.bez...@tuxon.dev. Learn why this is
>> important at https://aka.ms/LearnAboutSenderIdentification ]
>>
>> EXTERNAL EMAIL: Do not click links or open
* H. Nikolaus Schaller [230916 12:50]:
> Hi Tomi and Tony,
>
> > Am 13.09.2023 um 13:59 schrieb Tomi Valkeinen
> > :
> >
> > On 12/04/2023 10:39, Tony Lindgren wrote:
> >> We may not have dsi->dsidev initialized during probe, and that can
> >> lead into various dsi related warnings as
Update the max GSC-fw response time to match updated internal
fw specs. Because this response time is an SLA on the firmware,
not inclusive of i915->GuC->HW handoff latency, when submitting
requests to the GSC fw via intel_gsc_uc_heci_cmd_submit helpers,
start the count after the request hits the
On Meteorlake onwards, HW specs require that all user contexts that
run on render or compute engines and require PXP must enforce
run-alone bit in lrc. Add this enforcement for protected contexts.
Signed-off-by: Alan Previn
Reviewed-by: Vivaik Balasubrawmanian
---
Update the GSC-fw input/output HECI packet size to match
updated internal fw specs.
Signed-off-by: Alan Previn
Reviewed-by: Vivaik Balasubrawmanian
---
drivers/gpu/drm/i915/pxp/intel_pxp_cmd_interface_43.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
For MTL, update the GSC-HECI packet size and the max firmware
response timeout to match internal fw specs. Enforce setting
run-alone bit in LRC for protected contexts.
Changes from prio revs:
v6: - fix build error with PXP config (Alan)
v5: - PAGE_ALIGN typo fix (Alan).
- Use macro
On Sat, 2023-09-16 at 10:25 +0800, lkp wrote:
> Hi Alan,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on cf1e91e884bb1113c653e654e9de1754fc1d4488]
>
> aAll errors (new ones prefixed by >>):
>
>
alan:snip
alan: missed building with PXP config after that
5.15-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 4cfe75f0f14f044dae66ad0e6eea812d038465d9 upstream.
Fix the test for the AST2200 in the DRAM initialization. The value
in ast->chip has to be compared against an enum
5.15-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 992bdddaabfba19bdc77c1c7a4977b2aa41ec891 upstream.
Struct bd6107_platform_data refers to a platform device within
the Linux device hierarchy. The test in
5.15-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 7b91d017f77c1bda56f27c2f4bbb70de7c6eca08 upstream.
Struct gpio_backlight_platform_data refers to a platform device within
the Linux device hierarchy. The test in
5.15-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 1ca8819320fd84e7d95b04e7668efc5f9fe9fa5c upstream.
Struct lv5207lp_platform_data refers to a platform device within
the Linux device hierarchy. The test in
6.1-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 4cfe75f0f14f044dae66ad0e6eea812d038465d9 upstream.
Fix the test for the AST2200 in the DRAM initialization. The value
in ast->chip has to be compared against an enum
6.5-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 4cfe75f0f14f044dae66ad0e6eea812d038465d9 upstream.
Fix the test for the AST2200 in the DRAM initialization. The value
in ast->chip has to be compared against an enum
5.10-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 4cfe75f0f14f044dae66ad0e6eea812d038465d9 upstream.
Fix the test for the AST2200 in the DRAM initialization. The value
in ast->chip has to be compared against an enum
5.10-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 1ca8819320fd84e7d95b04e7668efc5f9fe9fa5c upstream.
Struct lv5207lp_platform_data refers to a platform device within
the Linux device hierarchy. The test in
5.10-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 7b91d017f77c1bda56f27c2f4bbb70de7c6eca08 upstream.
Struct gpio_backlight_platform_data refers to a platform device within
the Linux device hierarchy. The test in
5.10-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 992bdddaabfba19bdc77c1c7a4977b2aa41ec891 upstream.
Struct bd6107_platform_data refers to a platform device within
the Linux device hierarchy. The test in
Am Wed, 13 Sep 2023 15:58:11 +0300
schrieb Tomi Valkeinen :
> On 13/09/2023 15:48, Tony Lindgren wrote:
> > * Tomi Valkeinen [230913 12:11]:
> >> I'm somewhat sure that the upstream driver used to work on omap4
> >> sdp, which has two DSI panels. But I can't even remember what
> >> omap4
On Fri, Sep 01, 2023 at 11:22:40AM -0600, Jeffrey Hugo wrote:
> A BO for a QAIC device has two states -
> 1. Allocated
> 2. Sliced
>
> A BO can be allocated at any time, and is initialized in the allocated state.
> A BO can transition to the sliced state via ATTACH_SLICE_BO. This prepares
> the
On Fri, Sep 01, 2023 at 11:22:47AM -0600, Jeffrey Hugo wrote:
> From: Pranjal Ramajor Asha Kanojiya
>
> Once a BO is attached with slicing configuration that BO can only be used
> for that particular setting. With this new feature user can detach slicing
> configuration off an already sliced BO
On Fri, Sep 01, 2023 at 11:22:46AM -0600, Jeffrey Hugo wrote:
> From: Pranjal Ramajor Asha Kanojiya
>
> This makes sure that we have a single place to initialize and
> re-initialize BO.
>
> Use this new API to cleanup release_dbc()
>
> We will need this for next patch to detach slicing to a
Hello,
syzbot found the following issue on:
HEAD commit:e143016b56ec Add linux-next specific files for 20230913
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=164c5ac7a8
kernel config: https://syzkaller.appspot.com/x/.config?x=76ee1517f109f01a
27 matches
Mail list logo
