From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/6] i.mx: Add the initial support for freescale i.MX6Q processor
Date: Tue, 15 Nov 2011 12:08:21 +0100 [thread overview]
Message-ID: <4EC24825.5010304@denx.de> (raw)
In-Reply-To: <CAFQ4atRCuf0PFdDp_R6J6rMpa+QQpivt7nHMs86tvgsDhsYpng@mail.gmail.com>
On 11/15/2011 11:10 AM, Jason Hui wrote:
>>> yes, we already had drivers/gpio/mxc_gpio.c driver. In this driver, we will
>>> use this structure. And it's the same as i.mx5 before.
>>
>> So why do you need to expose the structure, isn't it internal to the driver?
> Yes, it's internal to the gpio driver, but, all the soc does not have
> the same gpio_regs layout,
> so we put it here in order to have multiple #ifdef.
> Stefano, any comments for this?
We are using now the general GPIO framework - changes were done for all
iMX SOCs, and it is used in most other SOCs, too. So the general API is
exposed in include/asm/gpio.h.
We can have different implementation for each specific SOC. We want to
maintain only one driver (mxc_gpio.c), and the differences in layout are
done in arch/gpio.h (at the end, the structure we are talking about). As
you can see, there is a lot of specific implementation in asm/arch-*.
The generic API (include/asm/gpio.h) includes an arch specific file
asm/arch/gpio, and this file must be provided.
This allows us (theoretically) to adapt the driver to the specific
layout of the SOC. This helps if the layout of MX3x is differnt form the
layout of MX5x, MX6x,...
I admit that the layout for the interesting fields (data, direction) is
the same (see asm/arch-mx25/gpio.h, asm/arch-mx35/gpio.h and
asm/arch-mx5/gpio.h). There is the definition of other registers, but
they are not used. We have to provide in any case an arch specific
gpio.h, and this can contains the differences in layout, if any.
Another possibility can be to put the registers in a common place for
all IMX SOCs, and the arch specific gpio.h, required by the generic
gpio.h, will only include it. But if we go on on this solution (only if
we have *really* the same layout for all SOCs), this should be done for
all IMX in a shot, not only for one of them - I do not like to have
inconsistencies in the interface between IMX SOCs.
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-11-15 11:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 10:36 [U-Boot] [PATCH 0/6] i.mx: add the initial i.mx6q core/board support Jason Liu
2011-11-12 10:36 ` [U-Boot] [PATCH 1/6] i.mx: i.mx5: Move some files to imx-common folder Jason Liu
2011-11-14 8:34 ` Stefano Babic
2011-11-14 8:57 ` Jason Hui
2011-11-14 11:28 ` Stefano Babic
2011-11-12 10:36 ` [U-Boot] [PATCH 2/6] i.mx: Add the initial support for freescale i.MX6Q processor Jason Liu
2011-11-13 23:11 ` Marek Vasut
2011-11-14 8:47 ` Jason Hui
2011-11-14 10:45 ` Marek Vasut
2011-11-15 10:10 ` Jason Hui
2011-11-15 11:08 ` Stefano Babic [this message]
2011-11-14 9:03 ` Stefano Babic
2011-11-14 9:42 ` Jason Hui
2011-11-14 11:49 ` Stefano Babic
2011-11-15 10:18 ` Jason Hui
2011-11-12 10:36 ` [U-Boot] [PATCH 3/6] i.mx: mxc_gpio: add the i.mx6q support Jason Liu
2011-11-14 9:04 ` Stefano Babic
2011-11-12 10:36 ` [U-Boot] [PATCH 4/6] i.mx: serial_mxc: " Jason Liu
2011-11-12 10:36 ` [U-Boot] [PATCH 5/6] i.mx: fsl_esdhc: " Jason Liu
2011-11-12 16:35 ` Marek Vasut
2011-11-14 8:37 ` Jason Hui
2011-11-14 10:42 ` Marek Vasut
2011-11-15 9:46 ` Jason Hui
2011-11-15 11:56 ` Stefano Babic
2011-11-16 1:36 ` Jason Hui
2011-11-16 2:24 ` Marek Vasut
2011-11-14 9:06 ` Stefano Babic
2011-11-12 10:36 ` [U-Boot] [PATCH 6/6] i.mx: i.mx6q: Add the initial support for i.mx6q ARM2 board Jason Liu
2011-11-12 19:42 ` Fabio Estevam
2011-11-14 8:59 ` Jason Hui
2011-11-12 20:13 ` Fabio Estevam
2011-11-14 9:10 ` Jason Hui
2011-11-13 7:04 ` Igor Grinberg
2011-11-14 9:13 ` Jason Hui
2011-11-14 9:25 ` Stefano Babic
2011-11-14 9:55 ` Jason Hui
2011-11-14 11:36 ` Stefano Babic
2011-11-16 11:34 ` Dirk Behme
2011-11-16 12:15 ` Jason Hui
2011-11-12 16:10 ` [U-Boot] [PATCH 0/6] i.mx: add the initial i.mx6q core/board support Dirk Behme
2011-11-14 8:11 ` Jason Hui
2011-11-16 11:56 ` Dirk Behme
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=4EC24825.5010304@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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