From: urx.forever@gmail.com (Yuri Ludkevich)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: COLIBRI PXA320: fix UCB1400 irq autoprobing
Date: Fri, 20 Aug 2010 12:34:35 +0400 [thread overview]
Message-ID: <AANLkTiktCBNjwN6gfLMv6=BQnGvujbdGPZKk+o+yXqah@mail.gmail.com> (raw)
In-Reply-To: <20100818115008.GI17833@buzzloop.caiaq.de>
2010/8/18 Daniel Mack <daniel@caiaq.de>
> On Wed, Aug 11, 2010 at 11:26:20PM +0200, Marek Vasut wrote:
> > Dne St 11. srpna 2010 16:33:45 Daniel Mack napsal(a):
> > > Hi Yuri,
> > >
> > > thanks for the patch.
> > >
> > > On Wed, Aug 11, 2010 at 04:54:13PM +0400, Yuri Ludkevich wrote:
> > > > Ads properly initialization to GPIO4 ( alt. fn. #1, nCS3; because
> GPIO4
> > > > and GPIO4_2 cannot be
> > > > configured as GPIO simultaneously ) so GPIO4_2 which used as irq line
> > > > from UCB1400 may be
> > > > detected while irq autoprobing routine.
> > >
> > > This looks fine to me, but Marek wanted to rework the board support in
> > > order to unify the GPIO configs for better readability. Marek, is there
> > > any tree which contains your changes already?
> > >
> > I hope there will be tomorrow ...
>
> Yuri, could you check out Marek's tree from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/marex/pxa-linux-2.6.gitwork
>
> (not that "work" ist the branch you'll need to work on).
>
> You'll see that colibri-pxa320.c looks a lot different now, so your
> patch should be a one-liner now.
>
> Also, more testing of this code is certainly appreciated :)
>
>
I have looked at code and I have couple of questions about colibri-pxa320.c
and colibri-evalboard.c:
Why colibri_pxa320_evalboard_pin_config[] placed in colibri-pxa320.c, not in
evalboard?
Why there is no defconfig for colibri pxa320?
BTW: we have our own board which very similar to colibri evalboard - same
RTC, UCB1400 as sound and touch controller. But we have USB hub onboard, do
not use FFUART and use 800x600 screen - so we make our own file with board
init stuff. May be colibri_pxa320_evalboard_pin_config[] and
pxafb_mode_info/pxa_fb_mach info structures also can be moved to evalboard
file?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100820/875e20ce/attachment-0001.html>
next prev parent reply other threads:[~2010-08-20 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 12:54 [PATCH] ARM: COLIBRI PXA320: fix UCB1400 irq autoprobing Yuri Ludkevich
2010-08-11 14:33 ` Daniel Mack
2010-08-11 21:26 ` Marek Vasut
2010-08-12 11:48 ` Marek Vasut
2010-08-18 11:50 ` Daniel Mack
2010-08-20 8:34 ` Yuri Ludkevich [this message]
2010-08-20 9:34 ` Marek Vasut
2010-08-20 9:50 ` Daniel Mack
2010-08-11 21:25 ` Marek Vasut
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='AANLkTiktCBNjwN6gfLMv6=BQnGvujbdGPZKk+o+yXqah@mail.gmail.com' \
--to=urx.forever@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).