2012-10-03 15:00:34

by Matt Porter

[permalink] [raw]
Subject: Re: [PATCH v2 0/7] uio_pruss cleanup and platform support

On Fri, Sep 28, 2012 at 03:37:45PM -0400, Matt Porter wrote:
> Changes since v1:
> - Replaced uio_pruss private SRAM API use with genalloc
> - Added DA850 platform device and clock support
> - Added DA850 L3 RAM gen_pool support
> - Split out DT binding
>
> This series enables uio_pruss on both DA850 and AM33xx. The driver
> previously was not enabled by any platform and the private SRAM API
> was accessing an invalid SRAM bank for use on DA850. For AM33xx,
> DT, pinctrl, and runtime PM support are added since AM33xx only
> boots via DT.

I'm dropping AM33xx/OMAP support from v3 for this series since the
focus has turned to fixing Davinci SRAM to provide genalloc support
and the associated use of that in the driver.

I'll have a separate series with AM33xx support since dealing cleanly
with external resets on OMAP is a bigger issue.

-Matt


2012-10-05 06:42:11

by Hebbar, Gururaja

[permalink] [raw]
Subject: RE: [PATCH v2 0/7] uio_pruss cleanup and platform support

Matt,

On Wed, Oct 03, 2012 at 20:30:58, Porter, Matt wrote:
> On Fri, Sep 28, 2012 at 03:37:45PM -0400, Matt Porter wrote:
> > Changes since v1:
> > - Replaced uio_pruss private SRAM API use with genalloc
> > - Added DA850 platform device and clock support
> > - Added DA850 L3 RAM gen_pool support
> > - Split out DT binding
> >
> > This series enables uio_pruss on both DA850 and AM33xx. The driver
> > previously was not enabled by any platform and the private SRAM API
> > was accessing an invalid SRAM bank for use on DA850. For AM33xx,
> > DT, pinctrl, and runtime PM support are added since AM33xx only
> > boots via DT.
>
> I'm dropping AM33xx/OMAP support from v3 for this series

Just for my clarification, I believe you will be taking up AM33xx/OMAP
SRAM support later once you have completed supporting DaVinci. Right?

> since the
> focus has turned to fixing Davinci SRAM to provide genalloc support
> and the associated use of that in the driver.
>
> I'll have a separate series with AM33xx support since dealing cleanly
> with external resets on OMAP is a bigger issue.
>
> -Matt
> _______________________________________________
> Davinci-linux-open-source mailing list
> [email protected]
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>


Regards,
Gururaja

2012-10-05 21:27:54

by Matt Porter

[permalink] [raw]
Subject: Re: [PATCH v2 0/7] uio_pruss cleanup and platform support

On Fri, Oct 05, 2012 at 04:43:56AM +0000, Hebbar, Gururaja wrote:
> Matt,
>
> On Wed, Oct 03, 2012 at 20:30:58, Porter, Matt wrote:
> > On Fri, Sep 28, 2012 at 03:37:45PM -0400, Matt Porter wrote:
> > > Changes since v1:
> > > - Replaced uio_pruss private SRAM API use with genalloc
> > > - Added DA850 platform device and clock support
> > > - Added DA850 L3 RAM gen_pool support
> > > - Split out DT binding
> > >
> > > This series enables uio_pruss on both DA850 and AM33xx. The driver
> > > previously was not enabled by any platform and the private SRAM API
> > > was accessing an invalid SRAM bank for use on DA850. For AM33xx,
> > > DT, pinctrl, and runtime PM support are added since AM33xx only
> > > boots via DT.
> >
> > I'm dropping AM33xx/OMAP support from v3 for this series
>
> Just for my clarification, I believe you will be taking up AM33xx/OMAP
> SRAM support later once you have completed supporting DaVinci. Right?

There's no SRAM support for uio_pruss to be handled for AM33xx, but I
will be posting a separate series with the DT portion and some alternate
hard reset handling implementation. I find the private OMAP reset api to
be very ugly but we might have to go with that for now. I didn't want
the OMAP hard reset portion to hold up the more important part of this
cleanup.

-Matt

> > since the
> > focus has turned to fixing Davinci SRAM to provide genalloc support
> > and the associated use of that in the driver.
> >
> > I'll have a separate series with AM33xx support since dealing cleanly
> > with external resets on OMAP is a bigger issue.
> >
> > -Matt
> > _______________________________________________
> > Davinci-linux-open-source mailing list
> > [email protected]
> > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> >
>
>
> Regards,
> Gururaja
> _______________________________________________
> Davinci-linux-open-source mailing list
> [email protected]
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

2012-10-08 05:14:11

by Hebbar, Gururaja

[permalink] [raw]
Subject: RE: [PATCH v2 0/7] uio_pruss cleanup and platform support

On Sat, Oct 06, 2012 at 02:58:26, Porter, Matt wrote:
> On Fri, Oct 05, 2012 at 04:43:56AM +0000, Hebbar, Gururaja wrote:
> > Matt,
> >
> > On Wed, Oct 03, 2012 at 20:30:58, Porter, Matt wrote:
> > > On Fri, Sep 28, 2012 at 03:37:45PM -0400, Matt Porter wrote:
> > > > Changes since v1:
> > > > - Replaced uio_pruss private SRAM API use with genalloc
> > > > - Added DA850 platform device and clock support
> > > > - Added DA850 L3 RAM gen_pool support
> > > > - Split out DT binding
> > > >
> > > > This series enables uio_pruss on both DA850 and AM33xx. The driver
> > > > previously was not enabled by any platform and the private SRAM API
> > > > was accessing an invalid SRAM bank for use on DA850. For AM33xx,
> > > > DT, pinctrl, and runtime PM support are added since AM33xx only
> > > > boots via DT.
> > >
> > > I'm dropping AM33xx/OMAP support from v3 for this series
> >
> > Just for my clarification, I believe you will be taking up AM33xx/OMAP
> > SRAM support later once you have completed supporting DaVinci. Right?
>
> There's no SRAM support for uio_pruss to be handled for AM33xx,

Sorry for not being clearer.

I was referring to adding SRAM support for McASP module on AM335x platform.


> but I
> will be posting a separate series with the DT portion and some alternate
> hard reset handling implementation. I find the private OMAP reset api to
> be very ugly but we might have to go with that for now. I didn't want
> the OMAP hard reset portion to hold up the more important part of this
> cleanup.
>
> -Matt
>
> > > since the
> > > focus has turned to fixing Davinci SRAM to provide genalloc support
> > > and the associated use of that in the driver.
> > >
> > > I'll have a separate series with AM33xx support since dealing cleanly
> > > with external resets on OMAP is a bigger issue.
> > >
> > > -Matt
> > > _______________________________________________
> > > Davinci-linux-open-source mailing list
> > > [email protected]
> > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> > >
> >
> >
> > Regards,
> > Gururaja
> > _______________________________________________
> > Davinci-linux-open-source mailing list
> > [email protected]
> > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>


Regards,
Gururaja

2015-08-02 18:42:41

by Matwey V. Kornilov

[permalink] [raw]
Subject: Re: [PATCH v2 0/7] uio_pruss cleanup and platform support

2012-10-03 19:00 GMT+04:00 Matt Porter <[email protected]>:
> On Fri, Sep 28, 2012 at 03:37:45PM -0400, Matt Porter wrote:
>> Changes since v1:
>> - Replaced uio_pruss private SRAM API use with genalloc
>> - Added DA850 platform device and clock support
>> - Added DA850 L3 RAM gen_pool support
>> - Split out DT binding
>>
>> This series enables uio_pruss on both DA850 and AM33xx. The driver
>> previously was not enabled by any platform and the private SRAM API
>> was accessing an invalid SRAM bank for use on DA850. For AM33xx,
>> DT, pinctrl, and runtime PM support are added since AM33xx only
>> boots via DT.
>
> I'm dropping AM33xx/OMAP support from v3 for this series since the
> focus has turned to fixing Davinci SRAM to provide genalloc support
> and the associated use of that in the driver.
>
> I'll have a separate series with AM33xx support since dealing cleanly
> with external resets on OMAP is a bigger issue.

Hello Matt,

Any news on AM33xx support here?

I would even try to implement it by myself, but at the moment stuff
about external resets is too complicated to me, I even can not
understand where problem is. Fetching config from DT instead of
platform in pruss_probe seems to be trivial.

>
> -Matt
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>



--
With best regards,
Matwey V. Kornilov
http://blog.matwey.name
xmpp://[email protected]