lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5596280a-51bb-7491-31f4-5800219888ad@free-electrons.com>
Date:   Tue, 26 Sep 2017 15:08:21 +0200
From:   Quentin Schulz <quentin.schulz@...e-electrons.com>
To:     Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc:     linus.walleij@...aro.org, robh+dt@...nel.org, mark.rutland@....com,
        wens@...e.org, linux@...linux.org.uk, lee.jones@...aro.org,
        linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-sunxi@...glegroups.com, thomas.petazzoni@...e-electrons.com
Subject: Re: [PATCH v2 02/10] pinctrl: axp209: add pinctrl features

Hi Maxime,

On 26/09/2017 15:00, Maxime Ripard wrote:
> On Tue, Sep 26, 2017 at 12:17:12PM +0000, Quentin Schulz wrote:
>> +static const struct axp20x_desc_pin axp209_pins[] = {
>> +	AXP20X_PIN(AXP20X_PINCTRL_PIN(0, "GPIO0"),
>> +		   AXP20X_FUNCTION(0x0, "gpio_out"),
>> +		   AXP20X_FUNCTION(0x2, "gpio_in"),
>> +		   AXP20X_FUNCTION(0x3, "ldo"),
>> +		   AXP20X_FUNCTION(0x4, "adc")),
>> +	AXP20X_PIN(AXP20X_PINCTRL_PIN(1, "GPIO1"),
>> +		   AXP20X_FUNCTION(0x0, "gpio_out"),
>> +		   AXP20X_FUNCTION(0x2, "gpio_in"),
>> +		   AXP20X_FUNCTION(0x3, "ldo"),
>> +		   AXP20X_FUNCTION(0x4, "adc")),
>> +	AXP20X_PIN(AXP20X_PINCTRL_PIN(2, "GPIO2"),
>> +		   AXP20X_FUNCTION(0x0, "gpio_out"),
>> +		   AXP20X_FUNCTION(0x2, "gpio_in")),
>> +};
> 
> If all the functions are the same, and at the same offset, can't we
> just hardcode it, instead of having (and duplicate) all the logic
> below?
> 

AXP20X_PIN(AXP20X_PINCTRL_PIN(0, "GPIO0"),
		AXP20X_GPIO_OUT,
		AXP20X_GPIO_IN,
		AXP20X_LDO,
		AXP20X_ADC))

That's what you mean?

>> +	pctrl_desc = devm_kzalloc(&pdev->dev, sizeof(*pctrl_desc), GFP_KERNEL);
>> +	if (!pctrl_desc)
>> +		return -ENOMEM;
>> +
>> +	pctrl_desc->name = dev_name(&pdev->dev);
>> +	pctrl_desc->owner = THIS_MODULE;
>> +	pctrl_desc->pins = pins;
>> +	pctrl_desc->npins = gpio->desc->npins;
>> +	pctrl_desc->pctlops = &axp20x_pctrl_ops;
>> +	pctrl_desc->pmxops = &axp20x_pmx_ops;
> 
> The strict flag needs to be set too in order to avoid concurrent uses
> of GPIO and other functions.
> 

Strict is a property of pinmux_ops struct (pmxops) and it is set.

Thanks,
Quentin
-- 
Quentin Schulz, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com



Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ