All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org,
	Patrice Vilchez <patrice.vilchez@atmel.com>,
	Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: Re: [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board
Date: Thu, 20 Oct 2011 09:14:16 +0200	[thread overview]
Message-ID: <20111020091416.1e90828c@skate> (raw)
In-Reply-To: <1319041134-19712-4-git-send-email-maxime.ripard@free-electrons.com>

Le Wed, 19 Oct 2011 18:18:54 +0200,
Maxime Ripard <maxime.ripard@free-electrons.com> a =C3=A9crit :

> +void __init at91_add_device_adc(struct at91_adc_data *data)
> +{
> +	if (!data)
> +		return;
> +
> +	at91_set_A_periph(AT91_PIN_PC0, 0);
> +	at91_set_A_periph(AT91_PIN_PC1, 0);
> +	at91_set_A_periph(AT91_PIN_PC2, 0);
> +	at91_set_A_periph(AT91_PIN_PC3, 0);

As suggested, the decision of which ADC channels are used and therefore
which pins should be muxed to function A is a board-specific decision
and should not be enforced by SoC code.

> +static struct at91_adc_data ek_adc_data =3D {
> +	.channels =3D 4,
> +	.adc_clock =3D 5000000,
> +	.startup_time =3D 10,
> +};

And on the opposite, those informations are specific to a SoC, not to a
board. So to avoid duplication in all board files, they should be moved
to the corresponding SoC file.

Maybe something like:

#define AT91_ADC_MAX_CHANNELS 8

struct at91_adc_data {
    unsigned int adc_clock;
    u8 channels_used[AT91_ADC_MAX_CHANNELS];
    u8 startup_time;
    u8 channels;
};

at91_add_device_adc() {
	if (data->channels_used[0])
		at91_set_A_periph(AT91_PIN_PC0, 0);
	if (data->channels_used[1])
		at91_set_A_periph(AT91_PIN_PC1, 0);
	if (data->channels_used[2])
		at91_set_A_periph(AT91_PIN_PC2, 0);
	if (data->channels_used[3])
		at91_set_A_periph(AT91_PIN_PC3, 0);
	data->startup_time =3D ...
	data->channels =3D ...
	data->adc_clock =3D ...
}

and the board file would do:

struct at91_adc_data ek_adc_data =3D {
	.channels_used =3D { 1, 0, 1, 1 },;
};

Or maybe others have different suggestions ?

Regards,

Thomas
--=20
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

WARNING: multiple messages have this Message-ID (diff)
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board
Date: Thu, 20 Oct 2011 09:14:16 +0200	[thread overview]
Message-ID: <20111020091416.1e90828c@skate> (raw)
In-Reply-To: <1319041134-19712-4-git-send-email-maxime.ripard@free-electrons.com>

Le Wed, 19 Oct 2011 18:18:54 +0200,
Maxime Ripard <maxime.ripard@free-electrons.com> a ?crit :

> +void __init at91_add_device_adc(struct at91_adc_data *data)
> +{
> +	if (!data)
> +		return;
> +
> +	at91_set_A_periph(AT91_PIN_PC0, 0);
> +	at91_set_A_periph(AT91_PIN_PC1, 0);
> +	at91_set_A_periph(AT91_PIN_PC2, 0);
> +	at91_set_A_periph(AT91_PIN_PC3, 0);

As suggested, the decision of which ADC channels are used and therefore
which pins should be muxed to function A is a board-specific decision
and should not be enforced by SoC code.

> +static struct at91_adc_data ek_adc_data = {
> +	.channels = 4,
> +	.adc_clock = 5000000,
> +	.startup_time = 10,
> +};

And on the opposite, those informations are specific to a SoC, not to a
board. So to avoid duplication in all board files, they should be moved
to the corresponding SoC file.

Maybe something like:

#define AT91_ADC_MAX_CHANNELS 8

struct at91_adc_data {
    unsigned int adc_clock;
    u8 channels_used[AT91_ADC_MAX_CHANNELS];
    u8 startup_time;
    u8 channels;
};

at91_add_device_adc() {
	if (data->channels_used[0])
		at91_set_A_periph(AT91_PIN_PC0, 0);
	if (data->channels_used[1])
		at91_set_A_periph(AT91_PIN_PC1, 0);
	if (data->channels_used[2])
		at91_set_A_periph(AT91_PIN_PC2, 0);
	if (data->channels_used[3])
		at91_set_A_periph(AT91_PIN_PC3, 0);
	data->startup_time = ...
	data->channels = ...
	data->adc_clock = ...
}

and the board file would do:

struct at91_adc_data ek_adc_data = {
	.channels_used = { 1, 0, 1, 1 },;
};

Or maybe others have different suggestions ?

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2011-10-20  7:14 UTC|newest]

Thread overview: 139+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 16:18 [PATCH] AT91: Add a driver for the ADC Maxime Ripard
2011-10-19 16:18 ` Maxime Ripard
2011-10-19 16:18 ` [PATCH 1/3] ARM: AT91: Add platform data for the ADCs Maxime Ripard
2011-10-19 16:18   ` Maxime Ripard
2011-10-19 16:18 ` [PATCH 2/3] ARM: AT91: IIO: Add AT91 ADC driver Maxime Ripard
2011-10-19 16:18   ` Maxime Ripard
2011-10-19 16:42   ` Jonathan Cameron
2011-10-19 16:42     ` Jonathan Cameron
2011-10-19 18:23     ` Maxime Ripard
2011-10-19 18:23       ` Maxime Ripard
2011-10-20  7:05       ` Thomas Petazzoni
2011-10-20  7:05         ` Thomas Petazzoni
2011-10-20  8:33         ` Jonathan Cameron
2011-10-20  8:33           ` Jonathan Cameron
2011-10-20  8:49           ` Thomas Petazzoni
2011-10-20  8:49             ` Thomas Petazzoni
2011-10-20  9:19             ` Jonathan Cameron
2011-10-20  9:19               ` Jonathan Cameron
2011-10-20  9:52           ` Mark Brown
2011-10-20  9:52             ` Mark Brown
2011-10-20  7:09   ` Lars-Peter Clausen
2011-10-20  7:09     ` Lars-Peter Clausen
2011-10-21 17:54     ` Maxime Ripard
2011-10-21 17:54       ` Maxime Ripard
2011-10-21 17:55       ` Lars-Peter Clausen
2011-10-21 17:55         ` Lars-Peter Clausen
2011-10-23  9:08   ` Jean-Christophe PLAGNIOL-VILLARD
2011-10-23  9:08     ` Jean-Christophe PLAGNIOL-VILLARD
2011-10-24  8:21     ` Maxime Ripard
2011-10-24  8:21       ` Maxime Ripard
2011-10-19 16:18 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-10-19 16:18   ` Maxime Ripard
2011-10-20  6:28   ` Alexander Stein
2011-10-20  6:28     ` Alexander Stein
2011-10-21 17:47     ` Maxime Ripard
2011-10-21 17:47       ` Maxime Ripard
2011-10-20  7:14   ` Thomas Petazzoni [this message]
2011-10-20  7:14     ` Thomas Petazzoni
2011-11-03 10:11 ` [PATCHv2] AT91: Add a driver for the ADC Maxime Ripard
2011-11-03 10:11   ` Maxime Ripard
2011-11-03 10:11   ` [PATCH 1/3] ARM: AT91: Add platform data for the ADCs Maxime Ripard
2011-11-03 10:11     ` Maxime Ripard
2011-11-03 11:27     ` Linus Walleij
2011-11-03 11:27       ` Linus Walleij
2011-11-03 16:27       ` Maxime Ripard
2011-11-03 16:27         ` Maxime Ripard
2011-11-03 16:38         ` Linus Walleij
2011-11-03 18:05           ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 18:05             ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-04 10:27     ` Jonathan Cameron
2011-11-04 10:27       ` Jonathan Cameron
2011-11-04 10:36       ` Jonathan Cameron
2011-11-04 10:36         ` Jonathan Cameron
2011-11-04 10:34     ` Jonathan Cameron
2011-11-04 10:34       ` Jonathan Cameron
2011-11-04 15:22       ` Maxime Ripard
2011-11-04 16:28         ` Jonathan Cameron
2011-11-04 16:28           ` Jonathan Cameron
2011-11-03 10:11   ` [PATCH 2/3] ARM: AT91: IIO: Add AT91 ADC driver Maxime Ripard
2011-11-03 10:11     ` Maxime Ripard
2011-11-04 10:27     ` Jonathan Cameron
2011-11-04 10:27       ` Jonathan Cameron
2011-11-04 16:29       ` Maxime Ripard
2011-11-04 16:40         ` Jonathan Cameron
2011-11-03 10:11   ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-11-03 10:11     ` Maxime Ripard
2011-11-04 10:33     ` Jonathan Cameron
2011-11-04 10:33       ` Jonathan Cameron
2011-11-04 11:25       ` Maxime Ripard
2011-11-04 15:52         ` Linus Walleij
2011-11-04 16:32         ` Jonathan Cameron
2011-11-04 16:32           ` Jonathan Cameron
2011-11-07 16:08 ` [PATCHv3] AT91: Add a driver for the ADC Maxime Ripard
2011-11-07 16:08   ` Maxime Ripard
2011-11-07 16:08   ` [PATCH 1/3] ARM: AT91: Add platform data for the ADCs Maxime Ripard
2011-11-07 16:08     ` Maxime Ripard
2011-11-07 16:27     ` Jonathan Cameron
2011-11-07 16:27       ` Jonathan Cameron
2011-11-08 13:19     ` Thomas Petazzoni
2011-11-08 13:19       ` Thomas Petazzoni
2011-11-07 16:08   ` [PATCH 2/3] ARM: AT91: IIO: Add AT91 ADC driver Maxime Ripard
2011-11-07 16:08     ` Maxime Ripard
2011-11-08 13:30     ` Thomas Petazzoni
2011-11-08 13:30       ` Thomas Petazzoni
2011-11-07 16:08   ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-11-07 16:08     ` Maxime Ripard
2011-11-09 10:19 ` [PATCHv4] AT91: Add a driver for the ADC Maxime Ripard
2011-11-09 10:19   ` Maxime Ripard
2011-11-09 10:19   ` [PATCH 1/3] ARM: AT91: Add platform data for the ADCs Maxime Ripard
2011-11-09 10:19     ` Maxime Ripard
2011-11-09 10:19   ` [PATCH 2/3] ARM: AT91: IIO: Add AT91 ADC driver Maxime Ripard
2011-11-09 10:19     ` Maxime Ripard
2011-11-10 17:35     ` Jonathan Cameron
2011-11-10 17:35       ` Jonathan Cameron
2011-11-11 12:34       ` Jonathan Cameron
2011-11-11 12:34         ` Jonathan Cameron
2011-11-14  9:59         ` Maxime Ripard
2011-11-14  9:59           ` Maxime Ripard
2011-11-14  9:06       ` Maxime Ripard
2011-11-14  9:06         ` Maxime Ripard
2011-11-09 10:19   ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-11-09 10:19     ` Maxime Ripard
2011-11-10 17:37     ` Jonathan Cameron
2011-11-10 17:37       ` Jonathan Cameron
  -- strict thread matches above, loose matches on Subject: below --
2011-11-14 10:06 [PATCHv5] AT91: Add a driver for the ADC Maxime Ripard
2011-11-14 10:06 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-11-14 10:06   ` Maxime Ripard
2011-11-14 11:29   ` Nicolas Ferre
2011-11-14 11:29     ` Nicolas Ferre
2011-11-14 15:17     ` Maxime Ripard
2011-11-14 15:17       ` Maxime Ripard
2011-11-14 15:23       ` Nicolas Ferre
2011-11-14 15:23         ` Nicolas Ferre
2011-11-14 17:30 [PATCH v6] AT91: Add a driver for the ADC Maxime Ripard
2011-11-14 17:30 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-11-14 17:30   ` Maxime Ripard
2011-11-14 20:34   ` Jonathan Cameron
2011-11-14 20:34     ` Jonathan Cameron
2011-11-15 10:27     ` Maxime Ripard
2011-11-15 10:27       ` Maxime Ripard
2011-11-15 10:54 [PATCH v7] AT91: Add a driver for the ADC Maxime Ripard
2011-11-15 10:54 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-11-15 10:54   ` Maxime Ripard
2011-11-18 10:12 [PATCH v8] AT91: Add a driver for the ADC Maxime Ripard
2011-11-18 10:12 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-11-18 10:12   ` Maxime Ripard
2011-11-24 11:27 [PATCH v9] AT91: Add a driver for the ADC Maxime Ripard
2011-11-24 11:27 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-11-24 11:27   ` Maxime Ripard
2011-11-24 14:19   ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-24 14:19     ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-24 15:20   ` Fabio Estevam
2011-11-24 15:20     ` Fabio Estevam
2011-11-24 15:26     ` Maxime Ripard
2011-11-24 15:26       ` Maxime Ripard
2011-11-30  9:14 [PATCH v11] AT91: Add a driver for the ADC Maxime Ripard
2011-11-30  9:15 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-11-30  9:15   ` Maxime Ripard
2011-12-02 13:17 [PATCH v12] AT91: Add a driver for the ADC Maxime Ripard
2011-12-02 13:17 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2011-12-02 13:17   ` Maxime Ripard
2011-12-14 10:01 [PATCH v13] AT91: Add a driver for the ADC Maxime Ripard
2011-12-14 10:01 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2012-01-16 21:36 [PATCH RESEND v13] AT91: Add a driver for the ADC Maxime Ripard
2012-01-16 21:36 ` [PATCH 3/3] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2012-01-16 21:36   ` Maxime Ripard
2012-01-18 10:28   ` Nicolas Ferre
2012-01-18 10:28     ` Nicolas Ferre

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=20111020091416.1e90828c@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=patrice.vilchez@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.