[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f9455757-9b7c-683f-2347-118d997968a1@amazon.com>
Date: Thu, 18 Aug 2022 23:20:22 +0300
From: "Farber, Eliav" <farbere@...zon.com>
To: Guenter Roeck <linux@...ck-us.net>
CC: <jdelvare@...e.com>, <robh+dt@...nel.org>, <mark.rutland@....com>,
<linux-hwmon@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <talel@...zon.com>,
<hhhawa@...zon.com>, <jonnyc@...zon.com>, <hanochu@...zon.com>,
<ronenk@...zon.com>, <itamark@...zon.com>, <shellykz@...zon.com>,
<shorer@...zon.com>, <amitlavi@...zon.com>, <almogbs@...zon.com>,
<dwmw@...zon.co.uk>, <rtanwar@...linear.com>
Subject: Re: [PATCH v2 03/16] hwmon: (mr75203) update Moortec PVT controller intel,
vm-map property
On 8/18/2022 10:47 PM, Guenter Roeck wrote:
> Ah. This patch should come first, before making associated
> code changes, and there would need to be an explanation
> _why_ it is not a mandatory property. Also, some action
> is taken in the previous patches if the property is not
> there. That indicates that the driver is expected to
> use some defaults if the property is indeed not provided,
> and that expected default should be documented.
Ack.
I should have been more clear and explained that driver actually handles
the case that "intel,vm-map" does not exist (including an explicit comment
- "Incase intel,vm-map property is not defined ...") and that it is
actually optional.
--
Regards, Eliav
Powered by blists - more mailing lists