On Wed, May 9, 2012 at 1:29 PM, Kevin Hilman <khil...@ti.com> wrote:
> "Woodruff, Richard" <r-woodru...@ti.com> writes:
>>> From: Hilman, Kevin
>>> Sent: Tuesday, May 08, 2012 5:17 PM
>>> A basic OMAP AVS driver has been in mainline for a long time, yet we
>>> have not seen support submitted for all of these features.
>> 1.5/3.5 is a feature.
> And I'm still waiting for it to be submitted upstream.
>> ABB is requirement for a production useable driver. Higher speed rated
>> OMAP4 and all OMAP5 added these to be useable.
> ditto
>> Yes this is effort. Point of mentioning is to raise awareness of need.
> I'm well aware of the need.
>> Yet to be added feature has different meaning than functional gap.
> And both need to be submitted upstream.

SR 1.5: http://marc.info/?l=linux-omap&m=129933897910785&w=2
ABB: http://marc.info/?l=linux-omap&m=130939399209099&w=2

I am not sure what you mean "need to be submitted upstream"?

Just tired of seeing things perpetually change without considering
even how to handle features that are mandatory for SoC even with code
posted upstream to show exactly what it takes.. I think you do mean
merged upstream in this context.

Nishanth Menon
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to