From: Tony Lindgren <tony@atomide.com>
To: Sutharsan R <sutharsan.ram@gmail.com>
Cc: greg@kroah.com, linux-arm@vger.kernel.org, srmt@cypress.com,
david.cross@cypress.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] adding gpmc configuration functions, west bridge related
Date: Tue, 21 Dec 2010 12:46:51 -0800 [thread overview]
Message-ID: <20101221204651.GM5829@atomide.com> (raw)
In-Reply-To: <AANLkTi==X9maghSd3YwG6g3cQek3gV9-3Fx8W+n_zLmp@mail.gmail.com>
* Sutharsan R <sutharsan.ram@gmail.com> [101220 18:41]:
> This patch adds and exports gpmc configuration functions.
> 'gpmc' configuration functions will be used by
> westbridge device controller driver in staging tree.
> This patch is part of the work to get westbridge device controller driver
> out of staging tree.
Looks good in general..
> +EXPORT_SYMBOL(cywb_pnand_platform_retime);
But this you should not need. I know tusb6010 is
still doing that, but you can pass it in the platform_data
and then there's no need to export it.
Then in your driver you can do:
if (xxxxx->retime)
xxxxx->retime(123);
That way the driver will stay generic. The set_power
functions are doing that in drivers/usb/musb if you
need examples.
Also, this will need a slight update based on Adrian Hunter's
patch "OMAP2/3: GPMC: put sync_clk value in picoseconds
instead of nanosecond" that I'll be queuing.
Regards,
Tony
next prev parent reply other threads:[~2010-12-21 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 2:42 [PATCH] adding gpmc configuration functions, west bridge related Sutharsan R
2010-12-21 4:11 ` Greg KH
2010-12-21 20:46 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-13 23:23 Sutharsan Ramamoorthy
2011-01-13 23:44 ` Greg KH
2011-01-14 20:01 ` Tony Lindgren
[not found] <AANLkTim-1+CwW50mPwi6DnQDF680fxjJms7JrEPqsqkv@mail.gmail.com>
2011-01-12 21:36 ` Greg KH
2011-01-12 21:37 ` Greg KH
2010-12-17 0:33 Sutharsan
2010-12-17 0:41 ` Greg KH
2010-12-15 19:57 Sutharsan
2010-12-15 20:10 ` Greg KH
2010-12-15 22:11 ` Sutharsan
2010-12-15 22:18 ` Greg KH
2010-12-15 23:03 ` Sutharsan
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=20101221204651.GM5829@atomide.com \
--to=tony@atomide.com \
--cc=david.cross@cypress.com \
--cc=greg@kroah.com \
--cc=linux-arm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=srmt@cypress.com \
--cc=sutharsan.ram@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox