mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
	Jonathan Cameron <jic23@kernel.org>
Cc: Kiernan Hager <kah.listaddress@gmail.com>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [RFC] iio: light: acpi-als: Enable the light sensor on the Zenbook UX430UQ
Date: Sun, 19 Nov 2017 19:11:32 +0100	[thread overview]
Message-ID: <2bf0e8c2-efe9-c309-844c-de5392216848@denx.de> (raw)
In-Reply-To: <CABFtUbQm8JMUdo46d4VJR=8gHzphxEs1UofeB+cpxW6xHkSnAg@mail.gmail.com>

On 11/19/2017 06:38 PM, Gabriele Mazzotta wrote:
> 2017-11-19 18:03 GMT+01:00 Jonathan Cameron <jic23@kernel.org>:
>> On Wed, 15 Nov 2017 20:27:54 -0700
>> Kiernan Hager <kah.listaddress@gmail.com> wrote:
>>
>>> This makes acpi-als properly enable the light sensor on the Zenbook UX430UQ. I don't know if the checking that I do to make sure that the ACPI method exists is sufficient or if it should disable the sensor when the module is unloaded, so input is appreciated on those matters.
>>
>> Please wrap descriptions to around 72 characters (leaves room for indentation
>> in the email thread :)
>>
>> This seems very much like a board specific hack.  I've cc'd people
>> who have worked on the driver recently and the acpi list.
> 
> This is indeed board specific. I know many other laptops of the
> Zenbook line need something similar and if you look at
> drivers/platform/x86/asus-wmi.c or any other asus-* driver you'll
> find several quirks to enable various features.

Maybe that's where it should go . EC0 in the ACPI path seems like
Embedded Controller to me .

> Kiernan, check commit aca234f6378864d85514be558746c0ea6eabfa8e
> ("asus-wmi: provide access to ALS control") in particular.
> 
>>>
>>> Signed-off-by: Kiernan Hager <kah.listaddress@gmail.com>
>>> ---
>>>  drivers/iio/light/acpi-als.c | 16 ++++++++++++++++
>>>  1 file changed, 16 insertions(+)
>>>
>>> diff --git a/drivers/iio/light/acpi-als.c b/drivers/iio/light/acpi-als.c
>>> index c35e2f8df339..8fd66166f19f 100644
>>> --- a/drivers/iio/light/acpi-als.c
>>> +++ b/drivers/iio/light/acpi-als.c
>>> @@ -179,6 +179,10 @@ static int acpi_als_add(struct acpi_device *device)
>>>       struct acpi_als *als;
>>>       struct iio_dev *indio_dev;
>>>       struct iio_buffer *buffer;
>>> +     unsigned long long temp_val;
>>> +     acpi_status status;
>>> +     struct acpi_object_list arg_list;
>>> +     union acpi_object arg;
>>>
>>>       indio_dev = devm_iio_device_alloc(&device->dev, sizeof(*als));
>>>       if (!indio_dev)
>>> @@ -203,6 +207,18 @@ static int acpi_als_add(struct acpi_device *device)
>>>
>>>       iio_device_attach_buffer(indio_dev, buffer);
>>>
>>> +     arg_list.count = 1;
>>> +     arg_list.pointer = &arg;
>>> +     arg.type = ACPI_TYPE_INTEGER;
>>> +     arg.integer.value = 1;
>>> +
>>> +     if (acpi_has_method(als->device->handle, "\\_SB.PCI0.LPCB.EC0.ALSC")) {
>> So this is poking something on
>> PCI bus 0
>> LPC bus B
>> Somethingbus 0
>> Ambient light controller.
>>
>> I assume there is a better way of establishing this needs to be set?
>>
>>> +             status = acpi_evaluate_integer(als->device->handle,
>>> +                                            "\\_SB.PCI0.LPCB.EC0.ALSC",
>>> +                                            &arg_list,
>>> +                                            &temp_val);
>>> +     }
>>> +
>>>       return devm_iio_device_register(&device->dev, indio_dev);
>>>  }
>>>
>>


-- 
Best regards,
Marek Vasut

  reply	other threads:[~2017-11-19 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16  3:27 Kiernan Hager
2017-11-19 17:03 ` Jonathan Cameron
2017-11-19 17:38   ` Gabriele Mazzotta
2017-11-19 18:11     ` Marek Vasut [this message]
2017-11-20 16:51       ` Kiernan Hager

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=2bf0e8c2-efe9-c309-844c-de5392216848@denx.de \
    --to=marex@denx.de \
    --cc=gabriele.mzt@gmail.com \
    --cc=jic23@kernel.org \
    --cc=kah.listaddress@gmail.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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®