Hi,
On Thu, Feb 22, 2018 at 7:42 PM, Tomasz Figa wrote:
> On Thu, Feb 22, 2018 at 10:45 PM, Robin Murphy wrote:
>> [sorry, I had intended to reply sooner but clearly forgot]
>>
>>
>> On 16/02/18 00:13, Tomasz Figa wrote:
>>>
>>> On Fri, Feb 16, 2018 at 2:14 AM, Robin Murphy
>>> wrote:
On Thu, Feb 22, 2018 at 10:45 PM, Robin Murphy wrote:
> [sorry, I had intended to reply sooner but clearly forgot]
>
>
> On 16/02/18 00:13, Tomasz Figa wrote:
>>
>> On Fri, Feb 16, 2018 at 2:14 AM, Robin Murphy
>> wrote:
>>>
>>> On 15/02/18 04:17, Tomasz Figa wrote:
>>> [...]
>
>
> Co
[sorry, I had intended to reply sooner but clearly forgot]
On 16/02/18 00:13, Tomasz Figa wrote:
On Fri, Feb 16, 2018 at 2:14 AM, Robin Murphy wrote:
On 15/02/18 04:17, Tomasz Figa wrote:
[...]
Could you elaborate on what kind of locking you are concerned about?
As I explained before, the no
On Thu, Feb 22, 2018 at 3:13 AM, Tomasz Figa wrote:
> On Fri, Feb 16, 2018 at 9:13 AM, Tomasz Figa wrote:
>> On Fri, Feb 16, 2018 at 2:14 AM, Robin Murphy wrote:
>>> On 15/02/18 04:17, Tomasz Figa wrote:
>>> [...]
>
> Could you elaborate on what kind of locking you are concerned about?
>
On Fri, Feb 16, 2018 at 9:13 AM, Tomasz Figa wrote:
> On Fri, Feb 16, 2018 at 2:14 AM, Robin Murphy wrote:
>> On 15/02/18 04:17, Tomasz Figa wrote:
>> [...]
Could you elaborate on what kind of locking you are concerned about?
As I explained before, the normally happening fast path
On Fri, Feb 16, 2018 at 2:14 AM, Robin Murphy wrote:
> On 15/02/18 04:17, Tomasz Figa wrote:
> [...]
>>>
>>> Could you elaborate on what kind of locking you are concerned about?
>>> As I explained before, the normally happening fast path would lock
>>> dev->power_lock only for the brief moment of
On 15/02/18 04:17, Tomasz Figa wrote:
[...]
Could you elaborate on what kind of locking you are concerned about?
As I explained before, the normally happening fast path would lock
dev->power_lock only for the brief moment of incrementing the runtime
PM usage counter.
My bad, that's not even it.
On Wed, Feb 14, 2018 at 11:09 PM, Tomasz Figa wrote:
> On Thu, Feb 15, 2018 at 1:12 AM, Rob Clark wrote:
>> On Wed, Feb 14, 2018 at 10:48 AM, Jordan Crouse
>> wrote:
>>> On Wed, Feb 14, 2018 at 12:31:29PM +0900, Tomasz Figa wrote:
- When submitting commands to the GPU, the GPU driver
On Thu, Feb 15, 2018 at 12:17 PM, Tomasz Figa wrote:
> On Thu, Feb 15, 2018 at 1:03 AM, Robin Murphy wrote:
>> On 14/02/18 10:33, Vivek Gautam wrote:
>>>
>>> On Wed, Feb 14, 2018 at 2:46 PM, Tomasz Figa wrote:
>>>
>>> Adding Jordan to this thread as well.
>>>
On Wed, Feb 14, 2018 at 6:13 PM
On Thu, Feb 15, 2018 at 1:12 AM, Rob Clark wrote:
> On Wed, Feb 14, 2018 at 10:48 AM, Jordan Crouse
> wrote:
>> On Wed, Feb 14, 2018 at 12:31:29PM +0900, Tomasz Figa wrote:
>>>
>>> - When submitting commands to the GPU, the GPU driver will
>>> pm_runtime_get_sync() on the GPU device, which will
On Thu, Feb 15, 2018 at 1:03 AM, Robin Murphy wrote:
> On 14/02/18 10:33, Vivek Gautam wrote:
>>
>> On Wed, Feb 14, 2018 at 2:46 PM, Tomasz Figa wrote:
>>
>> Adding Jordan to this thread as well.
>>
>>> On Wed, Feb 14, 2018 at 6:13 PM, Vivek Gautam
>>> wrote:
Hi Tomasz,
On We
On Wed, Feb 14, 2018 at 10:48 AM, Jordan Crouse wrote:
> On Wed, Feb 14, 2018 at 12:31:29PM +0900, Tomasz Figa wrote:
>>
>> - When submitting commands to the GPU, the GPU driver will
>> pm_runtime_get_sync() on the GPU device, which will automatically do
>> the same on all the linked suppliers, wh
On 14/02/18 10:33, Vivek Gautam wrote:
On Wed, Feb 14, 2018 at 2:46 PM, Tomasz Figa wrote:
Adding Jordan to this thread as well.
On Wed, Feb 14, 2018 at 6:13 PM, Vivek Gautam
wrote:
Hi Tomasz,
On Wed, Feb 14, 2018 at 11:08 AM, Tomasz Figa wrote:
On Wed, Feb 14, 2018 at 1:17 PM, Vivek Gau
On Wed, Feb 14, 2018 at 12:31:29PM +0900, Tomasz Figa wrote:
> Hi Jordan,
>
> On Wed, Feb 14, 2018 at 1:42 AM, Jordan Crouse wrote:
> > On Tue, Feb 13, 2018 at 06:10:38PM +0900, Tomasz Figa wrote:
> >> Hi Vivek,
> >>
> >> Thanks for the patch. Please see my comments inline.
> >>
> >> On Wed, Feb
On Wed, Feb 14, 2018 at 2:46 PM, Tomasz Figa wrote:
Adding Jordan to this thread as well.
> On Wed, Feb 14, 2018 at 6:13 PM, Vivek Gautam
> wrote:
>> Hi Tomasz,
>>
>> On Wed, Feb 14, 2018 at 11:08 AM, Tomasz Figa wrote:
>>> On Wed, Feb 14, 2018 at 1:17 PM, Vivek Gautam
>>> wrote:
Hi Toma
On Wed, Feb 14, 2018 at 6:13 PM, Vivek Gautam
wrote:
> Hi Tomasz,
>
> On Wed, Feb 14, 2018 at 11:08 AM, Tomasz Figa wrote:
>> On Wed, Feb 14, 2018 at 1:17 PM, Vivek Gautam
>> wrote:
>>> Hi Tomasz,
>>>
>>> On Wed, Feb 14, 2018 at 8:31 AM, Tomasz Figa wrote:
On Wed, Feb 14, 2018 at 11:13 AM,
Hi Tomasz,
On Wed, Feb 14, 2018 at 11:08 AM, Tomasz Figa wrote:
> On Wed, Feb 14, 2018 at 1:17 PM, Vivek Gautam
> wrote:
>> Hi Tomasz,
>>
>> On Wed, Feb 14, 2018 at 8:31 AM, Tomasz Figa wrote:
>>> On Wed, Feb 14, 2018 at 11:13 AM, Rob Clark wrote:
On Tue, Feb 13, 2018 at 8:59 PM, Tomasz F
On Wed, Feb 14, 2018 at 1:17 PM, Vivek Gautam
wrote:
> Hi Tomasz,
>
> On Wed, Feb 14, 2018 at 8:31 AM, Tomasz Figa wrote:
>> On Wed, Feb 14, 2018 at 11:13 AM, Rob Clark wrote:
>>> On Tue, Feb 13, 2018 at 8:59 PM, Tomasz Figa wrote:
On Wed, Feb 14, 2018 at 3:03 AM, Rob Clark wrote:
> O
Hi Tomasz,
On Wed, Feb 14, 2018 at 8:31 AM, Tomasz Figa wrote:
> On Wed, Feb 14, 2018 at 11:13 AM, Rob Clark wrote:
>> On Tue, Feb 13, 2018 at 8:59 PM, Tomasz Figa wrote:
>>> On Wed, Feb 14, 2018 at 3:03 AM, Rob Clark wrote:
On Tue, Feb 13, 2018 at 4:10 AM, Tomasz Figa wrote:
> Hi Vi
Hi Jordan,
On Wed, Feb 14, 2018 at 1:42 AM, Jordan Crouse wrote:
> On Tue, Feb 13, 2018 at 06:10:38PM +0900, Tomasz Figa wrote:
>> Hi Vivek,
>>
>> Thanks for the patch. Please see my comments inline.
>>
>> On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
>> wrote:
>> > While handling the concerned i
On Wed, Feb 14, 2018 at 11:13 AM, Rob Clark wrote:
> On Tue, Feb 13, 2018 at 8:59 PM, Tomasz Figa wrote:
>> On Wed, Feb 14, 2018 at 3:03 AM, Rob Clark wrote:
>>> On Tue, Feb 13, 2018 at 4:10 AM, Tomasz Figa wrote:
Hi Vivek,
Thanks for the patch. Please see my comments inline.
>>>
On Tue, Feb 13, 2018 at 8:59 PM, Tomasz Figa wrote:
> On Wed, Feb 14, 2018 at 3:03 AM, Rob Clark wrote:
>> On Tue, Feb 13, 2018 at 4:10 AM, Tomasz Figa wrote:
>>> Hi Vivek,
>>>
>>> Thanks for the patch. Please see my comments inline.
>>>
>>> On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
>>> wrot
On Wed, Feb 14, 2018 at 3:03 AM, Rob Clark wrote:
> On Tue, Feb 13, 2018 at 4:10 AM, Tomasz Figa wrote:
>> Hi Vivek,
>>
>> Thanks for the patch. Please see my comments inline.
>>
>> On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
>> wrote:
>>> While handling the concerned iommu, there should not be
On Tue, Feb 13, 2018 at 4:10 AM, Tomasz Figa wrote:
> Hi Vivek,
>
> Thanks for the patch. Please see my comments inline.
>
> On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
> wrote:
>> While handling the concerned iommu, there should not be a
>> need to power control the drm devices from iommu inter
On Tue, Feb 13, 2018 at 06:10:38PM +0900, Tomasz Figa wrote:
> Hi Vivek,
>
> Thanks for the patch. Please see my comments inline.
>
> On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
> wrote:
> > While handling the concerned iommu, there should not be a
> > need to power control the drm devices from
Hi Vivek,
Thanks for the patch. Please see my comments inline.
On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
wrote:
> While handling the concerned iommu, there should not be a
> need to power control the drm devices from iommu interface.
> If these drm devices need to be powered around this time,
While handling the concerned iommu, there should not be a
need to power control the drm devices from iommu interface.
If these drm devices need to be powered around this time,
the respective drivers should take care of this.
Replace the pm_runtime_get/put_sync() with
pm_runtime_get/put_suppliers()
27 matches
Mail list logo