public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/7] mailbox: arm_mhu: add driver for ARM MHU controller
Date: Tue, 03 Feb 2015 16:25:11 +0100	[thread overview]
Message-ID: <4344803.3qsb2TUUaZ@wuerfel> (raw)
In-Reply-To: <20150203144611.GS8656@n2100.arm.linux.org.uk>

On Tuesday 03 February 2015 14:46:11 Russell King - ARM Linux wrote:
> On Tue, Feb 03, 2015 at 08:09:34PM +0530, Jassi Brar wrote:
> > On 3 February 2015 at 18:02, Russell King - ARM Linux
> > <linux@arm.linux.org.uk> wrote:
> > > On Tue, Feb 03, 2015 at 05:29:23PM +0800, Vincent Yang wrote:
> > >> +static int mhu_send_data(struct mbox_chan *chan, void *data)
> > >> +{
> > >> +     struct mhu_link *mlink = chan->con_priv;
> > >> +
> > >> +     pr_debug("%s:%d\n", __func__, __LINE__);
> > >> +     if (!mhu_last_tx_done(chan)) {
> > >> +             dev_err(chan->mbox->dev, "Last TX(%d) pending!\n", mlink->irq);
> > >> +             return -EBUSY;
> > >> +     }
> > >> +
> > >> +     writel_relaxed((u32)data, mlink->tx_reg + INTR_SET_OFS);
> > >
> > > Doesn't that cause a GCC warning?
> > >
> > I don't see any, but I'll drop the cast.
> 
> A cast is probably needed.  You're right that GCC no longer warns about
> this - I'm pretty sure it used to complain about casting pointers to
> ints, and we used to need to cast to "unsigned long" first.

It definitely warns about converting an u64 to pointer or back,
and it warns on 64-bit machines about this conversion.

On a related note, I wonder why the driver actually converts a pointer to
int. I believe we have discussed this in the past but don't remember the
outcome. I had expected to see here something like:

static int mhu_send_data(struct mbox_chan *chan, void *data)
{
	struct mhu_link *mlink = chan->con_priv;
	u32 *arg = data;

	writel_relaxed(*arg, mlink->tx_reg + INTR_SET_OFS);
}

i.e. dereferencing the pointer instead of using the actual value.

	Arnd

  reply	other threads:[~2015-02-03 15:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  9:21 [PATCH v5 0/7] Support for Fujitsu MB86S7X SoCs Vincent Yang
2015-02-03  9:27 ` [PATCH v5 1/7] ARM: Add platform support " Vincent Yang
2015-02-03  9:29 ` [PATCH v5 2/7] mailbox: arm_mhu: add driver for ARM MHU controller Vincent Yang
2015-02-03 12:32   ` Russell King - ARM Linux
2015-02-03 14:39     ` Jassi Brar
2015-02-03 14:46       ` Russell King - ARM Linux
2015-02-03 15:25         ` Arnd Bergmann [this message]
2015-02-04  3:27           ` Jassi Brar
2015-02-04 10:29             ` Arnd Bergmann
2015-02-04 14:34               ` Jassi Brar
2015-02-04 14:48                 ` Arnd Bergmann
2015-02-04 15:33                   ` Jassi Brar
2015-02-04 16:42                     ` Arnd Bergmann
2015-02-05  5:08                       ` Jassi Brar
2015-02-05 11:43                         ` Arnd Bergmann
     [not found]                           ` <CAJe_Zhf_WuRK2EE0Sj9ksXDDe5VA=DJ+H3eS4YRKpDZLdRRfow@mail.gmail.com>
2015-02-05 12:08                             ` Russell King - ARM Linux
2015-02-05 12:31                               ` Arnd Bergmann
2015-02-05 14:50                               ` Jassi Brar
2015-02-04 15:09               ` Russell King - ARM Linux
2015-02-03  9:30 ` [PATCH v5 3/7] ARM: MB86S7X: Add MCPM support Vincent Yang
2015-02-03  9:31 ` [PATCH v5 4/7] clk: Add clock driver for mb86s7x Vincent Yang
2015-02-03  9:32 ` [PATCH v5 5/7] dt: mb86s7x: add dt files for MB86S7x evbs Vincent Yang
2015-02-03  9:34 ` [PATCH v5 6/7] of: add Fujitsu vendor prefix Vincent Yang
2015-02-03  9:35 ` [PATCH v5 7/7] ARM: MB86S7x: Add configs Vincent Yang

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=4344803.3qsb2TUUaZ@wuerfel \
    --to=arnd@arndb.de \
    --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