All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH 1/5] powerpc/qe: Implement QE Pin Multiplexing API
Date: Wed, 17 Dec 2008 19:55:52 +0300	[thread overview]
Message-ID: <20081217165552.GA7307@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <C486295F-74E1-4A24-A8FE-C7BD446A53F5@kernel.crashing.org>

On Wed, Dec 17, 2008 at 10:46:17AM -0600, Kumar Gala wrote:
>
> On Dec 17, 2008, at 9:41 AM, Anton Vorontsov wrote:
>
>> On Wed, Dec 03, 2008 at 10:27:38PM +0300, Anton Vorontsov wrote:
>>> With this API we're able to set a QE pin to the GPIO mode or a  
>>> dedicated
>>> peripheral function.
>>>
>>> The API relies on the fact that QE gpio controllers are registered.  
>>> If
>>> they aren't, the API won't work (gracefully though).
>>>
>>> There is one caveat though: if anybody occupied the node->data  
>>> before us,
>>> or overwrote it, then bad things will happen. Luckily this is all in 
>>> the
>>> platform code that we fully control, so this should never happen.
>>>
>>> I could implement more checks (for example we could create a list of
>>> successfully registered QE controllers, and compare the node->data  
>>> in the
>>> qe_pin_request()), but this is unneeded if nobody is going to do  
>>> silly
>>> things behind our back.
>>>
>>> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
>>> ---
>>
>> Kumar, can you please merge this patch? It is the last patch that
>> holds the FHCI USB driver.
>>
>> Thanks,
>
> Will do.  Can I get you to add kdoc comments for the API functions:

The functions already have kdoc comments (see qe_lib/gpio.c changes).

> +extern struct qe_pin *qe_pin_request(struct device_node *np, int  
> index);
> +extern void qe_pin_free(struct qe_pin *qe_pin);
> +extern void qe_pin_set_gpio(struct qe_pin *qe_pin);
> +extern void qe_pin_set_dedicated(struct qe_pin *pin);

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

  reply	other threads:[~2008-12-17 16:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 19:26 [PATCH 0/5] Few patches for galak/powerpc.git next Anton Vorontsov
2008-12-03 19:27 ` [PATCH 1/5] powerpc/qe: Implement QE Pin Multiplexing API Anton Vorontsov
2008-12-17 15:41   ` Anton Vorontsov
2008-12-17 16:46     ` Kumar Gala
2008-12-17 16:55       ` Anton Vorontsov [this message]
2008-12-17 16:56         ` Kumar Gala
2008-12-17 16:47   ` Kumar Gala
2008-12-03 19:27 ` [PATCH 2/5] powerpc: Implement GPIO driver for simple memory-mapped banks Anton Vorontsov
2008-12-17 16:56   ` Kumar Gala
2008-12-17 17:10     ` Anton Vorontsov
2008-12-03 19:27 ` [PATCH 3/5] powerpc/83xx: Add USB Host/Gadget support for MPC8360E-MDS boards Anton Vorontsov
2008-12-17 16:59   ` Kumar Gala
2008-12-17 17:03     ` Timur Tabi
2008-12-17 17:15     ` Anton Vorontsov
2008-12-17 20:21       ` Kumar Gala
2008-12-03 19:27 ` [PATCH 4/5] powerpc/83xx: Add USB Host support for MPC8360E-RDK boards Anton Vorontsov
2008-12-03 19:27 ` [PATCH 5/5] powerpc/83xx: Fix sparse warnings in mpc836x_mds.c Anton Vorontsov
2008-12-16 18:27   ` Kumar Gala
2008-12-03 19:53 ` [PATCH 0/5] Few patches for galak/powerpc.git next Kumar Gala
2008-12-03 22:28   ` Anton Vorontsov

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=20081217165552.GA7307@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.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 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.