All of lore.kernel.org
 help / color / mirror / Atom feed
From: Min Li <min.li.xe@renesas.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "richardcochran@gmail.com" <richardcochran@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lee.jones@linaro.org" <lee.jones@linaro.org>
Subject: RE: [PATCH net-next] ptp: clockmatrix: use rsmu driver to access i2c/spi bus
Date: Thu, 23 Sep 2021 16:29:44 +0000	[thread overview]
Message-ID: <TYCPR01MB66084980E50015D3C3F1F43CBAA39@TYCPR01MB6608.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20210923083032.093c3859@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>



> -----Original Message-----
> From: Jakub Kicinski <kuba@kernel.org>
> Sent: September 23, 2021 11:31 AM
> To: Min Li <min.li.xe@renesas.com>
> Cc: richardcochran@gmail.com; netdev@vger.kernel.org; linux-
> kernel@vger.kernel.org; lee.jones@linaro.org
> Subject: Re: [PATCH net-next] ptp: clockmatrix: use rsmu driver to access
> i2c/spi bus
> 
> On Wed, 22 Sep 2021 09:57:14 -0400 min.li.xe@renesas.com wrote:
> > From: Min Li <min.li.xe@renesas.com>
> >
> > rsmu (Renesas Synchronization Management Unit ) driver is located in
> > drivers/mfd and responsible for creating multiple devices including
> > clockmatrix phc, which will then use the exposed regmap and mutex
> > handle to access i2c/spi bus.
> 
> Does not build on 32 bit. You need to use division helpers.

Hi Jakub

I did build it through 32 bit arm and didn't get the problem.

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-

Thanks

Min

  reply	other threads:[~2021-09-23 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 13:57 [PATCH net-next] ptp: clockmatrix: use rsmu driver to access i2c/spi bus min.li.xe
2021-09-23 15:30 ` Jakub Kicinski
2021-09-23 16:29   ` Min Li [this message]
2021-09-23 16:41     ` Jakub Kicinski
2021-09-23 19:49       ` Min Li
2021-09-23 20:04         ` Jakub Kicinski
2021-09-23 21:05           ` Min Li

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=TYCPR01MB66084980E50015D3C3F1F43CBAA39@TYCPR01MB6608.jpnprd01.prod.outlook.com \
    --to=min.li.xe@renesas.com \
    --cc=kuba@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.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 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.