On Tue, Aug 04, 2020 at 12:59:24PM +0300, Codrin Ciubotariu wrote:
> Multiple I2C bus drivers use similar bindings to obtain information needed
> for I2C recovery. For example, for platforms using device-tree, the
> properties look something like this:
>
> {
> ...
> pinctrl-names =
Multiple I2C bus drivers use similar bindings to obtain information needed
for I2C recovery. For example, for platforms using device-tree, the
properties look something like this:
{
...
pinctrl-names = "default", "gpio";
pinctrl-0 = <_i2c_default>;
pinctrl-1 =
> I agree will all your suggestions, except with the removal of if
> (bri->recover_bus) . If you agree with this, I can send the next version
> and remove the RFC.
Yes, sure. That was a brown paper bag thingie from my side. Please go
ahead!
signature.asc
Description: PGP signature
On 02.08.2020 19:54, Wolfram Sang wrote:
> On Fri, Jun 19, 2020 at 05:19:02PM +0300, Codrin Ciubotariu wrote:
>> Multiple I2C bus drivers use similar bindings to obtain information needed
>> for I2C recovery. For example, for platforms using device-tree, the
>> properties look something like this:
On Fri, Jun 19, 2020 at 05:19:02PM +0300, Codrin Ciubotariu wrote:
> Multiple I2C bus drivers use similar bindings to obtain information needed
> for I2C recovery. For example, for platforms using device-tree, the
> properties look something like this:
>
> {
> ...
> pinctrl-names =
Multiple I2C bus drivers use similar bindings to obtain information needed
for I2C recovery. For example, for platforms using device-tree, the
properties look something like this:
{
...
pinctrl-names = "default", "gpio";
// or pinctrl-names = "default", "recovery";
6 matches
Mail list logo
