On 2016-08-08 04:14, Vinod Koul wrote:
On Thu, Aug 04, 2016 at 09:59:43AM -0400, Sinan Kaya wrote:
On 8/4/2016 8:46 AM, Vinod Koul wrote:
>> > Yes, I do have a new device ID for platforms with MSI capability.
>> >
>> > Which new binding are you referring to?
> If you have "QCOM8062" why do you need DT to tell hidma-1.1 ?
Unfortunately, DT cannot do a binding with the ACPI names. Similarly,
ACPI
cannot do a binding with the DT name.
The structure of binding name is also subject to different kind of
rules
for DT and ACPI.
This driver supports both device tree and ACPI. That's why, two
different
names are required.
Hmmm, wasn't the who get_property stuff supposed to make properties
work on
both ACPi & DT. I am not sure though about the current state of affairs
on
that.
Get property works. It is able to abstract device driver properties. A
driver doesn't need to know whether it is coming from acpi dsd or of.
However, no such mechanism exists for driver names due to nature of
different naming requirements.
Of has its own match table and acpi has its own. Acpi also has
ridiculous 8 character name limitation.
--
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
