[lng-odp] drv api in api-next
In api-next we have some drv apis which is a copy of linux-generic but with drv prefix. I'm thinking what to do with them for Tiger Moth. Or merge them or merge and revert. For now we do not use that api. Maxim.
Re: [lng-odp] drv api in api-next
On 30/10/17 19:43, Maxim Uvarov wrote: > In api-next we have some drv apis which is a copy of linux-generic but > with drv prefix. I'm thinking what to do with them for Tiger Moth. Or > merge them or merge and revert. For now we do not use that api. I'd say, let's revert that for now. Implementation in master is far from being complete. We can reintroduce them later. -- With best wishes Dmitry
Re: [lng-odp] drv api in api-next
We use most of it for mdev implementation. Ideally we'll clean that up once we decide which path to follow on driver(vfio-pci or mediated devices) On 31 October 2017 at 11:05, Dmitry Eremin-Solenikov < dmitry.ereminsoleni...@linaro.org> wrote: > On 30/10/17 19:43, Maxim Uvarov wrote: > > In api-next we have some drv apis which is a copy of linux-generic but > > with drv prefix. I'm thinking what to do with them for Tiger Moth. Or > > merge them or merge and revert. For now we do not use that api. > > I'd say, let's revert that for now. Implementation in master is far from > being complete. We can reintroduce them later. > > -- > With best wishes > Dmitry >
Re: [lng-odp] drv api in api-next
But they are APIs, even though they were copied from Linux-generic. I am thinking the discussion has already happened on why they should be in API directory. Is there any reason to revert and restart the discussion? On 30 October 2017 at 11:43, Maxim Uvarov wrote: > In api-next we have some drv apis which is a copy of linux-generic but > with drv prefix. I'm thinking what to do with them for Tiger Moth. Or > merge them or merge and revert. For now we do not use that api. > > Maxim.
Re: [lng-odp] drv api in api-next
On 31/10/17 22:21, Honnappa Nagarahalli wrote: > But they are APIs, even though they were copied from Linux-generic. I > am thinking the discussion has already happened on why they should be > in API directory. Is there any reason to revert and restart the > discussion? They are used for 2.0, but are unused in linux-generic (at least in TigerMoth). I'd vote to remove incomplete drv_* headers from TM. They will come back through 2.0. > On 30 October 2017 at 11:43, Maxim Uvarov wrote: >> In api-next we have some drv apis which is a copy of linux-generic but >> with drv prefix. I'm thinking what to do with them for Tiger Moth. Or >> merge them or merge and revert. For now we do not use that api. >> >> Maxim. -- With best wishes Dmitry
Re: [lng-odp] drv api in api-next
On 1 November 2017 at 03:17, Dmitry Eremin-Solenikov wrote: > On 31/10/17 22:21, Honnappa Nagarahalli wrote: >> But they are APIs, even though they were copied from Linux-generic. I >> am thinking the discussion has already happened on why they should be >> in API directory. Is there any reason to revert and restart the >> discussion? > > They are used for 2.0, but are unused in linux-generic (at least in > TigerMoth). I'd vote to remove incomplete drv_* headers from TM. They > will come back through 2.0. > The changes in api-next are merged to 2.0 branch. If we remove them in master/api-next, the automatic merge will remove them from 2.0 as well. >> On 30 October 2017 at 11:43, Maxim Uvarov wrote: >>> In api-next we have some drv apis which is a copy of linux-generic but >>> with drv prefix. I'm thinking what to do with them for Tiger Moth. Or >>> merge them or merge and revert. For now we do not use that api. >>> >>> Maxim. > > > -- > With best wishes > Dmitry
Re: [lng-odp] drv api in api-next
as discussed today we will drop drv from master and api-next branch. 2.0 branch will need to revert this deletion commit. So that drv will be in 2.0 before it's will be ready to merge to master. Maxim.
