Thread (17 messages) 17 messages, 6 authors, 2016-11-08

Re: [PATCH v2 3/4] Device bindings documentation updated ACPI-enabled platforms not currently supported

From: Ramiro Oliveira <hidden>
Date: 2016-10-18 14:51:55

On 10/14/2016 7:20 PM, Wolfram Sang wrote:
On Fri, Oct 14, 2016 at 06:30:15PM +0100, Mark Rutland wrote:
quoted
On Fri, Oct 14, 2016 at 05:52:50PM +0100, Luis.Oliveira@synopsys.com wrote:
quoted
-		is_slave = device_property_read_bool(&pdev->dev, "isslave");
Which tree is this based on? I cant see the existing isslave property in
mainline HEAD (commit 29fbff8698fc0ac1).
Same surprise here. Because I likely would have NAKed the binding.

Why is it needed? Doesn't the driver allow to be master/slave on the
same bus?
I'm replying for Lu�s, since at the moment he's not able to reply.

This is needed because the configuration is different and the i2c-designware
cannot be master/slave without a reset. To resolve that I added this property to
bind it as a slave when needed.

BRs,
Ramiro
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help