All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mitsyanko <i.mitsyanko@samsung.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: e.voevodin@samsung.com, qemu-devel@nongnu.org,
	"Peter A. G. Crosthwaite" <peter.crosthwaite@petalogix.com>,
	kyungmin.park@samsung.com, d.solodkiy@samsung.com,
	edgar.iglesias@gmail.com, m.kozlov@samsung.com,
	john.williams@petalogix.com
Subject: Re: [Qemu-devel] [PATCH v5 2/4] exynos4210: Added SD host controller model
Date: Tue, 17 Jul 2012 18:58:20 +0400	[thread overview]
Message-ID: <50057D8C.8090705@samsung.com> (raw)
In-Reply-To: <CAFEAcA9VoQmutEYM+dVHuRpvW_OsKmysrsHkyRF86hkJUrsChA@mail.gmail.com>

On 07/17/2012 05:37 PM, Peter Maydell wrote:
> On 17 July 2012 13:55, Igor Mitsyanko <i.mitsyanko@samsung.com> wrote:
>> On 07/16/2012 09:13 PM, Peter Maydell wrote:
>>> The IRQ handling code still looks really weird. I would expect
>>> that the code would be:
>>>     [code which updates various kinds of irq related state]
>>>     sdhci_update_irq();
>>>
>>> where sdhci_update_irq() calls qemu_set_irq() based on the state.
>>>
>>> At the moment it looks as if you're using slotint as a cached value
>>> of the expression
>>> "((s->norintsts & s->norintsigen) || (s->errintsts & s->errintsigen) ||
>>>    ((s->norintsts & SDHC_NIS_INSERT) && (s->wakcon & SDHC_WKUP_ON_INS)) ||
>>>    ((s->norintsts & SDHC_NIS_REMOVE) && (s->wakcon & SDHC_WKUP_ON_RMV)))"
>>>
>>> [can these two ever have different values?] and also attempting to
>>> shortcut by manually updating slotint in codepaths which change only
>>> parts of the state which this expression is testing. Why not just do
>>> things the simple and straightforward way and get rid of slotint
>>> completely?
>> Linux seems to ignore SLOTINT status register, probably because it only
>> supports single slot configuration while SLOTINT really required for
>> multislot controllers only, so I think we can remove it completely and
>> simply return 0 on reads. Same for status of WAKCON register, nobody cares
>> about controller's wakeup functionality. Then update irq function could be
>> simplified to
>>
>>   "qemu_set_irq(s->irq, (s->norintsts & s->norintsigen) || (s->errintsts &
>> s->errintsigen))"
> We should be modelling what the hardware does, not just what Linux happens
> to use.
>
> I've now gone and found the SDHCI specification. (figure 1-6 and table 1-6
> in the simplified spec v3.00 are relevant here.) What happens is that the
> SLOTINT bit tracks the external interrupt line's state, and that interrupt
> line is the logical combination of the various *sts/*sigen registers.
> I would suggest two functions:
>
> int sdhci_slotint(SDHCIState *s)
> which just calculates and returns the external interrupt line state
> (might be able to make this 'static'), and
>
> void sdhci_update_irq(SDHCIState *s)
> {
>      qemu_set_irq(sdhci_slotint(s));
> }
>
> Then just call sdhci_update_irq() any time you update state that
> can affect the interrupt line.
>
> The 'read the SLOTINT register' implementation just calls
> sdhci_slotint(), obviously.
>
> This approach:
>   * doesn't store any extra state in our state struct that the hardware
>     doesn't also have as stored state
>   * doesn't prematurely optimise the calculation of the interrupt line
>     state, so it's nice and clear how the irq line works and that it
>     follows the spec
>
> -- PMM
>

Ok, but I'd rather make sdhci_slotint() return uint8_t, to emphasize 
that this function returns
a value of hardware SLOTINT register.

  reply	other threads:[~2012-07-17 14:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05  4:03 [Qemu-devel] [PATCH v5 0/4] Standard SD host controller model Peter A. G. Crosthwaite
2012-07-05  4:03 ` [Qemu-devel] [PATCH v5 1/4] hw: introduce standard SD host controller Peter A. G. Crosthwaite
2012-07-05  4:04 ` [Qemu-devel] [PATCH v5 2/4] exynos4210: Added SD host controller model Peter A. G. Crosthwaite
2012-07-16 17:13   ` Peter Maydell
2012-07-17 12:55     ` Igor Mitsyanko
2012-07-17 13:37       ` Peter Maydell
2012-07-17 14:58         ` Igor Mitsyanko [this message]
2012-07-17 15:04           ` Peter Maydell
2012-07-18  7:13             ` Peter Crosthwaite
2012-07-05  4:04 ` [Qemu-devel] [PATCH v5 3/4] vl.c: allow for repeated -sd arguments Peter A. G. Crosthwaite
2012-07-16 17:28   ` Peter Maydell
2012-07-05  4:04 ` [Qemu-devel] [PATCH v5 4/4] xilinx_zynq: Added SD controllers Peter A. G. Crosthwaite
2012-07-16 17:28   ` Peter Maydell

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=50057D8C.8090705@samsung.com \
    --to=i.mitsyanko@samsung.com \
    --cc=d.solodkiy@samsung.com \
    --cc=e.voevodin@samsung.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=john.williams@petalogix.com \
    --cc=kyungmin.park@samsung.com \
    --cc=m.kozlov@samsung.com \
    --cc=peter.crosthwaite@petalogix.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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.