mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Hoan Tran <hotran@apm.com>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Loc Ho <lho@apm.com>, patches <patches@apm.com>
Subject: Re: [PATCH v3] hwmon: xgene: Support hwmon v2
Date: Fri, 13 Oct 2017 21:54:51 -0700	[thread overview]
Message-ID: <c2fc7da0-8254-583b-def0-5e261193078a@roeck-us.net> (raw)
In-Reply-To: <CAFHUOYw6ynSxbxrEPJ3DthKG9idjn2GLOcuBhDY-aaVPxk+6fQ@mail.gmail.com>

On 10/13/2017 09:38 PM, Hoan Tran wrote:
> Hi Guenter,
> 
> On Fri, Oct 13, 2017 at 9:28 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> On 10/13/2017 04:10 PM, Hoan Tran wrote:
>>>
>>> This patch supports xgene-hwmon v2 which uses the non-cachable memory
>>> as the PCC shared memory.
>>>
>>> Signed-off-by: Hoan Tran <hotran@apm.com>
>>> ---
>>> v3
>>>    - Use local version variable
>>>    - Use inline calls instead of the private map function
>>>
>>> v2
>>>    - Map PCC shared mem by ioremap() in case hwmon is v2
>>>
>>>    drivers/hwmon/xgene-hwmon.c | 40
>>> +++++++++++++++++++++++++++++++---------
>>>    1 file changed, 31 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/drivers/hwmon/xgene-hwmon.c b/drivers/hwmon/xgene-hwmon.c
>>> index 9c0dbb8..6b6c732 100644
>>> --- a/drivers/hwmon/xgene-hwmon.c
>>> +++ b/drivers/hwmon/xgene-hwmon.c
>>> @@ -91,6 +91,11 @@
>>>    #define to_xgene_hwmon_dev(cl)                \
>>>          container_of(cl, struct xgene_hwmon_dev, mbox_client)
>>>    +enum xgene_hwmon_version {
>>> +       XGENE_HWMON_V1 = 0,
>>> +       XGENE_HWMON_V2 = 1,
>>> +};
>>> +
>>>    struct slimpro_resp_msg {
>>>          u32 msg;
>>>          u32 param1;
>>> @@ -609,6 +614,15 @@ static void xgene_hwmon_tx_done(struct mbox_client
>>> *cl, void *msg, int ret)
>>>          }
>>>    }
>>>    +#ifdef CONFIG_ACPI
>>> +static const struct acpi_device_id xgene_hwmon_acpi_match[] = {
>>> +       {"APMC0D29", XGENE_HWMON_V1},
>>> +       {"APMC0D8A", XGENE_HWMON_V2},
>>> +       {},
>>> +};
>>> +MODULE_DEVICE_TABLE(acpi, xgene_hwmon_acpi_match);
>>> +#endif
>>> +
>>>    static int xgene_hwmon_probe(struct platform_device *pdev)
>>>    {
>>>          struct xgene_hwmon_dev *ctx;
>>> @@ -650,6 +664,16 @@ static int xgene_hwmon_probe(struct platform_device
>>> *pdev)
>>>                  }
>>>          } else {
>>>                  struct acpi_pcct_hw_reduced *cppc_ss;
>>> +               const struct acpi_device_id *acpi_id;
>>> +               int version;
>>> +
>>> +#ifdef CONFIG_ACPI
>>> +               acpi_id = acpi_match_device(xgene_hwmon_acpi_match,
>>> &pdev->dev);
>>> +               if (!acpi_id)
>>> +                       return -EINVAL;
>>> +
>>> +               version = (int)acpi_id->driver_data;
>>> +#endif
>>>
>>
>> This leaves "version" uninitialized if CONFIG_ACPI is not defined.
> 
> If CONFIG_ACPI is not defined, "acpi_disabled" is true. So this piece
> of code is not executed
> 

Then why do you need the ifdef in code that isn't executed anyway
if CONFIG_ACPI is not defined ? Because xgene_hwmon_acpi_match is
conditional ? Not an argument, because that doesn't have to be.

Also, the compiler doesn't know that, and I am quite sure that
it is going to complain that version may be used uninitialized if
CONFIG_ACPI is not defined.

Sorry, I won't accept that code.

Guenter

> Thanks
> Hoan
> 
>>
>> Guenter
>>
>>
>>>                  if (device_property_read_u32(&pdev->dev, "pcc-channel",
>>>                                               &ctx->mbox_idx)) {
>>> @@ -690,7 +714,13 @@ static int xgene_hwmon_probe(struct platform_device
>>> *pdev)
>>>                   */
>>>                  ctx->comm_base_addr = cppc_ss->base_address;
>>>                  if (ctx->comm_base_addr) {
>>> -                       ctx->pcc_comm_addr = memremap(ctx->comm_base_addr,
>>> +                       if (version == XGENE_HWMON_V2)
>>> +                               ctx->pcc_comm_addr = (void __force
>>> *)ioremap(
>>> +
>>> ctx->comm_base_addr,
>>> +                                                       cppc_ss->length);
>>> +                       else
>>> +                               ctx->pcc_comm_addr = memremap(
>>> +
>>> ctx->comm_base_addr,
>>>                                                          cppc_ss->length,
>>>                                                          MEMREMAP_WB);
>>>                  } else {
>>> @@ -758,14 +788,6 @@ static int xgene_hwmon_remove(struct platform_device
>>> *pdev)
>>>          return 0;
>>>    }
>>>    -#ifdef CONFIG_ACPI
>>> -static const struct acpi_device_id xgene_hwmon_acpi_match[] = {
>>> -       {"APMC0D29", 0},
>>> -       {},
>>> -};
>>> -MODULE_DEVICE_TABLE(acpi, xgene_hwmon_acpi_match);
>>> -#endif
>>> -
>>>    static const struct of_device_id xgene_hwmon_of_match[] = {
>>>          {.compatible = "apm,xgene-slimpro-hwmon"},
>>>          {}
>>>
>>
> 

  reply	other threads:[~2017-10-14  4:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 23:10 Hoan Tran
2017-10-14  4:28 ` Guenter Roeck
2017-10-14  4:38   ` Hoan Tran
2017-10-14  4:54     ` Guenter Roeck [this message]
2017-10-14  4:59       ` Hoan Tran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c2fc7da0-8254-583b-def0-5e261193078a@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=hotran@apm.com \
    --cc=jdelvare@suse.com \
    --cc=lho@apm.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@apm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®