All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aguirre, Sergio" <saaguirre@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: [RFC part1/2 merge][PATCH 06/10] omap3: serial: Fix uart4 handling for 3630
Date: Mon, 8 Mar 2010 10:57:16 -0600	[thread overview]
Message-ID: <A24693684029E5489D1D202277BE894453D68E0E@dlee02.ent.ti.com> (raw)
In-Reply-To: <87fx4awybe.fsf@deeprootsystems.com>



From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
Sent: Monday, March 08, 2010 10:52 AM
> "Aguirre, Sergio" <saaguirre@ti.com> writes:
> 
> >> -----Original Message-----
> >> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> >> owner@vger.kernel.org] On Behalf Of Aguirre, Sergio
> >> Sent: Friday, March 05, 2010 5:12 PM
> >> To: Kevin Hilman
> >> Cc: linux-omap@vger.kernel.org
> >> Subject: RE: [RFC part1/2 merge][PATCH 06/10] omap3: serial: Fix uart4
> >> handling for 3630
> >>
> >>
> >> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
> >> Sent: Friday, March 05, 2010 4:38 PM
> >>
> >> <snip>
> >>
> >> > > @@ -694,6 +698,10 @@ void __init omap_serial_early_init(void)
> >> > >
> >> > >  		if (cpu_is_omap44xx())
> >> > >  			p->irq += 32;
> >> > > +
> >> > > +		/* IRQ for UART4 in omap3630 is 80 */
> >> > > +		if (cpu_is_omap3630() && (i == 3))
> >> > > +			p->irq = 80;
> >> >
> >> > Should add a symbolic name to irqs.h and use it here, instead
> >> > of hard-coded constant.
> >>
> >> Sounds like a nice idea! Thanks!
> >>
> >> I'll update the patchset and resend.
> >
> > Actually, I have been thinking on a patch to remove all magic numbering,
> also for OMAP4... I'll think about it and include it in the next version.
> 
> Don't spend too much time on this.
> 
> Soon, this serial core will be converted over to hwmod (RFC patches
> already posted) so all the IRQ and base address stuff will be
> handled by hwmod.

Hmm... ok, thanks for clarifying that.

Then I won't touch anything that my original series doesn't cover.
I'll just use this define for 3630 as you originally suggested here,
and resend.

Regards,
sergio

> 
> Kevin
> 
> 


  reply	other threads:[~2010-03-08 16:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 14:18 [RFC part1/2 merge][PATCH 00/10] omap2/3/4: uart4 fixes + zoom2/3 changes Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 01/10] OMAP3: serial: Check for zero-based physical addr Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 02/10] omap2/3/4: serial: Remove condition for getting uart4_phys Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 03/10] ARM: OMAP3630: PRCM: Add UART4 control bits Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 04/10] OMAP clock: Add uart4_ick/fck definitions for 3630 Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 05/10] OMAP3: PRCM: Consider UART4 for 3630 chip in prcm_setup_regs Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 06/10] omap3: serial: Fix uart4 handling for 3630 Sergio Aguirre
2010-03-05 22:37   ` Kevin Hilman
2010-03-05 23:11     ` Aguirre, Sergio
2010-03-08 16:44       ` Aguirre, Sergio
2010-03-08 16:52         ` Kevin Hilman
2010-03-08 16:57           ` Aguirre, Sergio [this message]
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 07/10] omap3: zoom2/3 / 3630sdp: Don't init always all uarts Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 08/10] omap3: 3630sdp: Explicitly enable all UARTs Sergio Aguirre
2010-03-03 14:35   ` Aguirre, Sergio
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 09/10] omap3: zoom 2/3: Change debugboard serial port id Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 10/10] omap3: zoom2/3: Register only 1 8250 port Sergio Aguirre
2010-03-05 22:40 ` [RFC part1/2 merge][PATCH 00/10] omap2/3/4: uart4 fixes + zoom2/3 changes Kevin Hilman

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=A24693684029E5489D1D202277BE894453D68E0E@dlee02.ent.ti.com \
    --to=saaguirre@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.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 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.