Home
last modified time | relevance | path

Searched hist:"8729 b1ae2cbda83059a55811614a2b0dbfdf7e53" (Results 1 – 8 of 8) sorted by relevance

/openbmc/u-boot/drivers/misc/
H A Dstm32mp_fuse.cdiff 8729b1ae2cbda83059a55811614a2b0dbfdf7e53 Tue Nov 06 16:21:39 CST 2018 Simon Glass <sjg@chromium.org> misc: Update read() and write() methods to return bytes xfered

At present these functions return 0 on success. For some devices we want
to know how many bytes were transferred. It seems useful to adjust the API
to be more like the POSIX read() and write() functions.

Update these two methods, a test and all users.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>
H A Dmisc_sandbox.cdiff 8729b1ae2cbda83059a55811614a2b0dbfdf7e53 Tue Nov 06 16:21:39 CST 2018 Simon Glass <sjg@chromium.org> misc: Update read() and write() methods to return bytes xfered

At present these functions return 0 on success. For some devices we want
to know how many bytes were transferred. It seems useful to adjust the API
to be more like the POSIX read() and write() functions.

Update these two methods, a test and all users.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>
H A Drockchip-efuse.cdiff 8729b1ae2cbda83059a55811614a2b0dbfdf7e53 Tue Nov 06 16:21:39 CST 2018 Simon Glass <sjg@chromium.org> misc: Update read() and write() methods to return bytes xfered

At present these functions return 0 on success. For some devices we want
to know how many bytes were transferred. It seems useful to adjust the API
to be more like the POSIX read() and write() functions.

Update these two methods, a test and all users.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>
H A Daltera_sysid.cdiff 8729b1ae2cbda83059a55811614a2b0dbfdf7e53 Tue Nov 06 16:21:39 CST 2018 Simon Glass <sjg@chromium.org> misc: Update read() and write() methods to return bytes xfered

At present these functions return 0 on success. For some devices we want
to know how many bytes were transferred. It seems useful to adjust the API
to be more like the POSIX read() and write() functions.

Update these two methods, a test and all users.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>
/openbmc/u-boot/drivers/clk/
H A Dclk_vexpress_osc.cdiff 8729b1ae2cbda83059a55811614a2b0dbfdf7e53 Tue Nov 06 16:21:39 CST 2018 Simon Glass <sjg@chromium.org> misc: Update read() and write() methods to return bytes xfered

At present these functions return 0 on success. For some devices we want
to know how many bytes were transferred. It seems useful to adjust the API
to be more like the POSIX read() and write() functions.

Update these two methods, a test and all users.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>
/openbmc/u-boot/test/dm/
H A Dmisc.cdiff 8729b1ae2cbda83059a55811614a2b0dbfdf7e53 Tue Nov 06 16:21:39 CST 2018 Simon Glass <sjg@chromium.org> misc: Update read() and write() methods to return bytes xfered

At present these functions return 0 on success. For some devices we want
to know how many bytes were transferred. It seems useful to adjust the API
to be more like the POSIX read() and write() functions.

Update these two methods, a test and all users.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>
/openbmc/u-boot/include/
H A Dmisc.hdiff 8729b1ae2cbda83059a55811614a2b0dbfdf7e53 Tue Nov 06 16:21:39 CST 2018 Simon Glass <sjg@chromium.org> misc: Update read() and write() methods to return bytes xfered

At present these functions return 0 on success. For some devices we want
to know how many bytes were transferred. It seems useful to adjust the API
to be more like the POSIX read() and write() functions.

Update these two methods, a test and all users.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>
/openbmc/u-boot/arch/arm/mach-stm32mp/
H A Dcpu.cdiff 8729b1ae2cbda83059a55811614a2b0dbfdf7e53 Tue Nov 06 16:21:39 CST 2018 Simon Glass <sjg@chromium.org> misc: Update read() and write() methods to return bytes xfered

At present these functions return 0 on success. For some devices we want
to know how many bytes were transferred. It seems useful to adjust the API
to be more like the POSIX read() and write() functions.

Update these two methods, a test and all users.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>