RE: pinctrl/amd: Configure GPIO register using BIOS settings

["Agrawal, Nitesh-kumar" <Nitesh-kumar.Agrawal@xxxxxxx>]

-----Original Message-----
From: Dmitry Torokhov [mailto:dmitry.torokhov@xxxxxxxxx] 
Sent: Thursday, September 28, 2017 12:28 PM
To: Agrawal, Nitesh-kumar <Nitesh-kumar.Agrawal@xxxxxxx>
Cc: linus.walleij@xxxxxxxxxx; Sen, Pankaj <Pankaj.Sen@xxxxxxx>; S-k, Shyam-sundar <Shyam-sundar.S-k@xxxxxxx>; linux-gpio@xxxxxxxxxxxxxxx
Subject: Re: pinctrl/amd: Configure GPIO register using BIOS settings

On Fri, Sep 09, 2016 at 03:18:09PM +0000, Agrawal, Nitesh-kumar wrote:
> In the function amd_gpio_irq_set_type, use the settings provided by 
> the BIOS,when the LevelTrig is Edge and activeLevel is HIGH, to 
> configure the GPIO registers. Ignore the settings from client.
> 
> Reviewed-by: Pankaj Sen <Pankaj.Sen@xxxxxxx>
> Signed-off-by: Nitesh Kumar Agrawal <Nitesh-kumar.Agrawal@xxxxxxx>

Just found this patch in the tree. Can you please explain why it is needed (the patch description unfortunately tells what the patch does, but not why).

I would expect that we either allow reprogramming the trigger as client wishes or would error out and let the upper layers know. Silently "fixing" the settings is wrong course of action in my opinion.

If this was trying to work around Elan touchpad drivers not working on AMD platforms it needs to be solved in Elan driver, not here.

[Nitesh]We have reverted the patch in the later version of the patch.

--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html