All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Vitaly Bordug <vitb@kernel.crashing.org>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] [POWERPC] MPC8349E-mITX: use platform IDE driver for CF	interface
Date: Wed, 25 Jul 2007 13:39:20 -0500	[thread overview]
Message-ID: <46A798D8.7020906@freescale.com> (raw)
In-Reply-To: <46A7941F.2050300@ru.mvista.com>

Sergei Shtylyov wrote:
> Hello.
> 
> Scott Wood wrote:
> 
>>>    Also, what mmio-ide in the compat properly means in the context of 
>>> ide_platform which is able to handle both port and memory mapped IDE.
> 
> 
>> I/O-space is only valid in the context of PCI, ISA, or similar buses, and
>> the bus-specific reg format indicates whether it's mmio-space or
>> io-space.
> 
>    You could save time on lecturing me (and use it to look on the driver 
> ;-).

Sorry, I misread the question as being a mismatch between the 
capabilities of the device binding and the driver, not about the 
specific compatible name.  Something like "generic-ide" would probably 
be better.

>> What is board specific about a set of standard IDE registers at a given
> 
>    The regisrer mapping used is highly non-standard.

The gap between registers is nonstandard, but that's a fairly common 
type of noncompliance in embedded-land, and probably merits being 
supported in a generic way.  I wouldn't call it "highly" nonstandard.

Is there some other non-standardness that I'm missing?

>    We're already in board specific code, so why the heck not? :-)
> 
>> various ns16550-compatibles out there as well?
> 
>    I never suggested that -- what I did suggest was make of_serial.c 
> recognize certain chip types and register them with 8250 driver.

What would be the advantage of maintaining a list of chips whose only 
difference is register spacing, rather than just using reg-shift and 
being done with it?

-Scott

WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/2] [POWERPC] MPC8349E-mITX: use platform IDE driver for CF	interface
Date: Wed, 25 Jul 2007 13:39:20 -0500	[thread overview]
Message-ID: <46A798D8.7020906@freescale.com> (raw)
In-Reply-To: <46A7941F.2050300@ru.mvista.com>

Sergei Shtylyov wrote:
> Hello.
> 
> Scott Wood wrote:
> 
>>>    Also, what mmio-ide in the compat properly means in the context of 
>>> ide_platform which is able to handle both port and memory mapped IDE.
> 
> 
>> I/O-space is only valid in the context of PCI, ISA, or similar buses, and
>> the bus-specific reg format indicates whether it's mmio-space or
>> io-space.
> 
>    You could save time on lecturing me (and use it to look on the driver 
> ;-).

Sorry, I misread the question as being a mismatch between the 
capabilities of the device binding and the driver, not about the 
specific compatible name.  Something like "generic-ide" would probably 
be better.

>> What is board specific about a set of standard IDE registers at a given
> 
>    The regisrer mapping used is highly non-standard.

The gap between registers is nonstandard, but that's a fairly common 
type of noncompliance in embedded-land, and probably merits being 
supported in a generic way.  I wouldn't call it "highly" nonstandard.

Is there some other non-standardness that I'm missing?

>    We're already in board specific code, so why the heck not? :-)
> 
>> various ns16550-compatibles out there as well?
> 
>    I never suggested that -- what I did suggest was make of_serial.c 
> recognize certain chip types and register them with 8250 driver.

What would be the advantage of maintaining a list of chips whose only 
difference is register spacing, rather than just using reg-shift and 
being done with it?

-Scott

  reply	other threads:[~2007-07-25 18:39 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 16:53 [PATCH 1/2] [IDE] Platform IDE driver (was: MMIO IDE driver) Vitaly Bordug
2007-07-25 16:53 ` Vitaly Bordug
2007-07-25 16:53 ` Vitaly Bordug
2007-07-25 16:53 ` [PATCH 2/2] [POWERPC] MPC8349E-mITX: use platform IDE driver for CF interface Vitaly Bordug
2007-07-25 16:53   ` Vitaly Bordug
2007-07-25 16:53   ` Vitaly Bordug
2007-07-25 17:06   ` Sergei Shtylyov
2007-07-25 17:06     ` Sergei Shtylyov
2007-07-25 17:54     ` Sergei Shtylyov
2007-07-25 18:01       ` Scott Wood
2007-07-25 18:01         ` Scott Wood
2007-07-25 18:19         ` Sergei Shtylyov
2007-07-25 18:19           ` Sergei Shtylyov
2007-07-25 18:39           ` Scott Wood [this message]
2007-07-25 18:39             ` Scott Wood
2007-07-25 19:30             ` Sergei Shtylyov
2007-07-25 19:30               ` Sergei Shtylyov
2007-07-26 16:24               ` Sergei Shtylyov
2007-07-26 16:24                 ` Sergei Shtylyov
2007-07-31 22:47             ` Segher Boessenkool
2007-07-31 22:47               ` Segher Boessenkool
2007-07-25 18:29         ` Sergei Shtylyov
2007-07-25 18:29           ` Sergei Shtylyov
2007-07-25 18:46           ` Scott Wood
2007-07-25 18:46             ` Scott Wood
2007-07-26 17:21             ` Vitaly Bordug
2007-07-26 17:21               ` Vitaly Bordug
2007-07-26 17:45               ` Sergei Shtylyov
2007-07-26 17:45                 ` Sergei Shtylyov
2007-07-31 22:36       ` Segher Boessenkool
2007-07-31 22:36         ` Segher Boessenkool
2007-07-31 23:56         ` Alan Cox
2007-07-31 23:56           ` Alan Cox
2007-08-06 17:19           ` Segher Boessenkool
2007-08-06 17:19             ` Segher Boessenkool
2007-08-01 13:11         ` Sergei Shtylyov
2007-08-01 13:11           ` Sergei Shtylyov
2007-07-26 17:12     ` Vitaly Bordug
2007-07-26 17:12       ` Vitaly Bordug
2007-07-25 17:29   ` Scott Wood
2007-07-25 17:29     ` Scott Wood
2007-07-25 17:43 ` [PATCH 1/2] [IDE] Platform IDE driver (was: MMIO IDE driver) Alan Cox
2007-07-25 17:43   ` Alan Cox
2007-07-26 19:28   ` Bartlomiej Zolnierkiewicz
2007-07-26 19:28     ` Bartlomiej Zolnierkiewicz
2007-07-25 17:59 ` Kumar Gala
2007-07-25 17:59   ` Kumar Gala
2007-07-25 19:00 ` Sergei Shtylyov
2007-07-25 19:00   ` Sergei Shtylyov
2007-07-25 19:05   ` Scott Wood
2007-07-25 19:05     ` Scott Wood
2007-07-25 19:16     ` Sergei Shtylyov
2007-07-25 19:16       ` Sergei Shtylyov
2007-07-25 19:17       ` [PATCH 1/2] [IDE] Platform IDE driver Scott Wood
2007-07-25 19:17         ` Scott Wood
2007-07-25 19:35         ` Sergei Shtylyov
2007-07-25 19:35           ` Sergei Shtylyov
2007-07-31 22:31           ` Segher Boessenkool
2007-07-31 22:31             ` Segher Boessenkool
2007-08-01 12:39             ` Sergei Shtylyov
2007-08-01 12:39               ` Sergei Shtylyov
2007-08-06 17:16               ` Segher Boessenkool
2007-08-06 17:16                 ` Segher Boessenkool
2007-07-25 19:37 ` [PATCH 1/2] [IDE] Platform IDE driver (was: MMIO IDE driver) Guennadi Liakhovetski
2007-07-25 19:37   ` Guennadi Liakhovetski
2007-07-25 19:48   ` Sergei Shtylyov
2007-07-25 19:48     ` Sergei Shtylyov
2007-07-25 19:54     ` Guennadi Liakhovetski
2007-07-25 19:54       ` Guennadi Liakhovetski
2007-07-25 20:01       ` Sergei Shtylyov
2007-07-25 20:01         ` Sergei Shtylyov
2007-07-25 20:09         ` Guennadi Liakhovetski
2007-07-25 20:09           ` Guennadi Liakhovetski
2007-07-25 20:39   ` Alan Cox
2007-07-25 20:39     ` Alan Cox
2007-07-26 19:41     ` Guennadi Liakhovetski
2007-07-26 19:41       ` Guennadi Liakhovetski
2007-07-26 19:52       ` Sergei Shtylyov
2007-07-26 19:52         ` Sergei Shtylyov
2007-07-26 20:13         ` Guennadi Liakhovetski
2007-07-26 20:11       ` Bartlomiej Zolnierkiewicz
2007-07-26 20:11         ` Bartlomiej Zolnierkiewicz
2007-07-26 19:28 ` Bartlomiej Zolnierkiewicz
2007-07-26 19:28   ` Bartlomiej Zolnierkiewicz

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=46A798D8.7020906@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sshtylyov@ru.mvista.com \
    --cc=vitb@kernel.crashing.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 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.