From: Sylvain Munaut <tnt@246tNt.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] powerpc: Add of_platform support for OHCI/Bigendian HC
Date: Tue, 07 Nov 2006 00:28:57 +0100 [thread overview]
Message-ID: <454FC539.2050900@246tNt.com> (raw)
In-Reply-To: <9580D2CE-BD68-440F-A1FD-09E882D93231@kernel.crashing.org>
Kumar Gala wrote:
> On Nov 6, 2006, at 4:35 AM, Nicolas DET wrote:
>
>
>> This patch use of_platform device to probe and install OHCI big
>> endian HC.
>>
>> PS: I did not success to properly inline the file using thrunderbird.
>>
>
> You really copy the USB maintainers on this. Also, why bother with
> the Kconfig for USB_OHCI_HCD_PPC_OF_BE/USB_OHCI_HCD_PPC_OF_LE?
>
I think it's a good idea to use those :
- Just including both when PPC_OF is used is overkill because it makes
all USB
perform useless tests if you never intend to use the LE version for example.
- Using the already defined symbol USB_OHCI_BIG_ENDIAN would force
other ohci user to select BE/LE and they may not want to expose this.
However in this bus glue test :
+ || defined (CONFIG_USB_OHCI_HCD_PPC_OF_LE) \
+ || defined (CONFIG_USB_OHCI_HCD_PPC_OF_BE) \
I would just test for CONFIG_USB_OHCI_HCD_PPC_OF to keep things the same
betwenn all the bus glues. (Sure it would be stupid to select PPC_OF and neither
LE nor BE ...)
But that's just me and if the usb maintainer is ok with it, it's his call.
So otherwise, looks good to me. Haven't tested in hw yet ... I'll report asap.
Sylvain
next prev parent reply other threads:[~2006-11-06 23:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 10:35 [PATCH] powerpc: Add of_platform support for OHCI/Bigendian HC Nicolas DET
2006-11-06 19:24 ` Kumar Gala
2006-11-06 23:28 ` Sylvain Munaut [this message]
2006-11-07 16:46 ` Kumar Gala
2006-11-07 17:32 ` Sylvain Munaut
2006-11-07 17:37 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2006-11-06 11:01 Nicolas DET
2006-11-06 22:55 ` Benjamin Herrenschmidt
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=454FC539.2050900@246tNt.com \
--to=tnt@246tnt.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).