When working on applications using libsamsung-ipc, we sometimes
have functions that have an ipc client type argument and that
work for all 3 ipc client types, or want to refactorize the
code to do that in order to make the code more clean and generic.

However in these cases, these functions often needed to output
some error message or tell users what is going on through
logging prints, and the code ends up being way cleaner if there
is a generic function to get the name of the ipc client type.

In many cases it makes sense not to use the full
IPC_CLIENT_TYPE_<type> name but only the <name> type in these
messages, so because it's easier to add IPC_CLIENT_TYPE_ to the
<type> than removing it, it makes sense to only return the string
associated to the type (like "FMT", "RFS" or "DUMMY".

The least significant number of the library version was also
bumped as we are adding a new function, but the applications that
were built against older libsamsung-ipc revisions should still work.

However applications that depends on this ipc_client_type_string
will not work with previous versions of libsamsung-ipc.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

These wrappers are meant to handle the case where read or writes
handles a smaller number of bytes than requested.

This way that handling doesn't need to be duplicated everywhere
in libsamsung-ipc.

Having access to the ipc_client struct could enable future
logging of read and writes without having to change any of the
code already using data_read and data_write.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

While ipc_group_string is not used by libsamsung-ipc (yet),
it's still a good idea to add it as tools and applications using
libsamsung-ipc can then use it to display the group of a command.

It's also a better idea to have it in libsamsung-ipc than in
each tool using it as libsamsung-ipc centralizes the knowledge
about the samsung-ipc protocol, so if new groups appear at some
point, the ipc_group_string function could be updated along the way.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

Including samsung-ipc.h in a file without other includes results
in a compilation error:
    .../include/samsung-ipc.h:161:1: error: unknown type name ‘off_t’
       161 | off_t file_data_size(struct ipc_client *client, [...]
           | ^~~~~

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

Including samsung-ipc.h in a file without other includes results
in a compilation error:
    .../include/samsung-ipc.h:51:2: error: unknown type name ‘size_t’
        51 |  size_t size;
           |  ^~~~~~
    .../include/samsung-ipc.h:77:7: error: unknown type name ‘size_t’
        77 |       size_t size),
           |       ^~~~~~
    .../include/samsung-ipc.h:26:1: note: ‘size_t’ is defined in header
                                   ‘<stddef.h>’;
				   did you forget to ‘#include <stddef.h>’?
        25 | #include <sys/time.h>
       +++ |+#include <stddef.h>
        26 |

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

This separates more what is part of the header and what is not
so things are more clear to the people reading the code.

In addition, having all includes statements inside the #ifdef #endif
header guards avoids issues with the inclusion of headers that are
missing such guards. This can happen with headers imported from vendor
kernels.

So while headers imported from vendor kernels are typically not
included in the headers exported by libsamsung-ipc, it's still good
to have a consistent code style between exported and non exported
headers.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

This contains no functional changes.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Reviewed-by: Joonas Kylmälä <joonas.kylmala@iki.fi>

This contains no functional changes.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Reviewed-by: Joonas Kylmälä <joonas.kylmala@iki.fi>

This contains no functional changes.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Reviewed-by: Joonas Kylmälä <joonas.kylmala@iki.fi>