From: Alexander Varnin <fenixk19@mail.ru>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: linux-samsung-soc@vger.kernel.org, Kukjin Kim <kgene@kernel.org>
Subject: Re: [PATCH] ARM: S3C2443: Workaround for 2443 EXTINT error
Date: Sat, 24 Nov 2012 13:01:31 +0400 [thread overview]
Message-ID: <50B08CEB.70308@mail.ru> (raw)
In-Reply-To: <201211240116.44494.heiko@sntech.de>
I've done it within another function, because otherwise users of other
chips would pay for a one more runtime check, which they don't need. On
the other hand, this function get called not so frequently, to make it
valueable. The first version of my patch i've used internally worked as
you said, so i can resend it.
I want to ask more experienced users of s3c2443. If this problem occures
on all s3c2443 chips, or only with some series of it? Maybe we need some
more checks, not to break working cases.
24.11.2012 04:16, Heiko Stübner пишет:
>>> What does this do or what should it do? Also it gets calculated but
>>> never used?
>>>
>>> And please use scripts/checkpatch.pl to verify your patch follows
>>> coding guidelines, as this block is especially hard to read.
> So essentially register-reads somehow returned transformed data, but the write
> is done according to the datasheet.
>
>
> It would definitely be better to integrate it into the existing _irqext_type
> function instead of introducing a second one.
>
> The cpu_id is present in the samsung_cpu_id var and the list of cpus including
> the s3c2443 can be found in common.c. With this it would be possible to
> identify when the irq code is run on a s3c2443 machine and the original
> _irqext_type function could change the behaviour accordingly.
>
> Not sure if it would make sense to introduce soc_is_s3c2443() etc macros for
> this.
>
> And of course the actual block doing the transformation on read would need a
> more elaborate comment on the why and how, because in 3 years someone might
> not directly see what this does and why it was necessary.
>
next prev parent reply other threads:[~2012-11-24 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 0:16 [PATCH] ARM: S3C2443: Workaround for 2443 EXTINT error Heiko Stübner
2012-11-24 9:01 ` Alexander Varnin [this message]
2012-11-24 11:24 ` Heiko Stübner
2012-11-24 12:32 ` Heiko Stübner
-- strict thread matches above, loose matches on Subject: below --
2012-11-22 13:00 Alexander Varnin
2012-11-22 23:11 ` Heiko Stübner
[not found] ` <50AF2157.5050508@mail.ru>
2012-11-24 0:04 ` Heiko Stübner
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=50B08CEB.70308@mail.ru \
--to=fenixk19@mail.ru \
--cc=heiko@sntech.de \
--cc=kgene@kernel.org \
--cc=linux-samsung-soc@vger.kernel.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.