public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Trimarchi <trimarchi@gandalf.sssup.it>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh7786: modify usb setup timeout judgment bug.
Date: Thu, 09 Apr 2009 10:04:21 +0000	[thread overview]
Message-ID: <49DDC825.4080101@gandalf.sssup.it> (raw)
In-Reply-To: <uzleql7ud.wl%morimoto.kuninori@renesas.com>

Hi,

Yoshihiro Shimoda wrote:
> Hi Morimoto-san,
>
> morimoto.kuninori@renesas.com wrote:
>> Dear Michael
>>
>>>>> shimoda san
>>>> Can you change use driver to be able to call peculiar init function ?
>>>> Or Can I do that ?
>>>>   
>>> I will try to provide a patch if you want on 14 of April, or if you 
>>> prefer just start and
>>> send a patch to the reviewer :)
>> Ooops. sorry.
>> My request is to "shimoda san" who created usb driver for SH :)
>>
>
> I think that it is after next month if I try it.
> Because linux-2.6.30 merge window was just closed recently :)
>
I don't have all the data. Look at the code there only the init function 
to be
deferrable. Introduce a platform data it can be usefull but I would like to
know if there are other info that can be passed with the platform data.
Is that the only cpu that needs a specific initialization? Before a patch
maybe we can ask how can we use it?
Just to know:
what is this function sh7786_usb_use_exclock?

for example the s3c2410 define and use a platform data, for port flags or
power control or overun current situation. What can we put in a platform 
data?

Michael



-
> Thanks,
> Yoshihiro Shimoda
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  parent reply	other threads:[~2009-04-09 10:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  4:38 [PATCH] sh7786: modify usb setup timeout judgment bug Kuninori Morimoto
2009-04-09  6:09 ` Nobuhiro Iwamatsu
2009-04-09  6:17 ` Michael Trimarchi
2009-04-09  8:12 ` morimoto.kuninori
2009-04-09  8:29 ` Michael Trimarchi
2009-04-09  8:36 ` morimoto.kuninori
2009-04-09  8:41 ` Michael Trimarchi
2009-04-09  9:09 ` morimoto.kuninori
2009-04-09  9:42 ` Yoshihiro Shimoda
2009-04-09 10:04 ` Michael Trimarchi [this message]
2009-04-09 11:08 ` Yoshihiro Shimoda
2009-04-09 15:09 ` Paul Mundt
2009-04-10  0:27 ` morimoto.kuninori
2009-04-10  1:24 ` Yoshihiro Shimoda
2009-04-10  4:56 ` morimoto.kuninori
2009-04-10 22:22 ` Paul Mundt

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=49DDC825.4080101@gandalf.sssup.it \
    --to=trimarchi@gandalf.sssup.it \
    --cc=linux-sh@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