[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9951c217-70c1-81cf-a43d-baf6bb02beb9@linux.intel.com>
Date: Wed, 3 Oct 2018 10:10:23 -0700
From: Jae Hyun Yoo <jae.hyun.yoo@...ux.intel.com>
To: Joel Stanley <joel@....id.au>
Cc: Brendan Higgins <brendanhiggins@...gle.com>,
Wolfram Sang <wsa@...-dreams.de>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Andrew Jeffery <andrew@...id.au>, linux-i2c@...r.kernel.org,
OpenBMC Maillist <openbmc@...ts.ozlabs.org>,
devicetree <devicetree@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-aspeed@...ts.ozlabs.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jarkko.nikula@...ux.intel.com,
James Feist <james.feist@...ux.intel.com>,
Vernon Mauery <vernon.mauery@...ux.intel.com>
Subject: Re: [PATCH i2c-next v4 2/3] i2c: aspeed: Add 'timeout' DT property
reading code
Hi Joel,
On 10/3/2018 12:49 AM, Joel Stanley wrote:
> Hello Jae,
>
> On Mon, 1 Oct 2018 at 22:28, Jae Hyun Yoo <jae.hyun.yoo@...ux.intel.com> wrote:
>> @@ -918,6 +919,11 @@ static int aspeed_i2c_probe_bus(struct platform_device *pdev)
>> bus->bus_frequency = 100000;
>> }
>>
>> + ret = of_property_read_u32(pdev->dev.of_node, "timeout",
>> + &timeout_ms);
>> + if (ret)
>> + timeout_ms = 0; /* then adap.timeout will be set by i2c-core */
>
> Is it possible to implement the parsing of this property in the i2c
> core instead?
>
Yes, that's possible but I'm not sure that could be acceptable or not.
Let me try.
Thanks,
Jae
Powered by blists - more mailing lists