Re: [PATCH v6 4/4] venus: firmware: register separate platform_device for... | linux-devicetree

[PATCH v6 0/4] Venus updates - PIL · Vikash Garodia <hidden> · 2018-08-23
[PATCH v6 1/4] venus: firmware: add routine to reset ARM9 · Vikash Garodia <hidden> · 2018-08-23
Re: [PATCH v6 1/4] venus: firmware: add routine to reset ARM9 · Alexandre Courbot <hidden> · 2018-08-24
Re: [PATCH v6 1/4] venus: firmware: add routine to reset ARM9 · Stanimir Varbanov <hidden> · 2018-08-24
Re: [PATCH v6 1/4] venus: firmware: add routine to reset ARM9 · Vikash Garodia <hidden> · 2018-08-24
Re: [PATCH v6 1/4] venus: firmware: add routine to reset ARM9 · Alexandre Courbot <hidden> · 2018-08-27
Re: [PATCH v6 1/4] venus: firmware: add routine to reset ARM9 · Stanimir Varbanov <hidden> · 2018-08-27
Re: [PATCH v6 1/4] venus: firmware: add routine to reset ARM9 · Alexandre Courbot <hidden> · 2018-08-28
[PATCH v6 2/4] venus: firmware: move load firmware in a separate function · Vikash Garodia <hidden> · 2018-08-23
Re: [PATCH v6 2/4] venus: firmware: move load firmware in a separate function · Alexandre Courbot <hidden> · 2018-08-24
Re: [PATCH v6 2/4] venus: firmware: move load firmware in a separate function · Stanimir Varbanov <hidden> · 2018-08-24
Re: [PATCH v6 2/4] venus: firmware: move load firmware in a separate function · Alexandre Courbot <hidden> · 2018-08-27
[PATCH v6 3/4] venus: firmware: add no TZ boot and shutdown routine · Vikash Garodia <hidden> · 2018-08-23
Re: [PATCH v6 3/4] venus: firmware: add no TZ boot and shutdown routine · Alexandre Courbot <hidden> · 2018-08-24
Re: [PATCH v6 3/4] venus: firmware: add no TZ boot and shutdown routine · Vikash Garodia <hidden> · 2018-08-24
Re: [PATCH v6 3/4] venus: firmware: add no TZ boot and shutdown routine · Alexandre Courbot <hidden> · 2018-08-27
Re: [PATCH v6 3/4] venus: firmware: add no TZ boot and shutdown routine · Vikash Garodia <hidden> · 2018-08-27
Re: [PATCH v6 3/4] venus: firmware: add no TZ boot and shutdown routine · Alexandre Courbot <hidden> · 2018-08-28
[PATCH v6 4/4] venus: firmware: register separate platform_device for firmware loader · Vikash Garodia <hidden> · 2018-08-23
Re: [PATCH v6 4/4] venus: firmware: register separate platform_device for firmware loader · Stephen Boyd <hidden> · 2018-08-24
Re: [PATCH v6 4/4] venus: firmware: register separate platform_device for firmware loader · Alexandre Courbot <hidden> · 2018-08-24
Re: [PATCH v6 4/4] venus: firmware: register separate platform_device for firmware loader · Rob Herring <robh@kernel.org> · 2018-08-28
Re: [PATCH v6 4/4] venus: firmware: register separate platform_device for firmware loader · kbuild test robot <hidden> · 2018-08-30
Re: [PATCH v6 0/4] Venus updates - PIL · Alexandre Courbot <hidden> · 2018-08-24

Re: [PATCH v6 4/4] venus: firmware: register separate platform_device for firmware loader

From: Stephen Boyd <hidden>
Date: 2018-08-24 06:45:20
Also in: linux-arm-msm, linux-media, lkml

Quoting Vikash Garodia (2018-08-23 07:28:48)

From: Stanimir Varbanov <redacted>

This registers a firmware platform_device and associate it with
video-firmware DT subnode. Then calls dma configure to initialize
dma and iommu.

Yes, but why? Commit text isn't supposed to say what is obvious from the
code.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help