public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Mohammed Billoo <mab@mab-labs.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: ocores: add gaisler to platform data
Date: Thu, 13 Aug 2020 16:10:59 +0200	[thread overview]
Message-ID: <87lfii7i18.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200811134426.7613-1-mab@mab-labs.com> (Mohammed Billoo's message of "Tue, 11 Aug 2020 09:44:26 -0400")

>>>>> "Mohammed" == Mohammed Billoo <mab@mab-labs.com> writes:

Hi,

Please send i2c patches to the linux-i2c mailing list as well, so the
i2c maintainer can apply it.

 > There may be instances when the device tree is not suitable to interface
 > with the ocores implementation. For example, when the FPGA/ASIC is
 > not on the same silicon die (e.g. the communication between the CPU and
 > the FPGA/ASIC is over PCI), information about the ocore implementation,
 > such as whether the gaisler implementation is used, must be determined
 > during runtime. In this case, the client driver would prepopulate the
 > platform data during device instantiation. Thus, a boolean needs to be
 > added in the platform data, to instruct the i2c-ocores driver whether
 > the gaisler register callbacks should be used.

 > Signed-off-by: Mohammed Billoo <mab@mab-labs.com>
 > ---
 >  drivers/i2c/busses/i2c-ocores.c          | 4 ++++
 >  include/linux/platform_data/i2c-ocores.h | 1 +
 >  2 files changed, 5 insertions(+)

 > diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c
 > index f5fc75b65a19..0975f6797069 100644
 > --- a/drivers/i2c/busses/i2c-ocores.c
 > +++ b/drivers/i2c/busses/i2c-ocores.c
 > @@ -647,6 +647,10 @@ static int ocores_i2c_probe(struct platform_device *pdev)
 >  i2c-> bus_clock_khz = pdata->bus_khz;
 >  		else
 >               i2c-> bus_clock_khz = 100;
 > +		if (pdata->gaisler) {
 > +			i2c->setreg = oc_setreg_grlib;
 > +			i2c->getreg = oc_getreg_grlib;
 > +		}
 >  	} else {
 >  		ret = ocores_i2c_of_probe(pdev, i2c);
 >  		if (ret)
 > diff --git a/include/linux/platform_data/i2c-ocores.h b/include/linux/platform_data/i2c-ocores.h
 > index e6326cbafe59..a3cb38f21417 100644
 > --- a/include/linux/platform_data/i2c-ocores.h
 > +++ b/include/linux/platform_data/i2c-ocores.h
 > @@ -16,6 +16,7 @@ struct ocores_i2c_platform_data {
 >  	bool big_endian; /* registers are big endian */
 >  	u8 num_devices; /* number of devices in the devices list */
 >  	struct i2c_board_info const *devices; /* devices connected to the bus */
 > +	bool gaisler; /* implementation is gaisler */

NIT: Perhaps it would be nicer to place this after big_endian, as it is
quite similar to that?

A clearer comment could be "Use Gaisler GRLIB accessors"

Other than that it looks good to me, thanks.

Acked-by: Peter Korsgaard <peter@korsgaard.com>

-- 
Bye, Peter Korsgaard

       reply	other threads:[~2020-08-13 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200811134426.7613-1-mab@mab-labs.com>
2020-08-13 14:10 ` Peter Korsgaard [this message]
     [not found]   ` <CALkjhPpF9wqaZGWQSZ9FphtcXD_obYubFX4te9xtcDdOP4M_gg@mail.gmail.com>
     [not found]     ` <CALkjhPrz=0q+sKsB9Y=i4LCCuFVg-bGSzGDyAHaE-XE=qBrVXQ@mail.gmail.com>
2020-08-13 16:29       ` [PATCH] i2c: ocores: add gaisler to platform data Peter Korsgaard
2020-08-13 18:42         ` Wolfram Sang

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=87lfii7i18.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mab@mab-labs.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