public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Markus Klotzbücher" <mk@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PXA27x USB device
Date: Fri, 04 May 2007 12:20:37 +0200	[thread overview]
Message-ID: <87bqh0j3ey.fsf@denx.de> (raw)
In-Reply-To: <200705031029.39472.sr@denx.de> (Stefan Roese's message of "Thu, 3 May 2007 10:29:38 +0200")

Hi Stefan,

Stefan Roese <sr@denx.de> writes:

> On Thursday 03 May 2007 09:49, Markus Klotzb?cher wrote:
>> Rodolfo Giometti <giometti@enneenne.com> writes:
>> > I'm looking at drivers/usbdcore_mpc8xx.c for an implementation example
>> > but I don't understand why such support has been put there instead of
>> > cpu/mpc8xx directory.
>> >
>> > Can someone explain to me why? Should I put my PXA27x support also
>> > there?
>>
>> I have no idea why this is so, but it does seem wrong to me. Platform
>> specific code should go into the corresponding cpu/ directory, and so
>> should your pxa support.
>>
>> Any objections?
>
> We had a lengthy discussion about the right places for such drivers a few 
> months ago. IIRC the consent was to put them into the drivers directory 
> (please correct me, if my memory fails me here). But we wanted to structure 
> this directly better. So I would suggest something like:
>
> drivers/usb/device/mpc8xx.c
> drivers/usb/device/pxa27x.c
>
> or even
>
> drivers/usb/gadget/mpc8xx.c
> drivers/usb/gadget/pxa27x.c
>
> to follow the Linux example a little more.
>
> Any comments?

Hmm. Seems reasonable, especially if this structure will be used for all
drivers. But is this the case? I still feel uncomfortable about placing
a cpu dependant host controller driver in a generic driver
directory. Will such a driver be maintained mainly by the USB Custodian
or the respective Architecture Custodian? I would assume the latter.

Best regards

	Markus

--
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany

  parent reply	other threads:[~2007-05-04 10:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 14:05 [U-Boot-Users] PXA27x USB device Rodolfo Giometti
2007-05-02 22:05 ` Bryan O'Donoghue
2007-05-03  7:49 ` Markus Klotzbücher
2007-05-03  8:29   ` Stefan Roese
2007-05-03 10:15     ` Rodolfo Giometti
2007-05-04 10:20     ` Markus Klotzbücher [this message]
2007-05-04 11:47       ` Stefan Roese
2007-05-04 12:31         ` Wolfgang Denk
2007-05-07 11:55         ` Markus Klotzbücher
2007-05-07 12:22           ` Stefan Roese
2007-05-07 13:23             ` Markus Klotzbücher
2007-05-07 15:22               ` Robert Schwebel
2007-05-07 19:58               ` Wolfgang Denk
2007-05-08  6:39                 ` Markus Klotzbücher
2007-05-08  8:47                   ` Rodolfo Giometti
2007-05-08 10:04                     ` Markus Klotzbücher
2007-05-08 12:49                       ` Rodolfo Giometti
2007-05-08 14:14                         ` Loeliger Jon-LOELIGER

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=87bqh0j3ey.fsf@denx.de \
    --to=mk@denx.de \
    --cc=u-boot@lists.denx.de \
    /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