I'm puzzled. Could someone point me to some real code where cell-
index
is used as a pointer into some global data. Sorry for my ignorance.
http://ozlabs.org/pipermail/linuxppc-dev/2008-June/057254.html
Yep, I saw that it's used for I2C (and SPI). But "cell-index" is also
defined for networ
Kumar Gala wrote:
>
I'm puzzled. Could someone point me to some real code where cell-index
is used as a pointer into some global data. Sorry for my ignorance.
>>>
>>> http://ozlabs.org/pipermail/linuxppc-dev/2008-June/057254.html
>>
>> Yep, I saw that it's used for I2C (and SPI). But
On Thu, 5 Jun 2008 08:22:00 +0200, Stefan Roese wrote:
> On Thursday 05 June 2008, Sean MacLennan wrote:
> > On Wed, 4 Jun 2008 22:05:55 -0500
> >
> > Josh Boyer <[EMAIL PROTECTED]> wrote:
> > > I'm not proposing we remove that. I'm just proposing that it can be
> > > derived from something other
hi,
I'm really sorry if this message disturb anybody, however..
=
10th Real-Time Linux Workshop
October 29 November 1, 2008 University of Guadalajara Centro
Universitario
del Norte Carretera Federal # 23 Km 191, C.P.
This patch enables the IBM I2C driver for all PPC4xx variants by adding
"ibm,iic" to the compatible list. This way all currently available
arch/powerpc 4xx ports can make use of this driver without any changes.
Additionally all "other" compatible entries are removed since they are
not needed anymor
Jesse Barnes wrote:
Now, in hindsight, using a PIO write set & test flag approach in
writeX/spin_unlock (ala powerpc) might have been a better approach, but iirc
that never came up in the discussion, probably because we were focused on PCI
posting and not uncached vs. cached ordering.
Hi Jess
On Thu, 2008-06-05 at 10:40 +0200, Jes Sorensen wrote:
> Jesse Barnes wrote:
> > Now, in hindsight, using a PIO write set & test flag approach in
> > writeX/spin_unlock (ala powerpc) might have been a better approach, but
> > iirc
> > that never came up in the discussion, probably because we wer
On Thursday 05 June 2008, Jean Delvare wrote:
> > > Maybe it is time to remove the index, or maybe we should go back to
> > > using both a static and the index. But at the time we decided to
> > > enforce an index.
> >
> > So what should we do now? Currently I2C doesn't work at all on 4xx since
> >
[NAND] driver extension to support NAND on TQM85xx modules
This patch extends the FSL UPM NAND driver from Anton Vorontsov to
support NAND on the TQM85xx modules. Unfortunately, the hardware does
not support the R/B pins of the NAND chip and therefore the specified
maximum delay time must used. It
Hello,
it follows version 2 of patches adding support for the TQM8548 modules
from TQ Components (http://www.tqc.de) and furthermore fixing some
issues with other TQM85xx modules.
They are already based on Kumar's powerpc Linux tree (linux-2.6-galak).
The NAND support requires the patch with the
Some TQM85xx boards could be equipped with up to 1 GiB (NOR) flash
memory and therefore a modified memory map is required and setup by
the board loader. This patch adds an appropriate DTS file.
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/tqm8548-bigflash.dts |
[POWERPC] 85xx: add board support for the TQM8548 modules
This patch adds support for the TQM8548 modules from TQ-Components
GmbH (http://www.tqc.de).
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/Makefile |1
arch/powerpc/boot/dts/tqm8548.dts
Add local bus nodes for Flash and CAN to tqm8560.dts
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/tqm8560.dts | 65 ++
1 file changed, 65 insertions(+)
Index: linux-2.6-galak/arch/powerpc/boot/dts/tqm8560.dts
=
Like for the TQM5200, the vendor prefix "tqc," is now used for all
TQM85xx modules from TQ-Components GmbH (http://www.tqc.de) in the
corresponding DTS files.
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/tqm8540.dts |4 ++--
arch/powerpc/boot/dts/t
Scott Wood <[EMAIL PROTECTED]> wrote:
> int tmp;
>
> asm volatile("addi %1, %2, -1;"
> "andc %1, %2, %1;"
> "cntlzw %1, %1;"
> "subfic %0, %1, 31" : "=r" (j), "=&r" (tmp) : "r" (i));
Registers are usually assumed to be 'long' in size, so I'd recommend using
On Wed, Jun 04, Linus Torvalds wrote:
> Another week, another batch of mostly pretty small fixes. Hopefully the
> regression list is shrinking, and we've fixed at least a couple of the
> oopses on Arjan's list.
SATA on a dualcore G5 is broken, it happend between
c3b25b32e8bef526cca748e1ba023c6b
On Thu, 5 Jun 2008 10:10:53 +0200
Stefan Roese <[EMAIL PROTECTED]> wrote:
> This patch enables the IBM I2C driver for all PPC4xx variants by adding
> "ibm,iic" to the compatible list. This way all currently available
> arch/powerpc 4xx ports can make use of this driver without any changes.
> Addi
On Thu, 5 Jun 2008 10:45:42 +0200
Stefan Roese <[EMAIL PROTECTED]> wrote:
> On Thursday 05 June 2008, Jean Delvare wrote:
> > > > Maybe it is time to remove the index, or maybe we should go back to
> > > > using both a static and the index. But at the time we decided to
> > > > enforce an index.
>
On Thu, 5 Jun 2008, Olaf Hering wrote:
> On Wed, Jun 04, Linus Torvalds wrote:
>
> > Another week, another batch of mostly pretty small fixes. Hopefully the
> > regression list is shrinking, and we've fixed at least a couple of the
> > oopses on Arjan's list.
>
> SATA on a dualcore G5 is broken
bump? :)
On Mon, 17 Mar 2008 14:48:23 +0100, Imre Kaloz <[EMAIL PROTECTED]> wrote:
Signed-off-by: Imre Kaloz <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/taishan.dts | 29 +++-
arch/powerpc/configs/taishan_defconfig | 79
+++-
2 files changed, 1
On Thu, 5 Jun 2008 13:24:36 +0200
Olaf Hering <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 04, Linus Torvalds wrote:
>
> > Another week, another batch of mostly pretty small fixes. Hopefully the
> > regression list is shrinking, and we've fixed at least a couple of the
> > oopses on Arjan's list.
>
> And the patch I'm finding successful is below: I won't sign it off,
> for all I know it's reverting part of what Alan is trying to achieve;
> but I expect it'll help towards the right fix.
Its the right fix
ata_sff_check_altstatus() is a routine which does the altstatus
check and may o
On Thu, 05 Jun 2008 14:50:41 +0200
"Imre Kaloz" <[EMAIL PROTECTED]> wrote:
> bump? :)
It won't apply anymore, but the fixups are trivial. I can do that if
Stefan acks the changes.
josh
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozla
On Jun 5, 2008, at 4:05 AM, Wolfgang Grandegger wrote:
[POWERPC] 85xx: add board support for the TQM8548 modules
This patch adds support for the TQM8548 modules from TQ-Components
GmbH (http://www.tqc.de).
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/Makefile
Fix G5 SATA irq 18: nobody cared, reported on -rc5 by Olaf Hering:
fixlet to a57c1bade5a0ee5cd8b74502db9cbebb7f5780b2 libata-sff:
Fix oops reported in kerneloops.org for pnp devices with no ctl
Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
Acked-by: Alan Cox <[EMAIL PROTECTED]>
---
drivers
On Jun 5, 2008, at 4:09 AM, Wolfgang Grandegger wrote:
Some TQM85xx boards could be equipped with up to 1 GiB (NOR) flash
memory and therefore a modified memory map is required and setup by
the board loader. This patch adds an appropriate DTS file.
Signed-off-by: Wolfgang Grandegger <[EMAIL PR
On Jun 5, 2008, at 4:13 AM, Wolfgang Grandegger wrote:
Like for the TQM5200, the vendor prefix "tqc," is now used for all
TQM85xx modules from TQ-Components GmbH (http://www.tqc.de) in the
corresponding DTS files.
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts
The "ndfc-chip" device doesn't need any resources. All resources
are handled by the "ndfc-nand" device. Registering the same memory
resource twice causes "cat /proc/iomem" to go into an infinite loop
displaying NDFC memory addresses.
Signed-off-by: Valentine Barshak <[EMAIL PROTECTED]>
---
arch/p
This patch add a check to the PPC4xx PCIe driver to detect if the port
is disabled via the device-tree. This is needed for the AMCC Canyonlands
board which has an option to either select 2 PCIe ports or 1 PCIe port
and one SATA port. The SATA port and the 1st PCIe port pins are multiplexed
so we ca
On Thursday 05 June 2008, Valentine Barshak wrote:
> The "ndfc-chip" device doesn't need any resources. All resources
> are handled by the "ndfc-nand" device. Registering the same memory
> resource twice causes "cat /proc/iomem" to go into an infinite loop
> displaying NDFC memory addresses.
>
> Si
On Thu, Jun 05, Hugh Dickins wrote:
> Fix G5 SATA irq 18: nobody cared, reported on -rc5 by Olaf Hering:
> fixlet to a57c1bade5a0ee5cd8b74502db9cbebb7f5780b2 libata-sff:
> Fix oops reported in kerneloops.org for pnp devices with no ctl
>
> Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
> Ack
This commit (patch omitted due to size) is sitting in my local tree:
commit 0d7efc1e80fc262bcc507a605482c5681e3f082a
Author: Josh Boyer <[EMAIL PROTECTED]>
Date: Thu Jun 5 09:46:17 2008 -0500
ppc/4xx: Remove 4xx support from arch/ppc
Remove support for PPC 403, 405, and 440 process
From: Dave Liu <[EMAIL PROTECTED]>
The e500 core enter DOZE/NAP power-saving modes when the core go to
cpu_idle routine.
The power management default running mode is DOZE, If the user
echo 1 > /proc/sys/kernel/powersave-nap
the system will change to NAP running mode.
---
I'm post this for rev
On Tue, Jun 03, 2008 at 12:07:49PM +0200, Marc Pignat wrote:
> Hi all!
>
> On Friday 23 May 2008, Anton Vorontsov wrote:
> > get_ro() callback must return values >= 0 for its logical state, and
> ...
> > static void pxamci_set_ios(struct mmc_host *mmc, struct mmc_ios *ios)
> > diff --git a/includ
On Thu, Jun 5, 2008 at 8:52 AM, Josh Boyer <[EMAIL PROTECTED]> wrote:
> This commit (patch omitted due to size) is sitting in my local tree:
>
> commit 0d7efc1e80fc262bcc507a605482c5681e3f082a
> Author: Josh Boyer <[EMAIL PROTECTED]>
> Date: Thu Jun 5 09:46:17 2008 -0500
>
>ppc/4xx: Remove 4x
On Thu, 5 Jun 2008 09:11:48 -0600
"Grant Likely" <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 5, 2008 at 8:52 AM, Josh Boyer <[EMAIL PROTECTED]> wrote:
> > This commit (patch omitted due to size) is sitting in my local tree:
> >
> > commit 0d7efc1e80fc262bcc507a605482c5681e3f082a
> > Author: Josh Boye
Josh Boyer wrote:
> From a device tree perspective, index and cell-index are both
> incorrect. The IIC macros don't share register blocks with anything,
> are enumerated as unique instances per macro in the device tree, and
> should be able to be distinguished by "regs" and/or unit address.
I th
Josh Boyer wrote:
> seems to be a more distinct definition of what this is. But I have no
> idea how well that would go over, and it would probably need to be
> changed in all the fsl boards as well.
Which would end up breaking backwards compatibility with older device trees.
Like I said earlier
Stefan Roese wrote:
> So what should we do now? Currently I2C doesn't work at all on 4xx since the
> driver expects the "index" property and no dts sets this property. Personally
> I would like to move to using cell-index here, since this seems to be more
> common. But I could also life with re
On Thu, Jun 5, 2008 at 9:13 AM, Timur Tabi <[EMAIL PROTECTED]> wrote:
> Josh Boyer wrote:
>
>> From a device tree perspective, index and cell-index are both
>> incorrect. The IIC macros don't share register blocks with anything,
>> are enumerated as unique instances per macro in the device tree, a
Grant Likely wrote:
> if you need explicit indexing then use an alias. My opinion however
> is that explicit indexing is unnecessary and is just an artifact of
> current i2c subsystem internals. There is already enough information
> in the device tree to match i2c devices with i2c busses without
Hi Timur,
> In situations where it doesn't matter which I2C bus is #1 and which one is #2,
> then I think the code should just initialize idx based on the order the nodes
> are found in the tree.
>
> In situations where it does matter, then we should use cell-index.
that's what I did in i2c-cpm,
I think we should just expand the definition of cell-index to include
standard
device enumeration for when it's needed. The original definition is
too
limited, IMHO.
nak
if you need explicit indexing then use an alias. My opinion however
is that explicit indexing is unnecessary and is just
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:linuxppc-dev-
> [EMAIL PROTECTED] On Behalf Of Josh
Boyer
> Sent: Thursday, June 05, 2008 8:19 AM
> To: Grant Likely
> Cc: linuxppc-dev@ozlabs.org; Paul Mackerras
> Subject: Re: 4xx support in arch/ppc is going away Real Soon Now
>
> O
Jochen Friedrich wrote:
> Hi Timur,
>
>> In situations where it doesn't matter which I2C bus is #1 and which one is
>> #2,
>> then I think the code should just initialize idx based on the order the nodes
>> are found in the tree.
>>
>> In situations where it does matter, then we should use cell-i
Hi Grant,
> if you need explicit indexing then use an alias. My opinion however
> is that explicit indexing is unnecessary and is just an artifact of
> current i2c subsystem internals. There is already enough information
> in the device tree to match i2c devices with i2c busses without
> resorti
if you need explicit indexing then use an alias. My opinion however
is that explicit indexing is unnecessary and is just an artifact of
current i2c subsystem internals. There is already enough information
in the device tree to match i2c devices with i2c busses without
resorting to indexes.
Not
On Wed, 2008-06-04 at 21:14 -0500, Josh Boyer wrote:
> On Wed, 04 Jun 2008 17:26:44 -0500
> Jerone Young <[EMAIL PROTECTED]> wrote:
>
> > Taken from the PowerPC ISA BookIII-E specifies that DBCR0 is different
> > for all others that are not ppc405 chips. So I have now chnaged the
> > conditional t
On Thu, Jun 5, 2008 at 9:52 AM, Jochen Friedrich <[EMAIL PROTECTED]> wrote:
> Hi Grant,
>
>> if you need explicit indexing then use an alias. My opinion however
>> is that explicit indexing is unnecessary and is just an artifact of
>> current i2c subsystem internals. There is already enough infor
Update: Consolidated dbcr1 & dbcr2 under one define.
Taken from the PowerPC ISA BookIII-E specifies that DBCR0 is different
for all others that are not ppc405 chips. So I have now chnaged the
conditional to reflect this. Also added definitions needed for DBCR1 &
DBCR2.
Signed-off-by: Jerone Youn
On Thursday 05 June 2008, Anton Vorontsov wrote:
> On Tue, Jun 03, 2008 at 12:07:49PM +0200, Marc Pignat wrote:
> > Hi all!
> >
> > On Friday 23 May 2008, Anton Vorontsov wrote:
> > > get_ro() callback must return values >= 0 for its logical state, and
> > ...
> > > static void pxamci_set_ios(str
On Thu, Jun 5, 2008 at 9:43 AM, Timur Tabi <[EMAIL PROTECTED]> wrote:
> Grant Likely wrote:
>
>> if you need explicit indexing then use an alias. My opinion however
>> is that explicit indexing is unnecessary and is just an artifact of
>> current i2c subsystem internals. There is already enough i
Segher Boessenkool wrote:
> Sounds to me like both simply need to use adapter->nr.
How can a non-I2C driver get the adapter structure for another driver that is an
I2C driver?
> For access to
> Linux-internal data structures (and that is what this "index" is), you
> shouldn't have to go via the
On Thu, Jun 5, 2008 at 9:50 AM, Timur Tabi <[EMAIL PROTECTED]> wrote:
> Jochen Friedrich wrote:
>> Hi Timur,
>>
>>> In situations where it doesn't matter which I2C bus is #1 and which one is
>>> #2,
>>> then I think the code should just initialize idx based on the order the
>>> nodes
>>> are foun
Grant Likely wrote:
> That is still Linux internal artifacts leaking out. Don't encode that
> data into the device tree.
The I2C bus number is *not* an internal artifact. On Freescale parts, the one
I2C adapter is specifically designated I2C1, and the 2nd one is specifically
designated I2C2. T
Here is v3. I'm out of ideas if you won't like it. :-)
v3:
- Now these bindings are using bus notifiers chain, thus we adhere to the
spi bus.
By the way, this scheme (IMO) looks good for I2C devices which needs
platform_data extracted from the device tree too (Cc'ing Jochen).
- Plus change
Grant Likely wrote:
> [EMAIL PROTECTED] {
> #size-cells = <1>;
> #address-cells = <1>;
> ranges = <0 0xe 0x1000>;
> [EMAIL PROTECTED] {
> cell-index = <0>;
> regs = <0 0x100>;
> }
> [EMAIL PROTECTED] {
>
On Thu, 05 Jun 2008 11:13:23 -0500
Timur Tabi <[EMAIL PROTECTED]> wrote:
> Grant Likely wrote:
>
> > That is still Linux internal artifacts leaking out. Don't encode that
> > data into the device tree.
>
> The I2C bus number is *not* an internal artifact. On Freescale parts, the one
> I2C adap
Hi Timur,
> It's a little late for that. I'm okay with coming up with a new property to
> provide system-level indexing, but it needs to be the same property name for
> each type of device. I don't want linux,i2c-index and linux,dma-index and
> linux,ssi-index, etc. I also don't understand why
On Jun 5, 2008, at 10:56 AM, Jerone Young wrote:
Update: Consolidated dbcr1 & dbcr2 under one define.
Taken from the PowerPC ISA BookIII-E specifies that DBCR0 is different
for all others that are not ppc405 chips. So I have now chnaged the
conditional to reflect this. Also added definitions n
On Thu, Jun 05, 2008 at 11:09:16AM -0500, Timur Tabi wrote:
> The fabric driver doesn't have access to any I2C structures when it starts
> looking for the codec driver. The fabric driver is like an OF platform
> driver,
> in that it's OF-aware and machine-specific. By parsing the device tree (wh
On Thu, Jun 5, 2008 at 10:22 AM, Jochen Friedrich <[EMAIL PROTECTED]> wrote:
> Hi Timur,
>
>> It's a little late for that. I'm okay with coming up with a new property to
>> provide system-level indexing, but it needs to be the same property name for
>> each type of device. I don't want linux,i2c-
Josh Boyer wrote:
> And it does. It does so by the unique "regs" properties and
> unit-names. You can assign the index that the i2c subsystem needs
> based on probe order, like I already said.
The probe order is not sufficient on platforms that specifically enumerate their
I2C (or whatever) dev
On Thu, Jun 5, 2008 at 10:18 AM, Timur Tabi <[EMAIL PROTECTED]> wrote:
> Grant Likely wrote:
>
>> [EMAIL PROTECTED] {
>> #size-cells = <1>;
>> #address-cells = <1>;
>> ranges = <0 0xe 0x1000>;
>> [EMAIL PROTECTED] {
>> cell-index = <0>;
>>
On Thu, Jun 5, 2008 at 10:25 AM, Timur Tabi <[EMAIL PROTECTED]> wrote:
> Josh Boyer wrote:
>
>> And it does. It does so by the unique "regs" properties and
>> unit-names. You can assign the index that the i2c subsystem needs
>> based on probe order, like I already said.
>
> The probe order is not
Grant Likely wrote:
> 2) for i2c purposes, explicit enumeration is not needed or desired.
> All the necessary data is already present in the device tree in that
> i2c device nodes are children of i2c bus nodes. The i2c bus numbers
> should be dynamically assigned.
NACK. For ASoC driver, they ca
On Thu, Jun 5, 2008 at 10:16 AM, Anton Vorontsov
<[EMAIL PROTECTED]> wrote:
> Here is v3. I'm out of ideas if you won't like it. :-)
>
> v3:
> - Now these bindings are using bus notifiers chain, thus we adhere to the
> spi bus.
>
> By the way, this scheme (IMO) looks good for I2C devices which ne
On Thu, Jun 05, 2008 at 11:44:51AM +0100, David Howells wrote:
> Scott Wood <[EMAIL PROTECTED]> wrote:
>
> > int tmp;
> >
> > asm volatile("addi %1, %2, -1;"
> > "andc %1, %2, %1;"
> > "cntlzw %1, %1;"
> > "subfic %0, %1, 31" : "=r" (j), "=&r" (tmp) : "r" (i
For the sake of safety, document that drivers should return only
1 or 0 from the get_ro() and get_cd() callbacks. Also document context
in which these callbacks should be executed.
wbsd driver modified to comply with this requirement.
Also, fix mmc_spi driver to not return raw values from the pla
Like for the TQM5200, the vendor prefix "tqc," is now used for all
TQM85xx modules from TQ-Components GmbH (http://www.tqc.de) in the
corresponding DTS files.
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/tqm8540.dts |4 ++--
arch/powerpc/boot/dts/tqm854
This patch adds support for the TQM8548 modules from TQ-Components
GmbH (http://www.tqc.de).
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/Makefile |1
arch/powerpc/boot/dts/tqm8548.dts | 365 +
arch/powerpc/boot/wrapper
Some TQM85xx boards could be equipped with up to 1 GiB (NOR) flash
memory and therefore a modified memory map is required and setup by
the board loader. This patch adds an appropriate DTS file.
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/tqm8548-bigflash.dts |
Add local bus nodes for Flash and CAN to the DTS file of the TQM8650 module.
Signed-off-by: Wolfgang Grandegger <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/tqm8560.dts | 65 ++
1 file changed, 65 insertions(+)
Index: linux-2.6-galak/arch/powerpc/boot/dts/t
Kumar Gala wrote:
>
> On Jun 5, 2008, at 4:05 AM, Wolfgang Grandegger wrote:
>
>> [POWERPC] 85xx: add board support for the TQM8548 modules
>>
>> This patch adds support for the TQM8548 modules from TQ-Components
>> GmbH (http://www.tqc.de).
>>
>> Signed-off-by: Wolfgang Grandegger <[EMAIL PROTEC
On Thu, Jun 05, 2008 at 10:45:17AM -0600, Grant Likely wrote:
> On Thu, Jun 5, 2008 at 10:16 AM, Anton Vorontsov
> <[EMAIL PROTECTED]> wrote:
> > Here is v3. I'm out of ideas if you won't like it. :-)
> >
> > v3:
> > - Now these bindings are using bus notifiers chain, thus we adhere to the
> > spi
On Thu, Jun 5, 2008 at 11:27 AM, Anton Vorontsov
<[EMAIL PROTECTED]> wrote:
> On Thu, Jun 05, 2008 at 10:45:17AM -0600, Grant Likely wrote:
>> On Thu, Jun 5, 2008 at 10:16 AM, Anton Vorontsov
>> <[EMAIL PROTECTED]> wrote:
>> > Here is v3. I'm out of ideas if you won't like it. :-)
>> >
>> > v3:
>>
Scott Wood wrote:
> No, it's not. It can determine that it's at address 0x4f on the i2c bus
> at 0xe0003100. This is exactly how the ethernet phy lookup is done.
But how does the fabric driver know whether e0003100 is I2C1 or I2C2?
And how does the codec driver, which sees only I2C information
On Thu, Jun 05, 2008 at 11:36:09AM -0600, Grant Likely wrote:
> On Thu, Jun 5, 2008 at 11:27 AM, Anton Vorontsov
> <[EMAIL PROTECTED]> wrote:
> > On Thu, Jun 05, 2008 at 10:45:17AM -0600, Grant Likely wrote:
> >> On Thu, Jun 5, 2008 at 10:16 AM, Anton Vorontsov
> >> <[EMAIL PROTECTED]> wrote:
> >>
Timur Tabi wrote:
Scott Wood wrote:
No, it's not. It can determine that it's at address 0x4f on the i2c bus
at 0xe0003100. This is exactly how the ethernet phy lookup is done.
But how does the fabric driver know whether e0003100 is I2C1 or I2C2?
It shouldn't have to care.
And how does t
On Thu, Jun 5, 2008 at 12:00 PM, Anton Vorontsov
<[EMAIL PROTECTED]> wrote:
> On Thu, Jun 05, 2008 at 11:36:09AM -0600, Grant Likely wrote:
>> On Thu, Jun 5, 2008 at 11:27 AM, Anton Vorontsov
>> <[EMAIL PROTECTED]> wrote:
>> > Well, I mentioned the usb_add_hcd()-alike approach for the mmc_spi
>> >
On Thu, 05 Jun 2008 11:25:23 -0500
Timur Tabi <[EMAIL PROTECTED]> wrote:
> Josh Boyer wrote:
>
> > And it does. It does so by the unique "regs" properties and
> > unit-names. You can assign the index that the i2c subsystem needs
> > based on probe order, like I already said.
>
> The probe orde
On Thu, Jun 05, 2008 at 12:18:56PM -0600, Grant Likely wrote:
> On Thu, Jun 5, 2008 at 12:00 PM, Anton Vorontsov
> <[EMAIL PROTECTED]> wrote:
> > On Thu, Jun 05, 2008 at 11:36:09AM -0600, Grant Likely wrote:
> >> On Thu, Jun 5, 2008 at 11:27 AM, Anton Vorontsov
> >> <[EMAIL PROTECTED]> wrote:
> >>
Josh Boyer wrote:
> I don't understand this statement. Are your I2C macros hot-pluggable?
> Can you dynamically add/remove an I2C engine on your hardware somehow?
> Are you mucking about with the DTB and randomly moving around the I2C
> node blobs so they probe order differs from boot to boot?
>
On Thu, 05 Jun 2008 13:35:18 -0500
Timur Tabi <[EMAIL PROTECTED]> wrote:
> Josh Boyer wrote:
>
> > I don't understand this statement. Are your I2C macros hot-pluggable?
> > Can you dynamically add/remove an I2C engine on your hardware somehow?
> > Are you mucking about with the DTB and randomly
On Thu, Jun 5, 2008 at 12:31 PM, Anton Vorontsov
<[EMAIL PROTECTED]> wrote:
> On Thu, Jun 05, 2008 at 12:18:56PM -0600, Grant Likely wrote:
>> On Thu, Jun 5, 2008 at 12:00 PM, Anton Vorontsov
>> <[EMAIL PROTECTED]> wrote:
>> > On Thu, Jun 05, 2008 at 11:36:09AM -0600, Grant Likely wrote:
>> >> On T
On Thu, Jun 5, 2008 at 12:27 PM, Josh Boyer <[EMAIL PROTECTED]> wrote:
> On Thu, 05 Jun 2008 11:25:23 -0500
> Timur Tabi <[EMAIL PROTECTED]> wrote:
>
>> Josh Boyer wrote:
>>
>> > And it does. It does so by the unique "regs" properties and
>> > unit-names. You can assign the index that the i2c sub
On Thu, 5 Jun 2008 12:46:39 -0600
"Grant Likely" <[EMAIL PROTECTED]> wrote:
> > (And I'm talking about I2C, not DMA. I don't care about DMA because
> > this conversation will go off into the weeds if we start talking about
> > cell-index and every possible device out there.)
>
> I need to disagr
===
--- /dev/null
+++ linux-2.6-galak/arch/powerpc/boot/dts/tqm8548.dts
+ memory {
+ device_type = "memory";
+ reg = <0x 0x2000>;
+ };
is memory fixed on this board to 256M?
On Jun 5, 2008, at 10:18 AM, Josh Boyer wrote:
On Thu, 5 Jun 2008 09:11:48 -0600
"Grant Likely" <[EMAIL PROTECTED]> wrote:
On Thu, Jun 5, 2008 at 8:52 AM, Josh Boyer <[EMAIL PROTECTED]
> wrote:
This commit (patch omitted due to size) is sitting in my local tree:
commit 0d7efc1e80fc262bcc507
On Thu, Jun 5, 2008 at 12:56 PM, Josh Boyer <[EMAIL PROTECTED]> wrote:
> On Thu, 5 Jun 2008 12:46:39 -0600
> "Grant Likely" <[EMAIL PROTECTED]> wrote:
>
>> In Timur's case, it is absolutely appropriate to use cell-index and/or
>> a phandle to make sure it gets the correct DMA registers (which is
>>
On Thu, 5 Jun 2008 13:59:44 -0500
Kumar Gala <[EMAIL PROTECTED]> wrote:
>
> On Jun 5, 2008, at 10:18 AM, Josh Boyer wrote:
>
> > On Thu, 5 Jun 2008 09:11:48 -0600
> > "Grant Likely" <[EMAIL PROTECTED]> wrote:
> >
> >> On Thu, Jun 5, 2008 at 8:52 AM, Josh Boyer <[EMAIL PROTECTED]
> >> > wrote:
>
On Thu, 5 Jun 2008 13:14:00 -0600
"Grant Likely" <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 5, 2008 at 12:56 PM, Josh Boyer <[EMAIL PROTECTED]> wrote:
> > On Thu, 5 Jun 2008 12:46:39 -0600
> > "Grant Likely" <[EMAIL PROTECTED]> wrote:
> >
> >> In Timur's case, it is absolutely appropriate to use cel
Grant Likely wrote:
> No; use an alias in the aliases node. That is what aliases is designed
> for. Something like 'index' is a reinvention of the wheel.
Do aliases work in reverse? That is, if I have a pointer to a device node, can
I look up its alias directly? Or do I have to scan the alias
On Thursday 05 June 2008, Stephen Neuendorffer wrote:
> > "Grant Likely" <[EMAIL PROTECTED]> wrote:
> >
> > > Paulus, Can we just kill all of arch/ppc for .27 right now?
> >
> > Acked-by: Josh Boyer <[EMAIL PROTECTED]>
> Acked-by: Stephen Neuendorffer <[EMAIL PROTECTED]>
Acked-by: Arnd Bergmann <[
On Thu, Jun 5, 2008 at 2:12 PM, Arnd Bergmann <[EMAIL PROTECTED]> wrote:
> On Thursday 05 June 2008, Stephen Neuendorffer wrote:
>> > "Grant Likely" <[EMAIL PROTECTED]> wrote:
>> >
>> > > Paulus, Can we just kill all of arch/ppc for .27 right now?
>> >
>> > Acked-by: Josh Boyer <[EMAIL PROTECTED]>
On Jun 5, 2008, at 3:12 PM, Arnd Bergmann wrote:
On Thursday 05 June 2008, Stephen Neuendorffer wrote:
"Grant Likely" <[EMAIL PROTECTED]> wrote:
Paulus, Can we just kill all of arch/ppc for .27 right now?
Acked-by: Josh Boyer <[EMAIL PROTECTED]>
Acked-by: Stephen Neuendorffer <[EMAIL PROT
Olof Johansson wrote:
On Jun 5, 2008, at 3:12 PM, Arnd Bergmann wrote:
On Thursday 05 June 2008, Stephen Neuendorffer wrote:
"Grant Likely" <[EMAIL PROTECTED]> wrote:
Paulus, Can we just kill all of arch/ppc for .27 right now?
Acked-by: Josh Boyer <[EMAIL PROTECTED]>
Acked-by: Stephen Ne
On Jun 5, 2008, at 3:30 PM, Scott Wood wrote:
Olof Johansson wrote:
On Jun 5, 2008, at 3:12 PM, Arnd Bergmann wrote:
On Thursday 05 June 2008, Stephen Neuendorffer wrote:
"Grant Likely" <[EMAIL PROTECTED]> wrote:
Paulus, Can we just kill all of arch/ppc for .27 right now?
Acked-by: Josh
Kumar Gala wrote:
>
>> ===
>> --- /dev/null
>> +++ linux-2.6-galak/arch/powerpc/boot/dts/tqm8548.dts
>>
>
>> +memory {
>> +device_type = "memory";
>> +reg = <0x 0x2000>;
>> +};
>
> is memory fixed
[Fixed up the collision between Grant and Olof]
"Grant Likely" <[EMAIL PROTECTED]> wrote:
Paulus, Can we just kill all of arch/ppc for .27 right now?
Acked-by: Josh Boyer <[EMAIL PROTECTED]>
Acked-by: Stephen Neuendorffer <[EMAIL PROTECTED]>
Acked-by: Arnd Bergmann <[EMAIL PROTECTED]>
Ack
1 - 100 of 136 matches
Mail list logo
