qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
To: Thiemo Seufer <ths@networkno.de>
Cc: Takashi Yoshii <yoshii.takashi@renesas.com>,
	Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel]  [PATCH] SH7750/51: add register BCR3, NCR4, PCR, RTCOR, RTCNT, RTCSR, SDMR2, SDMR3 and fix BCR2 support
Date: Mon, 15 Dec 2008 09:37:38 +0900	[thread overview]
Message-ID: <4945A6D2.8020806@juno.dti.ne.jp> (raw)
In-Reply-To: <20081214172431.GC7738@networkno.de>

Thiemo Seufer wrote:
> Jean-Christophe PLAGNIOL-VILLARD wrote:
>> On 00:36 Mon 15 Dec     , Shin-ichiro KAWASAKI wrote:
>>> Jean-Christophe PLAGNIOL-VILLARD wrote:
>>>>>>  -
>>>>>> +static int inline is_sh7751r_cpu(SH7750State * s)
>>>>>> +{
>>>>>> +	return (s->cpu->id & (SH_CPU_SH7751R));
>>>>>> +}
>>>>>>  /**********************************************************************
>>>>>>   I/O ports
>>>>>>  **********************************************************************/
>>>>>> @@ -212,8 +219,17 @@ static uint32_t sh7750_mem_readw(void *opaque, target_phys_addr_t addr)
>>>>>>      switch (addr) {
>>>>>>      case SH7750_BCR2_A7:
>>>>>>  	return s->bcr2;
>>>>>> +    case SH7750_BCR3_A7:
>>>>>> +	if(is_sh7751r_cpu(s)) {
>>>>>> +	    return s->bcr3;
>>>>>> +	} else {
>>>>>> +	    error_access("word read", addr);
>>>>>> +	    assert(0);
>>>>>> +	}
>>>>> BCR3 exists not only for SH7751R, but also SH7750.
>>>>> I think is_shh751r_cpu() check and error handling
>>>>> should be removed to simplify the differcence.
>>>> as write in the SH7751r datasheet
>>>>
>>>> Bus Control Register 3 (BCR3) (SH7751R Only)
>>>> Bus Control Register 4 (BCR4) (SH7751R Only)
>>>>
>>>> That's why I've add the check
>>> I see.  Your code is right, but let me add one more comment.
>>>
>>> - SH7750 and SH7751 ... does not have BCR3 nor BCR4
>>> - SH7750R and SH7751R ... have BCR3 and BCR4
>>>
>>> So, to make it better, how about renaming "is_h7751r_cpu()"
>>> into "has_bcr3_and_bcr4()"?  It will be like this.
>>>
>>> static int inline has_bcr3_and_bcr4(SH7750State * s)
>>> {
>>>        return (s->cpu->id & (SH_CPU_SH7750R | SH_CPU_SH7751R));
>>> }
>> I've download the SH7750 & SH7751 datasheet and yes as it's only availlable on
>> 'R' cpu revision
>>
>> I'll update as it
>>>
>>>>> Compared to 'if' statement, 'switch-case' might be more easy to
>>>>> understand, like as follows.
>>>>>   case SH7750_SDMR2 ... SH7750_SDMR2 + SDMR2_REGNB
>>>> ok elvenif it's a gcc ony extension
>>> Ah, gccism policy seems not clear in QEMU project.
>>> This extension is used in many hw/*.c, so I guessed it
>>> as a QEMU's usual implementation style.
>>> I hope comments on it from main developers.
>>>
>> Yes it will be nice
> 
> I believe "no new gcc-isms" would be a good policy.

Thank you.  I'll follow it.

So, my suggestion about 'if' vs 'switch-case' is not appropriate.


Regards,
Shin-ichiro KAWASAKI

  reply	other threads:[~2008-12-15  0:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 11:49 [Qemu-devel] [PATCH] SH7750/51: add register BCR3, NCR4, PCR, RTCOR, RTCNT, RTCSR, SDMR2, SDMR3 and fix BCR2 support Jean-Christophe PLAGNIOL-VILLARD
2008-12-14 11:37 ` Shin-ichiro KAWASAKI
2008-12-14 14:51   ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-14 15:36     ` Shin-ichiro KAWASAKI
2008-12-14 16:37       ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-14 17:24         ` Thiemo Seufer
2008-12-15  0:37           ` Shin-ichiro KAWASAKI [this message]
2008-12-15  1:08             ` Thiemo Seufer
2008-12-14 17:28       ` Aurelien Jarno
2008-12-17  9:18         ` [Qemu-devel] [PATCH V2] SH7750/51: add register BCR3, BCR4, " Jean-Christophe PLAGNIOL-VILLARD
2008-12-18 15:51           ` Aurelien Jarno
2008-12-18 21:49             ` [Qemu-devel] [PATCH V3] " Jean-Christophe PLAGNIOL-VILLARD
2008-12-18 23:33               ` [Qemu-devel] [PATCH V4] " Jean-Christophe PLAGNIOL-VILLARD
2009-02-07 15:19                 ` Aurelien Jarno

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=4945A6D2.8020806@juno.dti.ne.jp \
    --to=kawasaki@juno.dti.ne.jp \
    --cc=iwamatsu.nobuhiro@renesas.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ths@networkno.de \
    --cc=yoshii.takashi@renesas.com \
    /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).