linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andrew@ncrmnt.org (Andrew)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: rcm-k1879xb1: Add support for K1879XB1 SoC
Date: Fri, 26 Jun 2015 13:11:26 +0300	[thread overview]
Message-ID: <fb7ebabe2ce9cac0fac05535bbabfdbc@mail.ncrmnt.org> (raw)
In-Reply-To: <CAL_JsqKTUM8-ufR8gGJBsNtbc94LyS7o-7v=R2Fit3+0=-SofA@mail.gmail.com>

Rob Herring ????? 24.06.2015 05:15:
>> +
>> +static void __iomem *k1879_sctl_base(void)
>> +{
>> +       return (void __iomem *)RCM_K1879_SCTL_VIRT_BASE;
>> +}
>> +
>> +static void k1879_level_irq_i2c0_fixup(unsigned int irq, struct 
>> irq_desc *desc)
>> +{
>> +       writel(1, k1879_mif_base() + RCM_K1879_MIF_I2C_INT_STAT);
>> +       handle_level_irq(irq, desc);
>> +}
>> +
>> +static void k1879_level_irq_i2c1_fixup(unsigned int irq, struct 
>> irq_desc *desc)
>> +{
>> +       writel(1 << 0, k1879_sctl_base() + RCM_K1879_SCTL_INT_P_OUT);
>> +       handle_level_irq(irq, desc);
>> +}
>> +
>> +static void k1879_level_irq_i2c2_fixup(unsigned int irq, struct 
>> irq_desc *desc)
>> +{
>> +       writel(1 << 1, k1879_sctl_base() + RCM_K1879_SCTL_INT_P_OUT);
>> +       handle_level_irq(irq, desc);
>> +}
>> +
>> +static void k1879_level_irq_i2c3_fixup(unsigned int irq, struct 
>> irq_desc *desc)
>> +{
>> +       writel(1 << 2, k1879_sctl_base() + RCM_K1879_SCTL_INT_P_OUT);
>> +       handle_level_irq(irq, desc);
>> +}
> 
> What are all these for? They probably belong somewhere else.

As I've written already in response to to Russel King's review, these 
are the workarounds
around aeroflex i2c IP interrupt handling. Basically every interrupt 
from i2c requires
cleaning up respective 'pending' bit in SCTL register. This could be 
done in i2c driver,
but it is very platform-specific and would look ugly in the driver. If 
you know any cleaner
way for such a workaround, please advice. Right now I've cleaned up 
everything, save for
these fixups.


>> diff --git a/arch/arm/mach-rcm-k1879xb1/cpuidle.c 
>> b/arch/arm/mach-rcm-k1879xb1/cpuidle.c
>> new file mode 100644
>> index 0000000..7c621b6
>> --- /dev/null
>> +++ b/arch/arm/mach-rcm-k1879xb1/cpuidle.c
> 
> This should be a separate patch and located in drivers/cpuidle/

Got it, thanks.


-- 
Regards,
Andrew
RC Module :: http://module.ru

  reply	other threads:[~2015-06-26 10:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 15:50 [PATCH 0/4] [New SoC] Add support for RC Module's K1879XB1YA Andrew Andrianov
2015-06-23 15:50 ` [PATCH 1/4] ARM: rcm-k1879xb1: Add support for K1879XB1 SoC Andrew Andrianov
2015-06-23 16:11   ` Russell King - ARM Linux
2015-06-23 16:56     ` Andrew
2015-06-24  2:15   ` Rob Herring
2015-06-26 10:11     ` Andrew [this message]
2015-06-30 15:15     ` [PATCH v2 0/5] [New SoC] Add support for RC Module's K1879XB1YA Andrew Andrianov
2015-06-30 15:15       ` [PATCH v2 1/5] ARM: rcm-k1879xb1: Add support for K1879XB1 SoC Andrew Andrianov
2015-06-30 21:01         ` arnRe: " Arnd Bergmann
2015-06-30 15:15       ` [PATCH v2 2/5] of: Add vendor prefix for RC Module Andrew Andrianov
2015-06-30 15:15       ` [PATCH v2 3/5] ARM: dts: rcm-k1879xb1: Add dts files for K1879XB1YA Andrew Andrianov
2015-06-30 21:07         ` Arnd Bergmann
2015-06-30 15:15       ` [PATCH v2 4/5] ARM: Add defconfig for RC Module K1879XB1YA SoC Andrew Andrianov
2015-06-30 15:15       ` [PATCH v2 5/5] cpuidle: ARM: Add cpuidle driver for K1879XB1YA Andrew Andrianov
2015-06-30 16:24         ` Sudeep Holla
2015-06-30 21:09         ` Arnd Bergmann
2015-06-30 21:20           ` Andrew
2015-06-23 15:50 ` [PATCH 2/4] of: Add vendor prefix for RC Module Andrew Andrianov
2015-06-23 15:50 ` [PATCH 3/4] ARM: dts: rcm-k1879xb1: Add dts files for K1879XB1YA Andrew Andrianov
2015-06-23 15:50 ` [PATCH 4/4] ARM: Add defconfig for RC Module K1879XB1YA SoC Andrew Andrianov

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=fb7ebabe2ce9cac0fac05535bbabfdbc@mail.ncrmnt.org \
    --to=andrew@ncrmnt.org \
    --cc=linux-arm-kernel@lists.infradead.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 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).