[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160601181049.GA10954@roeck-us.net>
Date: Wed, 1 Jun 2016 11:10:49 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Hoan Tran <hotran@....com>
Cc: Jean Delvare <jdelvare@...e.com>, Jonathan Corbet <corbet@....net>,
Rob Herring <robh+dt@...nel.org>,
Jassi Brar <jassisinghbrar@...il.com>,
Ashwin Chaugule <ashwin.chaugule@...aro.org>,
Duc Dang <dhdang@....com>, Loc Ho <lho@....com>,
linux-hwmon@...r.kernel.org, linux-doc@...r.kernel.org,
lkml <linux-kernel@...r.kernel.org>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [2/3] hwmon: xgene: Adds hwmon driver
On Tue, May 31, 2016 at 11:00:05PM -0700, Hoan Tran wrote:
> Hi Guenter,
>
> >
> > Overall, I have to say that the code is quite complex due to the repeated
> > checks for ACPI. I am close to suggest having two separate drivers,
> > one for ACPI and one for non-ACPI. Any chance to separate ACPI vs. non-ACPI
> > code a bit better ?
>
> How about create separate rx_cb functions for ACPI and non-ACPI ?
Yes, that would be great if it is possible.
> As almost functions are the same between ACPI and non-ACPI, I thought
> keep the same driver is still OK, isn't it ?
>
If you can separate the ACPI code from the non-ACPI code a bit better than
right now, yes.
Thanks,
Guenter
Powered by blists - more mailing lists