Store the pointer to the i2c-clock controller/ adapter and increase its
usage-count during the initialization of the controller.

We need to keep the i2c-ocores till the time fmc-adc driver is in use.
Reported-by: Federico Vaga <federico.vaga@cern.ch>
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Add the API to write to the registers of the i2c clock.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

reported-by: Federico Vaga <federico.vaga@cern.ch>
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

The probe of fmc-adc should fail if it cannot register i2c-controller
for the clock.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

The Endianess of the i2c controller depends on the svec/spec platform.
Thus, define it accordingly.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Since we are not using si570 clock driver, there is no need to mention
it in board info. Otherwise it will remain in the file as unsed lines.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Print the register values of si570 on its debugs entry.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

The si570 i2c handler is used only to configure the clock at an early
stage, and never after. Thus, we don't require to save platform related
data of the i2c handler, and only the 'idr' should be enough.

Also because we can't do much with 'struct platform_device' data, but
with 'idr', we can obtain adapter and do data transfer via i2c APIs.

We can always retrieve the 'struct platform_device' data related to this
i2c_handler from its 'idr' if needed, for example in *exit().
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

The si570 clock is controlled by an i2c controller. Instantiate it and
match it with i2c-ocores so that we can configure the clock whenever we
want.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Resolve "make 6.1.0 release"

Closes #50

See merge request be-cem-edl/fec/hardware-modules/fmc-adc-100m14b4cha!17

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Resolve "automate convention version assignment"

Closes #29

See merge request be-cem-edl/fec/hardware-modules/fmc-adc-100m14b4cha!18

Resolve "Build entire SW in CI/CD and install the output"

Closes #48

See merge request be-cem-edl/fec/hardware-modules/fmc-adc-100m14b4cha!16

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Resolve "Use latest CI infrastructure for the builds"

Closes #47

See merge request be-cem-edl/fec/hardware-modules/fmc-adc-100m14b4cha!14

The test commands itself produce the result we want to know. Thus, we
don't want them to be printed.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

With project evergreen's CI/CD templates and includes, it is much easier
to build CI/Cd of other projects with simple .gitlab-ci.yml file.

One of the template is for building the driver for Fec-CC7 which already
includes docer image with needed packages. Thus, use it.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Apply patches from Gwen

See merge request be-cem-edl/fec/hardware-modules/fmc-adc-100m14b4cha!13

Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>

Resolve "Implement hardware monitoring API"

See merge request be-cem-edl/fec/hardware-modules/fmc-adc-100m14b4cha!12

In the case of error, the current API just reports via dev_err(), and
return a safe value. This is fine for callibration tools. But other
places, like sysfs, care about the eroor and the error code.

Thus, the API should return the error code in case of error, and the
tools which want a safe value, should do it in their own space.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Instead of manually calculating the size, allocating the memory, and
writing data to it, use devm_kasprintf(). It will do all the job in one
go.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Information from sensors like temperature, which are useful for
user-space, can be exposed via sysfs.

Earlier, the driver developers had to take care of defining the attributes,
initiating them, and perform other related jobs.

But since a long time, the HWMON framework in Linux has developed
significantly. And, utilizing it will reduce lot of maintainence work
for the developers.

All the sysfs related part is handled by the framework which also allows
user-space tools, like lm-sensors, to provide the data to the user in a
simplified manner.
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Resolve "Do a 6.0.4 release"

Closes #17

See merge request be-cem-edl/fec/hardware-modules/fmc-adc-100m14b4cha!6

And use it to avoid hard-coding the latest release version in the introduction.

Resolve "Migrate to common CI and publish bitstreams"

Closes #27

See merge request be-cem-edl/fec/hardware-modules/fmc-adc-100m14b4cha!11