From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Govindraj.R" <govindraj.raja@ti.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH v5] OMAP UART: Add omap-serial driver support.
Date: Wed, 27 Jan 2010 11:33:16 -0800 [thread overview]
Message-ID: <20100127193316.GF23505@atomide.com> (raw)
In-Reply-To: <87aavzuzwf.fsf@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [100127 11:08]:
> Tony Lindgren <tony@atomide.com> writes:
>
> > * Kevin Hilman <khilman@deeprootsystems.com> [100127 10:05]:
> >> Tony Lindgren <tony@atomide.com> writes:
> >>
> >> > * Kevin Hilman <khilman@deeprootsystems.com> [100127 09:46]:
> >> >> Tony Lindgren <tony@atomide.com> writes:
> >> >>
> >> >> [...]
> >> >>
> >> >> >
> >> >> > Do you have the board related patches somewhere so people can
> >> >> > actually test this driver?
> >> >> >
> >> >>
> >> >> Tony, the board/platform related patches are in my pm-wip/uart branch
> >> >> as part of the conversion of that code to hwmod/omap_device.
> >> >>
> >> >> This patch on top of that branch is working fine, at least for
> >> >> basic console.
> >> >
> >> > OK. What's the dependency to the PM branch with these UART
> >> > patches?
> >>
> >> The driver itself has no dependencies.
> >>
> >> But the platform changes and conversion to hwmod/omap_device have all
> >> been done on top of the PM branch + various ongoing hwmod/omap_device
> >> patches.
> >
> > Sounds like we should do all the hwmod conversion patches against the
> > mainline nowadays to cut down the dependencies. If there are some
> > dependencies still to PM branch, those should be patched away ASAP.
>
> Agreed, and already done. I'm collecting the various hwmod,
> omap_device conversion patches floating around and have them in a
> branch of my PM tree based on mainline.
>
> However, so far I have only been testing them when combined with the
> rest of the PM branch.
OK cool.
> > Adding new device drivers should not have any dependencies except
> > the mainline kernel :)
>
> In general that's true. But for all new drivers, I think we need to
> require that they use hwmod + omap_device so we don't have to do that
> part twice. Since the hwmod + omap_device stuff has a little ways to
> go, there will be some out-of-tree dependencies.
Sounds fair to me as long as we work out any out-of-mainline-tree
dependencies for adding drivers.
Tony
next prev parent reply other threads:[~2010-01-27 19:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 9:56 [PATCH v5] OMAP UART: Add omap-serial driver support Govindraj.R
2010-01-27 17:25 ` Tony Lindgren
2010-01-27 17:49 ` Kevin Hilman
2010-01-27 17:57 ` Tony Lindgren
2010-01-27 18:07 ` Kevin Hilman
2010-01-27 18:18 ` Tony Lindgren
2010-01-27 19:10 ` Kevin Hilman
2010-01-27 19:33 ` Tony Lindgren [this message]
2010-02-10 14:39 ` Govindraj
2010-02-10 17:25 ` Tony Lindgren
2010-01-27 18:20 ` Kevin Hilman
2010-01-27 19:37 ` Kevin Hilman
2010-01-28 3:22 ` Olof Johansson
2010-02-04 15:09 ` Govindraj.R
2010-02-04 15:28 ` Olof Johansson
2010-02-04 15:45 ` Govindraj.R
2010-02-04 17:46 ` Kevin Hilman
2010-02-04 20:37 ` Olof Johansson
2010-02-04 20:33 ` Olof Johansson
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=20100127193316.GF23505@atomide.com \
--to=tony@atomide.com \
--cc=govindraj.raja@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox